Skip to content

chore(release): v0.29.0 — variant source-linkage + V-model bridge#729

Merged
avrabe merged 1 commit into
mainfrom
release/v0.29.0
Jul 21, 2026
Merged

chore(release): v0.29.0 — variant source-linkage + V-model bridge#729
avrabe merged 1 commit into
mainfrom
release/v0.29.0

Conversation

@avrabe

@avrabe avrabe commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

v0.29.0 — variant source-linkage completeness + dev V-model bridge

Release-prep for v0.29.0. Bumps [workspace.package], Cargo.lock, and the
VS Code extension to 0.29.0; adds the CHANGELOG section.

Scope (all implemented on main)

REQ What shipped
REQ-265 variant source-linkage completeness — (a) honest external source links, (b) no serve variant scope leak, (c) disk-verified variant manifest, (d) export --variant
REQ-266 constraint-solver property-test coverage (previously zero)
REQ-269 shared child (diamond/DAG) no longer mis-reported as a cycle
REQ-270 dev-native verification type so a requirement can mechanically reach verified (dev@0.2.0 → 0.3.0, closes #721)

Self-verify (fresh 0.29.0 binary)

  • cargo build --release — OK
  • rivet validatePASS
  • rivet docs checkPASS (0 violations)

Falsification statement

A dev-only project can now close its own V (a verification verifies a
requirement); a variant-scoped export reflects the variant's field overlay
across all formats incl. the html compliance bundle; a diamond feature model
loads while a genuine cycle is still rejected; and the constraint solver's
Ok verdict is independently checked against every generated constraint.

Next: signed v0.29.0 tag → release.yml + release-npm.yml → verify GitHub assets + npm.

Implements: REQ-265, REQ-266, REQ-270 · Fixes: REQ-269

🤖 Generated with Claude Code

Bumps workspace + Cargo.lock + VS Code extension to 0.29.0 and adds the
CHANGELOG section. Ships v0.29.0 scope:

- REQ-265 variant source-linkage completeness (a: honest external links,
  b: no serve scope leak, c: disk-verified source manifest, d: export --variant)
- REQ-266 constraint-solver property-test coverage (was zero)
- REQ-269 diamond/DAG shared child no longer mis-reported as a cycle
- REQ-270 dev-native `verification` type so a requirement can mechanically
  reach verified (dev@0.2.0 -> 0.3.0, closes #721)

Self-verify with the fresh 0.29.0 binary: build OK, rivet validate PASS,
rivet docs check PASS (0 violations).

Implements: REQ-265, REQ-266, REQ-270
Fixes: REQ-269
@avrabe
avrabe merged commit 4621251 into main Jul 21, 2026
26 of 27 checks passed
@avrabe
avrabe deleted the release/v0.29.0 branch July 21, 2026 20:24
@codecov

codecov Bot commented Jul 21, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

No artifact type can verifies a requirement — the dev↔aspice V-model bridge is missing, so type: requirement can never mechanically reach verified

1 participant