docs(changelog): record the v0.5.0 changes missing from [Unreleased] - #425
Merged
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>
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
🤖 ThrillhouseBot PR SummaryWhat this PR doesAdds 13 missing user-facing changes to the [Unreleased] section of CHANGELOG.md for v0.5.0, including new features, performance improvements, dependency updates, and a missing issue citation. Changes Overview
Changed Files
Risk Assessment
No new issues found in this PR, but the review cannot be approved until CI is confirmed green.
|
| Check | Type | Status | Detail |
|---|---|---|---|
| actionlint | check-run | ⏳ Pending | - |
| format | check-run | ⏳ Pending | - |
| test | check-run | ⏳ Pending | - |
| changes | check-run | ⏳ Pending | - |
| frontend | check-run | ⏳ Pending | - |
| trivy | check-run | ⏳ Pending | - |
| dependency-review | 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! |
|
4 tasks
devops-thiago
added a commit
that referenced
this pull request
Jul 27, 2026
#426) ## What type of PR is this? - [x] 🏗️ CI/CD ## Description Release preparation for **v0.5.0**, dated **2026-07-26**. 1. **`pom.xml`** — `0.4.1-SNAPSHOT` → `0.5.0` (the only place the version appears). 2. **`CHANGELOG.md`** — `[Unreleased]` becomes `[0.5.0] — 2026-07-26` with a summary paragraph in the 0.4.0 style, and a fresh empty `[Unreleased]` is left above it for the next cycle. 3. **Docs freeze** — the 0.4.0 archive, plus `versions.json` `current.label` → `v0.5.0`. ### The 0.4.0 archive was never taken `versions.json` listed `current: v0.4.0` with archives stopping at **0.3.1**, so 0.4.0 was released without being frozen. That matters for *how* it gets archived now. `archive-docs-version.mjs` expands the `<!-- include: -->` markers **at archive time**, and README has since gained v0.5.0 options — so running it against the working tree would have produced a directory labelled "v0.4.0" that documents `REVIEW_CI_GATING`, `REVIEW_BLOCKING_STRICTNESS` and the rest. Users clicking *v0.4.0* would get 0.5.0 docs. The snapshot is therefore taken from the **`v0.4.0` tag's** content — README, `docs/`, `CONTRIBUTING.md` and the docs pages restored to the tag, archived, then reverted. Verified by `REVIEW_CI_GATING` returning 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 and `src/content/versions/0.4.0.json`. One thing that surfaced while doing it: the `v0.4.0` tag contains `docs/REVIEW_EVAL.md`, which has since been deleted on both `main` and `release/v0.5.0`. Restoring the tag temporarily resurrected it and 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? - [x] Manual testing - `./mvnw validate` passes on the bumped pom - `versions.json` parses; `current: v0.5.0`, 7 archived versions - Archived pages contain expanded content, not include markers (`AUTO_REVIEW_MIN_INTERVAL` present in the archived configuration page, 0 include markers left) - `git status` confirms the only tracked changes are `pom.xml`, `CHANGELOG.md`, `versions.json` and the 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, since `Fixes #N` does not fire on non-default-branch merges. ## Checklist - [x] My code follows the project's coding standards - [x] I have performed a self-review of my own code
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
[Unreleased]carried 6 entries for 20 merged issues. This adds the 13 missing user-facingchanges in the existing house style — bold lead-in, issue number, concrete before/after, dogfood
example where one exists.
Added — #123 adversarial failure-mode characterization, #322 CI gating strictness, #323 blocking
strictness, #64 model generation parameters. Also adds the missing
(#110)citation to the existingbug-fix efficacy entry.
Changed — #105 low-confidence findings routed to the summary, #97 exact-arithmetic / "test fails"
cap, #342 dual-gate merge policy (framed as contributor-facing, not operator-facing).
Fixed — #336 force-push anchor invalidation, #337 framework-idiomatic false positives, #334
duplicate CI-pending comment.
Performance (new section) — #386 pure renames excluded from budget, #135 backstop hot-path dedupe.
Dependencies (new section) — the seven bumps merged this cycle.
What was deliberately left out
Per the rule that only pre-0.5 behaviour belongs here, fixes to code introduced within this cycle
are excluded — they never reached a release, so there is nothing for a user to have experienced:
AckReactionServiceTestinterrupt race (test(webhook): remove the interrupt-test race that fails CI with UnnecessaryStubbing #421)@InjectMocksSUT-construction refactor (test: use @InjectMocks for SUT construction (java:S9024) #410)java:S5850regex fix and the coverage follow-up, both squashed into feat(review): adversarially stress-test newly-added parsers/regex/validators for their own failure modes (#123) #420#136 is also omitted — test hardening with no user-facing behaviour. It is the only merged issue
with no entry, and that is intentional.
### Performanceand### Dependenciesare non-standard Keep-a-Changelog headings, but 0.4.0 alreadyset the precedent by adding
### Dependencies.Related Issues
N/A — release preparation for v0.5.0.
How Has This Been Tested?
Verified programmatically that every merged issue is now cited in
[Unreleased]except the oneintentional omission:
Docs-only change; no code touched.
Still open for the release (not in this PR)
pom.xmlis0.4.1-SNAPSHOT— needs the 0.5.0 bump (PR ci(release): fail loudly on bump-PR creation; add RELEASING.md (supersedes #88) #208 hardens that flow).[Unreleased]needs renaming to[0.5.0] — <date>when the release is cut.cd website && npm run docs:archive -- <slug>before 0.5.0docs go current — archives exist for 0.1.0–0.3.0; worth confirming 0.4.0 was done.
Checklist