chore: sync uv.lock to 0.8.0 - #174
Merged
Merged
Conversation
release-please bumped apps/cli (openmagpie) and the root product version to 0.8.0 but doesn't touch uv.lock, so re-lock to match (openmagpie + the openmagpie-suite workspace root 0.7.0 -> 0.8.0). No dependency resolution changes.
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
1 participant
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.
What
Re-locks
uv.lockafter the 0.8.0 release: bumpsopenmagpie(theapps/cliCLI package) and theopenmagpie-suiteworkspace-root virtual package from 0.7.0 → 0.8.0.Why
release-please bumped the versions in
apps/cli/pyproject.tomland the rootpyproject.toml/version.txtwhen it cut v0.8.0, but it doesn't touchuv.lock. That left the lock pinningopenmagpieat 0.7.0 while its pyproject says 0.8.0, whichuv lock --check/ a--frozensync would flag as drift. Same follow-up that #165 bundled for 0.7.0.Notes
uv lockoutput was exactly the two version lines; no dependency resolution changed (75 packages resolved identically).uv lock --checkpasses after the change.chore:type, so it stays out of the changelog.