Repository navigation
chore(runtime): align script lock format with release runner - #184
Merged
Merged
Conversation
nmartorell
approved these changes
Oct 8, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Prepare still failed after the dependency refresh because CI uses uv 0.12.23, which rewrites the runtime lock's format revision from 3 to 5. The refreshed dependencies already match CI; this changes only that revision field.
Regenerated with
uvx --from uv==0.12.23 uv lock --script runtime/run_mcp.py --upgrade, matching the failed runner's version. Lock validation and a second upgrade pass without changing the file.Validation: locked sync, all pre-commit checks, 642 tests, and package build passed. Dependency versions and hashes are unchanged from #183.
Squash-merge into release/0.8.0 after review and CI, then rerun Prepare from main for release/0.8.0.