chore(deps): bump pulseengine/rivet from 0.16.0 to 0.16.1

[dependabot]

Bumps pulseengine/rivet from 0.16.0 to 0.16.1.

Release notes

Sourced from pulseengine/rivet's releases.

Rivet v0.16.1

What's Changed

• ci: CI reliability — Miri timeout headroom + Verus on ubuntu-latest (v0.17.0, #509) by @​avrabe in pulseengine/rivet#520
• ci(miri): parallelize with cargo-nextest so Miri uses the cores (not 45 min on one) by @​avrabe in pulseengine/rivet#521
• fix(cli): next-id/add hard-fail on a parse-broken source (REQ-216, #518) by @​avrabe in pulseengine/rivet#527
• fix(variant): check --variant accepts the form init scaffolds (REQ-217, #514) by @​avrabe in pulseengine/rivet#528
• release(v0.16.1): #514 + #518 fixes (gale unblock) by @​avrabe in pulseengine/rivet#529

Full Changelog: pulseengine/rivet@v0.16.0...v0.16.1

Changelog

Sourced from pulseengine/rivet's changelog.

[0.16.1] - 2026-06-14

Fixed

• REQ-217 / #514 — variant check accepts the form variant init writes. rivet variant init scaffolds a variant:-wrapped bindings file (and prints the variant check --variant <that file> command to run), but check parsed --variant strictly as the flat {name, selects} form and rejected it with missing field 'name'. VariantConfig::from_yaml_str now accepts both forms across every --variant path, so the init→check happy path works.
• REQ-216 / #518 — mutating commands refuse on a parse-broken source. A source file dropped from the graph by a YAML parse error (merge conflict, manual edit, or an unquoted-colon title pre-REQ-198) is invisible to the loader, so next-id allocated IDs against the partial store — colliding with the unparsed file's artifacts (the report saw five artifacts share one id) — and add exited 0 on the error. rivet next-id and rivet add now hard-fail (non-zero) with an actionable message when any source failed to parse; read-only commands still warn-and-continue.

Commits

• b3bec52 release(v0.16.1): bump version + CHANGELOG [0.16.1] (#529)
• abb1e24 fix(variant): check --variant accepts the wrapped form init scaffolds (REQ-21...
• 01b4297 fix(cli): next-id/add hard-fail when a source file failed to parse (REQ-216, ...
• 4c51a8b ci(miri): parallelize with cargo-nextest so Miri uses the cores (not 45 min o...
• e60a3a9 ci: CI reliability — Miri timeout headroom + Verus on ubuntu-latest (v0.17.0,...
• See full diff 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)