chore(release): v0.22.2 — dogfooding data-loss/correctness fixes + wasmtime security#635
Merged
Conversation
…smtime security (#625 #627 #628 #629 #632) Patch release from an internal bug-hunt of rivet's own write/validate paths: - #625 (P0 data loss): `modify --add-tag`/`--remove-tag` corrupted a block-style `tags:` list, making the whole file unparseable (REQ-034). - #627: `validate --direct`/MCP counted self-links as closing a rule (false PASS). - #628: `release status` greened an empty/typo'd release scope. - #629: `rivet add` routed non-deterministically across files. - #632 (security): wasmtime 44.0.3 -> 45.0.3 for RUSTSEC-2026-0188. Each fix shipped with a regression test proven to fail without it. 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.
v0.22.2 — Dogfooding hardening patch
Five fixes from an internal bug-hunt of rivet's own write/validate paths, all merged to main and each shipped with a regression test proven to fail without the fix:
modify --add-tag/--remove-tagcorrupted a block-styletags:list → whole file unparseable →rivet listloads 0 artifacts (REQ-034)validate --direct/MCP counted self-links as closing a rule → false PASS (REQ-004)release statusgreened an empty/typo'd release scope (REQ-007)rivet addrouted non-deterministically across files (REQ-007)Version bumped in Cargo.toml/lock + vscode-rivet/package.json; CHANGELOG
[0.22.2]added.rivet validate,rivet docs check(0 violations),clippy --all-targets, and the full rivet-core/rivet-cli test suites pass locally.🤖 Generated with Claude Code