ci(release-plz): refresh lens/Cargo.lock on the release PR - #34
Merged
Merged
Conversation
Stop the freshness gate from breaking on every timeglyph release. release-plz regenerates only the root workspace lock; `lens/` is a separate workspace (excluded because it is Windows-only) with its own committed Cargo.lock, so after each version bump it still pins the previous `timeglyph` path-dep version and the freshness job's `cargo update --locked --manifest-path lens/Cargo.toml` fails (as it did on 0.9.8, #30). Add a release-plz-pr post-step that refreshes lens/Cargo.lock on the same release PR branch whenever a release PR exists. lens is not published, so this touches no cargo-vet attestations. The step is guarded (exits cleanly if there is no release PR branch) and only commits when the lock actually changes. wasm/bindings-python/fuzz keep no committed lock, so freshness does not gate them and they need no handling. Co-Authored-By: Claude Opus 5 <noreply@anthropic.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
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.
Fixes the recurring
freshnessbreak on every timeglyph release.Cause: release-plz regenerates only the root workspace lock.
lens/is a separate workspace (excluded because it's Windows-only) with its own committedCargo.lock, so after each version bump it still pins the previoustimeglyphpath-dep version — and the freshness gate'scargo update --locked --manifest-path lens/Cargo.tomlfails (as it did on 0.9.8, #30, which needed a manual lock refresh to merge).Fix: a
release-plz-prpost-step that refresheslens/Cargo.lockon the same release PR branch whenever a release PR exists (created or updated). It's the automated form of the manual fix that unblocked #30.wasm/bindings-python/fuzzkeep no committed lock, so freshness doesn't gate them — no handling needed.Note (separate, pre-existing): the lens lock still drifts on third-party deps between releases; that general lock-drift is Renovate
lockFileMaintenanceterritory, not this PR.🤖 Generated with Claude Code