chore(ci): pin rivet v0.22.0 (release-handling) + document the readiness gate (#516)#530
Merged
Merged
Conversation
…ess gate (#516) Bump the CI rivet pin v0.19.0 -> v0.22.0, the version that adds the `rivet release` planning command (#516: `release status` readiness burn-down + `release move` re-targeting, paired with the `release:` artifact field). Validated regression-free before pinning (the #229 lesson — an unvalidated rivet bump silently reddened the gate once): ran the EXACT CI gate locally under v0.22.0 — `rivet validate` non-xref ERROR count 0, `rivet coverage` exit 0, same as v0.19.0. The pinned v0.22.0 tag's commit (8542cb96) is the build validated. Tested the new release-handling end-to-end on synth's artifacts: - `rivet release status vX.Y.Z` with a non-verified scoped artifact -> "✗ NOT cuttable" + the unverified set, exit 1 (CI-gateable); - after the artifact reaches `verified` -> "✓ Cuttable", exit 0; - `--format json` -> {cuttable, not_verified, by_status, total}. (Test scopes were reverted — no artifact was left re-scoped.) docs/release-process.md: add the release-readiness checklist step documenting the `rivet release status` gate and the `release:`-field-vs-`release-vX` tag note. CI/docs only — no codegen, no Rust source; frozen fixtures unaffected. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
What
Adopt the new rivet release-handling for synth's release process: bump the CI rivet pin v0.19.0 → v0.22.0 (the version that adds the
rivet releasecommand — #516:release statusreadiness burn-down +release move, paired with therelease:artifact field) and document the readiness gate indocs/release-process.md.Validated before pinning (the #229 lesson)
An unvalidated rivet bump once silently reddened the gate on unchanged artifacts (0.15.0 promoted a WARN→ERROR). So I ran the exact CI gate locally under v0.22.0 first:
rivet validate→ non-xref ERROR count 0rivet coverage→ exit 0Same result as v0.19.0. The pinned v0.22.0 tag's commit (
8542cb96) is exactly the build validated.Tested the new release-handling end-to-end
On synth's real artifacts:
rivet release status vX.Y.Zwith a non-verified scoped artifact → "✗ NOT cuttable" + the unverified set, exit 1 (CI-gateable);verified→ "✓ Cuttable", exit 0;--format json→{cuttable, not_verified, by_status, total}.Test scopes were reverted — no artifact was left re-scoped.
Docs
docs/release-process.mdgains a release-readiness checklist step documenting therivet release statusgate and therelease:-field-vs-release-vX-tag note.CI/docs only — no codegen, no Rust source; frozen fixtures unaffected.
Refs #516.
🤖 Generated with Claude Code