Repository navigation
Conversation
The latest uv rewrites uv.lock with a newer revision, which the release metadata check rejects as a change beyond the version substitution. Amp-Thread-ID: https://ampcode.com/threads/T-01a18b8a-340f-717d-9ca7-6dcf564a065a Co-authored-by: Kevin Longe <kvlonge@gmail.com>
Deploying sqlclean with
|
| Latest commit: |
fc82267
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://9e5ae27d.sqlclean.pages.dev |
| Branch Preview URL: | https://ci-pin-uv.sqlclean.pages.dev |
simulate_release.sh applies Release Please's version edits on a scratch worktree, refreshes the lockfiles like the release workflow and runs the release metadata check. required-version keeps local uv on the pinned line. Release Please now fails first with the missing variable or secret named. Amp-Thread-ID: https://ampcode.com/threads/T-01a18b8a-340f-717d-9ca7-6dcf564a065a Co-authored-by: Kevin Longe <kvlonge@gmail.com>
kvlonge
changed the title
kvlonge
added a commit
that referenced
this pull request
Oct 31, 2026
…edentials early (#3) * ci: pin uv so release lockfile refreshes keep the committed lock format The latest uv rewrites uv.lock with a newer revision, which the release metadata check rejects as a change beyond the version substitution. Co-authored-by: Kevin Longe <kvlonge@gmail.com> * ci: rehearse releases in Verify and name missing release credentials simulate_release.sh applies Release Please's version edits on a scratch worktree, refreshes the lockfiles like the release workflow and runs the release metadata check. required-version keeps local uv on the pinned line. Release Please now fails first with the missing variable or secret named. Co-authored-by: Kevin Longe <kvlonge@gmail.com> ---------
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.
Why
The first release pull request failed twice: Release Please crashed with a raw
appIderror while the release App settings were missing, and then uv 0.13.6 (latest in CI) rewroteuv.locktorevision = 5, which the release metadata check rejected.Changes
setup-uvstep to uv 0.12.9 and set[tool.uv] required-version = ">=0.12.9,<0.13", so local and CI uv write the same lock format.make release-rehearsaland a Release rehearsal job in Verify: apply Release Please's version edits on a scratch worktree, refresh lockfiles as the release workflow does, then run the unchanged strict release metadata check.RELEASE_APP_IDandRELEASE_APP_PRIVATE_KEYexist, without reading the secret, and names the missing one..github/RELEASING.md: one-time setup (release App, PyPI trusted publishers, Cloudflare domains), tooling versions and token limitations.Verification
make verifyand actionlint pass; hygiene scan clean.