Repository navigation
ci: centralize uv setup and update certifi - #456
Merged
Merged
Conversation
frgfm
force-pushed
the
codex/uv-certifi-pyro-engine
branch
from
October 21, 2026 10:00
2400e39 to
4ce94b5
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #456 +/- ##
========================================
Coverage 80.02% 80.02%
========================================
Files 6 6
Lines 846 846
========================================
Hits 677 677
Misses 169 169
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
frgfm
force-pushed
the
codex/uv-certifi-pyro-engine
branch
from
October 21, 2026 13:04
8dd21d6 to
108713b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
All uv workflows use one local composite action. It reads the root
[tool.uv].required-versionand installs its lowest compatible version. The Docker images remain pinned to uv 0.13.4.The project range is
>=0.13.4,<1.0.0. The four tracked lockfiles update certifi to2026.10.19and use uv's current lock format.Why
Astral's uv advisory says versions before 0.13.4 include the affected emSign root. Certifi published a related advisory. Neither advisory has a CVE. The locks use certifi 2026.10.19.
Test plan
uv lock --upgrade-package certifianduv lock --checkpassed in all four projects.git diff --checkpassed.