chore(deps): bump pulseengine/rivet from 0.17.0 to 0.22.1

[dependabot]

Bumps pulseengine/rivet from 0.17.0 to 0.22.1.

Release notes

Sourced from pulseengine/rivet's releases.

Rivet v0.22.1

What's Changed

• plan(v0.23): traceability-evidence slices (release: v0.23.0) by @​avrabe in pulseengine/rivet#609
• feat(schema): declare cited-source on verification types (REQ-236 pt1, #556) by @​avrabe in pulseengine/rivet#611
• fix(modify): set-release no longer corrupts a folded scalar with a blank line (#613) by @​avrabe in pulseengine/rivet#614
• chore(release): v0.22.1 — fix --set-release folded-scalar corruption (#613) by @​avrabe in pulseengine/rivet#615

Full Changelog: pulseengine/rivet@v0.22.0...v0.22.1

Rivet v0.22.0

What's Changed

• plan(v0.22): release-planning slices as requirements (release: v0.22.0) by @​avrabe in pulseengine/rivet#602
• feat(list): --release release-planning view (REQ-232, #516) by @​avrabe in pulseengine/rivet#604
• feat(release): rivet release status readiness burn-down (REQ-233, #516) by @​avrabe in pulseengine/rivet#605
• feat(release): rivet release move logged scope change (REQ-234, #516) by @​avrabe in pulseengine/rivet#606
• feat(shard): rivet shard splits a source into per-id files (REQ-235, #490) by @​avrabe in pulseengine/rivet#607
• chore(release): v0.22.0 — Release planning, complete by @​avrabe in pulseengine/rivet#608

Full Changelog: pulseengine/rivet@v0.21.1...v0.22.0

Rivet v0.21.1

What's Changed

• feat(add): per-id directory source layout for conflict-free parallel adds (#490) by @​avrabe in pulseengine/rivet#598
• fix(modify): insert new base fields after trailing block mappings, not inside by @​avrabe in pulseengine/rivet#600
• chore(release): v0.21.1 — fix --set-release artifact corruption by @​avrabe in pulseengine/rivet#601

Full Changelog: pulseengine/rivet@v0.21.0...v0.21.1

Rivet v0.21.0

What's Changed

• fix(test): cfg-gate import-alias reqif test to match the alias (#293) by @​avrabe in pulseengine/rivet#592
• fix(modify): normalize flow-style fields: maps instead of corrupting them (#573) by @​avrabe in pulseengine/rivet#593
• test(verify): guard workspace-layout default marker scan (#574) by @​avrabe in pulseengine/rivet#594
• feat(model): first-class release: field on artifacts (#516) by @​avrabe in pulseengine/rivet#595
• chore(release): v0.21.0 — Authoring & release ergonomics by @​avrabe in pulseengine/rivet#596

Full Changelog: pulseengine/rivet@v0.20.0...v0.21.0

Rivet v0.20.0

What's Changed

• design: SQL virtual-table facade over the live store — CLI-first, no MCP required (REQ-229, DD-068) by @​avrabe in pulseengine/rivet#578
• feat(sql): rivet sql — read-only SQL over the store, no MCP/server (REQ-229) by @​avrabe in pulseengine/rivet#580
• feat(sql): rivet sql write slice — UPDATE via validate + safe YAML edit (REQ-230) by @​avrabe in pulseengine/rivet#582
• design: adopt gluesql-core as the SQL engine, drop bundled SQLite (DD-069, REQ-231) by @​avrabe in pulseengine/rivet#585
• feat(serve): POST /api/v1/sql — read-only SQL over the live server (REQ-229) by @​avrabe in pulseengine/rivet#583
• feat(sql): migrate engine rusqlite → gluesql-core, drop bundled SQLite (REQ-231) by @​avrabe in pulseengine/rivet#586

... (truncated)

Changelog

Sourced from pulseengine/rivet's changelog.

[0.22.1] - 2026-06-27

Fixed

• rivet modify --set-release no longer corrupts an artifact with a folded (>) or literal (|) description: scalar (data loss). A follow-up to the v0.21.1 fix: the insert-position logic consumed a field's block extent but broke on the first blank line — and a block scalar can contain internal blank lines (a folded description: with a blank between paragraphs is very common). So --set-release spliced the new release: key inside the scalar, truncating the description and producing an invalid/misattributed value (silent — modify reported success). The inserter now peeks past blank runs: a blank belongs to the scalar only when a deeper-indented line follows. Reported on real v0.22.0 use (#613). (REQ-004)

[0.22.0] - 2026-06-27

Theme: Release planning, complete — turn the v0.21 release: field into a full, dogfooded workflow. v0.22 is the first rivet release planned, executed, and gated entirely with rivet's own tooling: the plan lives in release:-tagged artifacts, and rivet release status is the authority that called it cuttable.

Added

• rivet list --release <ver> (REQ-232, #516) — the release-planning view; keep only artifacts scoped to a release. Sugar for (= release "<ver>"), composes with --type/--status/--filter.
• rivet release status <ver> (REQ-233, #516) — readiness burn-down: per-status counts of the artifacts in a release, the not-yet-verified set that blocks the cut, and a cuttable verdict. Exits non-zero while not cuttable, so CI can gate a release on it. --format json too.
• rivet release move <id> <ver> (REQ-234, #516) — re-target an artifact to a release as a logged scope decision; reports the old → new transition, idempotent, via the safe modify write-path.
• rivet shard <file> (REQ-235, #490 / DD-070) — split a single-file artifact source into one <ID>.yaml per artifact so existing projects adopt the conflict-free per-id layout (the data-migration half of #490). Reversible and lossless: writes the per-id files, verifies they hold the same id set, backs up the original, reloads the whole project to confirm nothing was lost, and only then removes the backup — restoring + refusing on any mismatch.

[0.21.1] - 2026-06-26

Fixed

• rivet modify --set-release (and any new-base-field insert) no longer corrupts artifacts with a trailing block mapping (data loss). --set-release — shipped in v0.21.0 — spliced the new release: key between a trailing provenance: block and its children, producing invalid YAML so the artifact (and its file-mates) vanished on reload. Since every AI-stamped artifact has a provenance: block, this hit most artifacts the command touched. The inserter now skips a field's full extent, including nested block-mapping children, and places the new field after the whole block. Found by dogfooding the v0.21.0

... (truncated)

Commits

• 0c154fd Merge pull request #615 from pulseengine/release/v0.22.1
• 15ca22f chore(release): v0.22.1 — fix --set-release folded-scalar corruption (#613)
• a2ed930 Merge pull request #614 from pulseengine/fix/613-set-release-folded-scalar
• 0735022 Merge pull request #611 from pulseengine/feat/req-236-cited-source-verification
• 11c12b9 fix(modify): set-release no longer corrupts a folded scalar with a blank line...
• 0f9f5d2 feat(schema): declare cited-source on verification types (REQ-236 pt1, #556)
• 7bac135 Merge pull request #609 from pulseengine/plan/v0.23-traceability-evidence
• 0494f4b plan(v0.23): traceability-evidence slices as requirements (release: v0.23.0)
• 8542cb9 Merge pull request #608 from pulseengine/release/v0.22.0
• b57bde2 chore(release): v0.22.0 — Release planning, complete
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)