docs(changelog): backport v3.0.0 auto-generated items into repo.xml.tmpl#196
Merged
Merged
Conversation
When v3.0.1 was released, public-repo's changelog tab for fundocs lost the auto-generated items from v3.0.0's `<change>` block (the BREAKING CHANGE de-mavenize headline and the documentation fix that came in via eXist-db#152) — they had been merged in-memory on the v3.0.0 release runner but the script's output is never committed back to master, so the next release (v3.0.1) regenerated repo.xml from the hand-authored template, which held only the eXist-db#178 line. Result: v3.0.0 looked suspiciously thin for a major bump. Manually fold the missing items into the existing `<change version="3.0.0">` block so any subsequent release (v3.0.2+) ships a fuller v3.0.0 row, and public-repo's display recovers the full context. `docs:` prefix → no release triggered by this commit on its own.
line-o
approved these changes
May 29, 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 response was co-authored with Claude Code. -Joe]
After v3.0.1 was published to exist-db.org's public-repo, the changelog tab for fundocs (link) showed v3.0.0 with only one bullet — the hand-authored "Rewrite search queries" line from #178 — even though v3.0.0's own
.xarhad also listed the BREAKING CHANGE de-mavenize headline and thefix(documentation):ngram-index item.The cause is structural:
scripts/update-repo-changelog.jsruns in-memory on the release runner and the modifiedrepo.xml.tmplis never committed back to master (monex-style0.0.0-developmentflow). So when v3.0.1 was released, its.xarregeneratedrepo.xmlfrom the hand-authored template, which only knew about the #178 line for v3.0.0. Public-repo renders the latest.xar's changelog, so the older release rows got retroactively thinned out.This PR folds the missing v3.0.0 items into the hand-authored
<change version="3.0.0">block inrepo.xml.tmpl, so any subsequent release (v3.0.2+) will ship a fuller v3.0.0 row, and public-repo's display will recover the full context the next time a new release is uploaded.The
docs:prefix means this commit on its own won't trigger a release; the backport will surface to public-repo whenever the nextfix:/feat:PR lands.