docs(changelog): back-fill 0.9.7 and 0.10.0 entries - #85
Merged
Conversation
The <changelog> in xar-assembly.xml stopped at 0.9.6, so the two most recent releases shipped without entries. public-repo renders a package's changelog from the repo.xml built out of this file — not from the GitHub release notes — so 0.10.0 is currently published there advertising 0.9.6 as its newest change. Adds both missing entries, drawn from the corresponding GitHub release notes, in the existing newest-first order and markup style. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Up to standards ✅🟢 Issues
|
duncdrum
approved these changes
Aug 31, 2026
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
2 participants
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.
[This PR was prompted by Joe, drafted by Claude Code, and reviewed by Joe.]
Why
The
<changelog>inxar-assembly.xmlstopped at 0.9.6, so the last two releases shipped without entries. That matters more than it looks: public-repo renders a package's changelog from therepo.xmlbuilt out of this file, not from the GitHub release notes. The 0.10.0 artifact now published on public-repo therefore advertises 0.9.6 as its newest change.Since the published
.xaris byte-pinned and already resolving for eXist 7 clients, this is a forward fix rather than a re-upload: the next release carries the full history again.What
Two
<change>entries, in the existing newest-first order and markup style, drawn from the corresponding GitHub release notes:/api/search; langservice completions and signature help; the binary-safe/api/db/resourceconsolidation (feat(db): consolidate resource content onto a binary-safe /api/db/resource #59);.xarinstall by multipart upload; external variable binding on/api/query; the fix roll-up; and the contract-version move to 0.14.0 with its new CI guard.context-item/context-pathon/api/query(feat(query): add context-item / context-path to POST /api/query #41); mime auto-detection on resource store (fix(db): auto-detect mime from extension when mime-type is omitted #34);documentURI/nodeIdin query results (fix(cursor): populate documentURI / nodeId for stored-doc nodes (#40) #43).No code, no contract change —
modules/api.jsonis untouched, so the API version guard doesn't apply.Verification
xmllint --noout xar-assembly.xmlpasses, and the entries render in the same shape as their neighbors.