chore(release): v0.1.16 - #84
Merged
Merged
Conversation
`walk <path> --boundary` on a node that isn't a boundary now says so, instead of returning a bare `service error (404)`. The check runs against this working copy's index before the request, and says as much — a node's kind can change on the branch, so it names `hydrate pull` alongside the neighborhood read rather than asserting a snapshot as fact. An index that predates recorded kinds, or carries a kind this build doesn't know, defers to the server and reports why. `--depth` and the `--boundary` failure mode are now documented in the README and `hydrate guide`. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
rennehan
added a commit
that referenced
this pull request
Jul 29, 2026
`walk <path> --boundary` on a node that isn't a boundary now says so, instead of returning a bare `service error (404)`. The check runs against this working copy's index before the request, and says as much — a node's kind can change on the branch, so it names `hydrate pull` alongside the neighborhood read rather than asserting a snapshot as fact. An index that predates recorded kinds, or carries a kind this build doesn't know, defers to the server and reports why. `--depth` and the `--boundary` failure mode are now documented in the README and `hydrate guide`. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Version bump for v0.1.16.
Cargo.toml+Cargo.lockonly.Why now
v0.1.15 shipped with a broken guard.
walk <behavior> --boundaryreturns a bareservice error (404)there — the check lived in the response renderer, and the server rejects the request first, so it could never run. The fix only reaches users when it's released.The verdict comes from the local index, and the message says so. A node's kind is mutable on the branch, so stating a snapshot as fact would refuse a legitimate read while asserting something false. An index that predates recorded kinds — or carries a kind this build doesn't recognise — defers to the server and reports why.
Also:
--depth(shipped in v0.1.15) is finally documented in the README andhydrate guide, along with the--boundaryfailure mode.Shipped in #83, reviewed by a four-agent fan-out.
After merge
Tag
v0.1.16to publish the five-target release.