chore(release): cut v0.5.0 — version bump, changelog date, docs freeze - #426
Merged
Conversation
The section carried 6 entries for 20 merged issues. Adds the 13 user-facing changes that were missing, in the existing house style. Fixes are limited to behavior that shipped before this cycle (#334, #336, #337). Fixes to code introduced within this cycle are deliberately excluded — the flaky interrupt test, the @Injectmocks refactor, and the S5850/coverage fixes squashed into #420 — since none of them ever reached a release. #136 is likewise omitted: test hardening with no user-facing behavior. New Performance and Dependencies sections follow the 0.4.0 precedent of extending the standard headings. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Bumps pom to 0.5.0, dates the changelog section 2026-07-26, and freezes the outgoing docs. The 0.4.0 docs archive was never taken — versions.json listed current as v0.4.0 with archives stopping at 0.3.1. Because the site expands include markers at archive time and README has since gained v0.5.0 options, archiving the working tree would have produced a "v0.4.0" archive describing v0.5.0. The snapshot is therefore taken from the v0.4.0 tag's content, verified by REVIEW_CI_GATING being absent from it. current.label now reads v0.5.0. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
🤖 ThrillhouseBot PR SummaryWhat this PR doesPrepares the v0.5.0 release: bumps the version in pom.xml (though not visible in this diff snippet), dates the changelog section, and freezes the v0.4.0 documentation archive by copying ten pages and assets from the v0.4.0 tag, updating versions.json to list the archive and set current to v0.5.0.
|
| File | Change | Summary |
|---|---|---|
CHANGELOG.md |
Modified | Adds the [0.5.0] release section with summary, added/changed/fixed/performance/dependencies entries, and leaves an empty [Unreleased] above it. |
website/src/assets/0.4.0/icon.png |
Added | Adds the v0.4.0 icon asset. |
website/src/assets/0.4.0/live-streaming.png |
Added | Adds the dashboard streaming screenshot asset. |
website/src/assets/0.4.0/pr-approval.png |
Added | Adds the PR approval screenshot asset. |
website/src/content/docs/0.4.0/architecture.md |
Added | Adds the architecture overview, including Mermaid diagrams of the review flow. |
website/src/content/docs/0.4.0/commands.md |
Added | Adds the commands reference table and descriptions. |
website/src/content/docs/0.4.0/comparison.md |
Added | Adds the comparison page against other code-review tools. |
website/src/content/docs/0.4.0/configuration.md |
Added | Adds the configuration reference with environment variable tables and AI settings. |
website/src/content/docs/0.4.0/contributing.md |
Added | Adds the contributing guide with development setup and CI bar. |
website/src/content/docs/0.4.0/feedback.md |
Added | Adds the finding feedback documentation (data model, privacy, retention). |
website/src/content/docs/0.4.0/getting-started.md |
Added | Adds step-by-step getting-started guide for creating the GitHub App and running with Docker Compose. |
website/src/content/docs/0.4.0/index.md |
Added | Adds the v0.4.0 landing page with a feature list and navigation to other docs. |
website/src/content/docs/0.4.0/providers.md |
Added | Adds the AI providers guide with sample configuration and a table of providers. |
website/src/content/docs/0.4.0/review-eval.md |
Added | Adds the review-quality evaluation protocol for post-deploy testing. |
website/src/content/versions/0.4.0.json |
Added | Adds the sidebar configuration for the v0.4.0 documentation. |
website/versions.json |
Modified | Updates the current version label to v0.5.0 and adds v0.4.0 to the versions list. |
…and 1 more file(s).
Risk Assessment
| Risk | Count |
|---|---|
| 🔴 Critical | 0 |
| 🟠 High | 0 |
| 🟡 Medium | 0 |
| 🔵 Low | 0 |
No new issues found in this PR, but the review cannot be approved until CI is confirmed green.
⚠️ CI Checks Status
Some checks are still pending or have failed:
| Check | Type | Status | Detail |
|---|---|---|---|
| test | check-run | ⏳ Pending | - |
| trivy | check-run | ⏳ Pending | - |
| format | check-run | ⏳ Pending | - |
| changes | check-run | ⏳ Pending | - |
| actionlint | check-run | ⏳ Pending | - |
| frontend | check-run | ⏳ Pending | - |
| dependency-review | check-run | ⏳ Pending | - |
| build | check-run | ⏳ Pending | - |
Automated review by ThrillhouseBot. Reply with /review to re-run.
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
Release preparation for v0.5.0, dated 2026-07-26.
pom.xml—0.4.1-SNAPSHOT→0.5.0(the only place the version appears).CHANGELOG.md—[Unreleased]becomes[0.5.0] — 2026-07-26with a summary paragraph in the0.4.0 style, and a fresh empty
[Unreleased]is left above it for the next cycle.versions.jsoncurrent.label→v0.5.0.The 0.4.0 archive was never taken
versions.jsonlistedcurrent: v0.4.0with archives stopping at 0.3.1, so 0.4.0 was releasedwithout being frozen.
That matters for how it gets archived now.
archive-docs-version.mjsexpands the<!-- include: -->markers at archive time, and README has since gained v0.5.0 options — sorunning it against the working tree would have produced a directory labelled "v0.4.0" that documents
REVIEW_CI_GATING,REVIEW_BLOCKING_STRICTNESSand the rest. Users clicking v0.4.0 would get 0.5.0docs.
The snapshot is therefore taken from the
v0.4.0tag's content — README,docs/,CONTRIBUTING.mdand the docs pages restored to the tag, archived, then reverted. Verified byREVIEW_CI_GATINGreturning 0 matches in the archived README content, against 1 in the live one.Ten pages archived under
website/src/content/docs/0.4.0/, with matching assets andsrc/content/versions/0.4.0.json.One thing that surfaced while doing it: the
v0.4.0tag containsdocs/REVIEW_EVAL.md, which hassince been deleted on both
mainandrelease/v0.5.0. Restoring the tag temporarily resurrected itand six archived copies; those were removed before committing, and the old 0.1.0–0.3.1 archives are
byte-identical to before. The 0.4.0 archive keeps its copy, which is correct — it shipped in 0.4.0.
Related Issues
N/A — release preparation.
Depends on #425 (the changelog gap entries). This branch is stacked on it, so its diff will show
those entries until #425 merges. Merge #425 first and this reduces to the release-prep commit alone.
How Has This Been Tested?
Manual testing
./mvnw validatepasses on the bumped pomversions.jsonparses;current: v0.5.0, 7 archived versionsArchived pages contain expanded content, not include markers (
AUTO_REVIEW_MIN_INTERVALpresent inthe archived configuration page, 0 include markers left)
git statusconfirms the only tracked changes arepom.xml,CHANGELOG.md,versions.jsonandthe new 0.4.0 archive — no edits to existing archives
Not done here
Publishing the GitHub Release itself (which triggers the Pages deploy) — that is the manual step once
this and #425 are on
release/v0.5.0. The 21 milestone issues also still need closing by hand, sinceFixes #Ndoes not fire on non-default-branch merges.Checklist