Skip to content

chore(release): keep uv.lock in sync with release versions - #558

Merged
declan-scale merged 1 commit into
mainfrom
declan-scale/uv-lock-release-sync
Oct 30, 2026
Merged

declan-scale merged 1 commit into
mainfrom
declan-scale/uv-lock-release-sync

Conversation

@declan-scale

@declan-scale declan-scale commented Oct 30, 2026 •

Copy link
Copy Markdown
Contributor

Drift

release-please bumps pyproject.toml and adk/pyproject.toml, but it never updated uv.lock. After the 0.28.5 release, uv.lock on main still lists agentex-client and agentex-sdk at 0.28.4. Before #556 the lock said 0.21.0 while the packages were at 0.28.4. CI runs uv sync without --locked, so CI did not catch the drift.

Fix

  • release-please-config.json: each package gets a toml extra-files entry for uv.lock. The root package sets the agentex-client version. The adk package sets the agentex-sdk version (path /uv.lock, relative to the repo root). release-please merges the two into one update of uv.lock.
  • The jsonpath filter matches @.name or @.name.value. release-please 16.18.0 runs jsonpath over a tagged TOML tree, where each value is {start, end, value}, so a plain @.name filter 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 run uv 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.
  • The config validates against the release-please 16.18.0 config schema.
  • I ran the release-please 16.18.0 GenericToml updater with these jsonpaths on uv.lock locally. It changed only lines 18 and 94, and kept the formatting.
  • release-please release-pr --dry-run against this branch lists uv.lock in the updates as one composite updater, with no "No entries modified" warning.
  • I did not run the test suite. CI runs it.

Note

The trufflehog-bypass.yml workflow 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 main is an ancestor of production main, then run stlc-sync.yml in scaleapi/scale-agentex.

🤖 Generated with Claude Code

https://claude.ai/code/session_018gtTYcnigSuJ6qquhhDzxg

RetriggerView in GreptileConfidence 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.

  • Release updates keep both package versions in the lockfile.
  • Lint and build jobs fail when the lockfile is out of date.

Reviews (1) · Last reviewed commit: "chore(release): keep uv.lock in sync wit..." · Reviewed by Greptile

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
@declan-scale
declan-scale merged commit 9ef0707 into main Oct 30, 2026
48 checks passed
@declan-scale
declan-scale deleted the declan-scale/uv-lock-release-sync branch October 30, 2026 17:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants