chore: sync uv.lock own-version to the released 2.8.0 - #128
Merged
Conversation
Release 2.8.0 (#125) bumped pyproject.toml but the committed uv.lock still recorded agentscore-commerce 2.7.2. uv.lock embeds the project's own version, so a version bump leaves the lock stale unless uv lock is re-run. Re-locking resolves 141 packages with no dependency change; this corrects only the own-version line.
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.
Summary
Release 2.8.0 (#125) bumped
pyproject.tomlto 2.8.0 but the committeduv.lockstill recordedagentscore-commerceat 2.7.2.uv.lockembeds the project's own version, so a version bump leaves the lock stale unlessuv lockis re-run in the same change. This syncs the lock's own-version line to 2.8.0.uv lockresolves 141 packages with no dependency change; the only diff is the own-version line. The published 2.8.0 wheel is unaffected (the lock's own-version line is metadata, not shipped), so no re-release is needed.Worked with: Varun.
Type of change
Public API
None.
Test plan
uv lockre-run produced a single-line diff (2.7.2 to 2.8.0) and no dependency changes. No code changed. CI (ruff, format, ty, pytest) is the gate.Checklist