Repository navigation
chore(release): keep uv.lock in sync with release versions - #558
Merged
Merged
Conversation
release-please bumps pyproject.toml and adk/pyproject.toml but never
touched uv.lock, so the lock fell behind on every release. CI ran
uv sync without --locked, so the drift was not caught.
- Add toml extra-files entries so release-please sets the version of
the agentex-client and agentex-sdk entries in uv.lock.
- Refresh uv.lock to 0.28.5.
- Run uv sync --locked in the CI lint and build jobs.
The jsonpath filter matches both @.name and @.name.value because
release-please 16.18.0 runs jsonpath over a tagged TOML tree where each
value is wrapped as {start, end, value}.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018gtTYcnigSuJ6qquhhDzxg
danielmillerp
approved these changes
Oct 30, 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 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.
Drift
release-please bumps
pyproject.tomlandadk/pyproject.toml, but it never updateduv.lock. After the 0.28.5 release,uv.lockon main still listsagentex-clientandagentex-sdkat 0.28.4. Before #556 the lock said 0.21.0 while the packages were at 0.28.4. CI runsuv syncwithout--locked, so CI did not catch the drift.Fix
release-please-config.json: each package gets atomlextra-files entry foruv.lock. The root package sets theagentex-clientversion. Theadkpackage sets theagentex-sdkversion (path/uv.lock, relative to the repo root). release-please merges the two into one update ofuv.lock.@.nameor@.name.value. release-please 16.18.0 runs jsonpath over a tagged TOML tree, where each value is{start, end, value}, so a plain@.namefilter matches nothing. The second clause keeps the filter correct if a later release-please passes plain values.uv.lock: refreshed with uv 0.10.2 (the CI version). Only the two workspace version lines change, 0.28.4 to 0.28.5.ci.yml: the lint and build jobs now runuv sync --locked, so a stale lock fails CI. The release PR stays green because release-please now updates the lock in the same PR.Checks
uv lock --check(uv 0.10.2) passes.GenericTomlupdater with these jsonpaths onuv.locklocally. It changed only lines 18 and 94, and kept the formatting.release-please release-pr --dry-runagainst this branch listsuv.lockin the updates as one composite updater, with no "No entries modified" warning.Note
The
trufflehog-bypass.ymlworkflow failed on main at 16:45 UTC today. That workflow runs on PR comments and has failed on each comment since at least 2026-10-26 with "a workflow file issue". It is not related to this change.Per CONTRIBUTING.md, merge only while staging
mainis an ancestor of productionmain, then runstlc-sync.ymlin scaleapi/scale-agentex.🤖 Generated with Claude Code
https://claude.ai/code/session_018gtTYcnigSuJ6qquhhDzxg


Confidence Score: 5/5
The PR appears safe to merge; no actionable issue was found.Summary
This PR keeps workspace release versions aligned with
uv.lock.Reviews (1) · Last reviewed commit: "chore(release): keep uv.lock in sync wit..." · Reviewed by Greptile