release(v0.15.0): sub-directory-safe exports + agent-ergonomic CLI#400
Merged
Conversation
Bump workspace version 0.14.0 -> 0.15.0 (+ vscode-rivet/package.json, Cargo.lock) and finalize the CHANGELOG [0.15.0] section. Headline: the Zola/HTML export no longer emits absolute `/<prefix>/artifacts/…` links that 404 on a sub-directory deploy (REQ-115/116/118) — that fix merged ~17h after v0.14.0 was tagged, so 0.14.0 users still hit it; this ships it. Also: external `prefix:ID` resolution for hyphenated slugs (REQ-143), the localhost-oEmbed drop (REQ-117), the export build smoke check (REQ-138), query-driven `modify --where` (REQ-141), `list --rank-by-backlinks` (REQ-128), global `--quiet` (REQ-151), `validate --explain` (REQ-125) / `--min-severity` (REQ-137), the salsa status-gate soundness fix (REQ-146), the source-view whole-token match (REQ-144), and the test-results `rivet_tc_id` property (REQ-145). `rivet validate` PASS; `rivet docs check` PASS (VersionConsistency green — all version files at 0.15.0). Refs: REQ-115, REQ-116, REQ-118, REQ-143
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.
Cuts v0.15.0, shipping the 35 commits that accumulated since v0.14.0.
Why now
A user reported that 0.14.0 still emits absolute
/<prefix>/artifacts/…export links that 404 on a sub-directory deploy. Verified: the fix (#377, REQ-115/116/118) merged ~17 h after v0.14.0 was tagged, so it's onmainbut in no released tag. This release ships it. Currentmainis verified clean — the export build smoke check builds 1236 pages under a sub-directorybase_urlwith zero absolute-link leaks.Bumps
Cargo.tomlworkspace0.14.0 → 0.15.0vscode-rivet/package.json → 0.15.0Cargo.lockregenerated[Unreleased] → [0.15.0] - 2026-06-02Headline contents
prefix:IDresolution (REQ-143), localhost-oEmbed drop (REQ-117), export build smoke check (REQ-138)modify --wherebulk (REQ-141),list --rank-by-backlinks(REQ-128), global--quiet(REQ-151),validate --explain(REQ-125) /--min-severity(REQ-137), s-expr error guidance (REQ-142/147)rivet_tc_idproperty (REQ-145); loud-fail ReqIF import (REQ-119/120/123)Verification
rivet validatePASS;rivet docs checkPASS (VersionConsistency green — all version files at 0.15.0). Merge gates CI as usual; tag after merge.🤖 Generated with Claude Code