docs: prepare the v0.6.4 release — changelog, docs freeze, version bump - #743
Merged
Conversation
Writes the [0.6.4] changelog section, freezes the 0.6.3 docs version from its own tag, and sets the release version in pom.xml.
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
Contributor
🤖 ThrillhouseBot PR SummaryWhat this PR doesPrepares the v0.6.4 release: adds a dated [0.6.4] changelog section covering the four post-0.6.3 fixes (#729, #730, #731, #735), archives the full v0.6.3 documentation set (nine pages, sidebar JSON, image assets), moves versions.json's current label to v0.6.4 while registering 0.6.3 as an archived version, and — per the PR description, with pom.xml withheld from review — bumps the Maven version from 0.6.4-SNAPSHOT to 0.6.4. Description vs. ImplementationNo mismatch found between the PR description and the change. Changes Overview
Changed Files
…and 1 more file(s). Risk Assessment
No new issues found in this PR, but the review cannot be approved until required CI is confirmed green.
|
| Check | Type | Status | Detail |
|---|---|---|---|
| format | check-run | ⏳ Pending | - |
| trivy | check-run | ⏳ Pending | - |
| frontend | check-run | ⏳ Pending | - |
| test | check-run | ⏳ Pending | - |
| dependency-review | check-run | ⏳ Pending | - |
Automated review by ThrillhouseBot. Reply with /review to re-run.
thrillhousebot
Bot
added
documentation
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.
What type of PR is this?
Description
The manual release-prep steps from
docs/RELEASING.md, in one PR.Changelog. Writes the
[0.6.4]section covering the four fixes merged since v0.6.3, all found by the audit of that release: #729 (a rescued finding announced as lost), #730 (a shortRetry-Afterbypassing the content-creation floor), #731 (an unbounded error body scanned for credentials, plus the redaction narrowing that bounding introduced), and #735 (duplicate verdict ids drifting between the audit and its coverage count). Entries follow the file's established voice and keep the measured numbers.Docs freeze. Archives the 0.6.3 docs version per the procedure #715 added: snapshot taken from the v0.6.3 tag so the archived pages carry that release's expanded includes rather than the working tree's, then
npm run docs:archive -- 0.6.3, working docs restored from HEAD, andcurrent.labelmoved to v0.6.4. The post-restoregit statuswas clean — only the archive artifacts andversions.json, nothing resurrected.Version.
pom.xmlmoves from0.6.4-SNAPSHOTto0.6.4, the versionrelease.ymlchecks against the tag.Related Issues
Release preparation for v0.6.4. Refs #715 (freeze procedure).
How Has This Been Tested?
npm run buildrenders the archived0.6.3/pages, including the mermaid-heavy architecture page, alongside the current docs. The changelog section sits immediately after[Unreleased]in the dated-heading formatrelease.yml's note extraction expects.Checklist
Additional Notes
The changelog section is dated 2026-08-16; if the tag is cut on a later day, bump the date before tagging (
release.ymlmatches on version, not date).After merge the release is
git tag -a v0.6.4 <merge-commit> -m "Release v0.6.4"and a tag push — tag pushes are refused from the environment this was prepared in, so that step is manual.