chore(release): prepare v4.12.0 (re-stamped 2026-09-08) - #870
Merged
Conversation
The v4.12.0 section stamped in #855 on 2026-09-03 was never tagged or published — the latest release is still v4.11.0. Rather than leave a second phantom version, this folds the 23 bullets that landed since into the same section, re-dates it to today, and makes it the release cut_release.sh will actually produce (it computes v4.12.0 from the v4.11.0 tag). - CHANGELOG: Unreleased folded into [v4.12.0] - 2026-09-08 (106 bullets), the six duplicate ###-headings left by stacked merges consolidated into Added / Changed / Fixed, and a bullet added for #842 (workflow default model), which merged without one. Fresh empty [Unreleased] above. - DEPLOY.md: new "Container engine: Docker or podman" section for #866. - README: podman in the prerequisites; docs/review-graph.md linked from the Documentation list (it was reachable only from CONTRIBUTING). - OPERATIONS.md: scope note that podman-compose takes the same commands. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Qk88vvuDRJz5Nft2pRNpeY
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.
Release prep for v4.12.0, re-stamped to today.
Why a second v4.12.0 prep
#855 stamped
## [v4.12.0] - 2026-09-03on September 3, but the tag was never cut: there is nov4.12.0git tag, GitHub release, or published image, and the latest release is still v4.11.0 (August 25). That is the same shape as the phantom v4.11.1 that #855 itself cleaned up. Meanwhile 23 more bullets landed under[Unreleased]from today's PR batch (#795, #799, #800, #815, #857, #818, #821, #824, #866) and the model-eval stack.scripts/cut_release.shcomputes the next tag from the latest tag (v4.11.0 → v4.12.0), so the honest fix is to make the v4.12.0 section describe what that tag will actually contain: everything since v4.11.0.What this does
Folds Unreleased into v4.12.0 and re-dates it.
## [v4.12.0] - 2026-09-08, 106 bullets, fresh empty[Unreleased]above. The six duplicate### Fixed/### Addedheadings left by stacked merges are consolidated into one Added, one Changed, one Fixed. Verified programmatically: no bullet lost or duplicated, everything below v4.11.0 byte-identical.Fills one changelog gap. #842 (workflow-level default model, "Model — all steps" on the canvas) merged without a bullet; added under Added. #859 (dependabot-style dev bumps) gets none, matching past sections. Direct commits since v4.11.0 are the four already folded into this section by #855.
Documents podman support (#866). DEPLOY.md gains a Container engine: Docker or podman section (engine and Compose detection order, fully qualified image refs, Compose-level healthchecks, the "stopped stack counts as an existing deployment" behaviour change, and that
podman-composetakes the same subcommands as thedocker composelines in OPERATIONS.md). README prerequisites mention podman; OPERATIONS.md's scope line points at the new section.Links
docs/review-graph.mdfrom the README. It was reachable only from CONTRIBUTING.Operator actions
None beyond the usual upgrade.
git diff v4.11.0..main -- backend/.env.exampleis empty: no new environment variables.compose.yamlchanges since v4.11.0 are theINSTALL_BROWSERbuild arg (documented in #855),docker.io/-qualified image references, and Compose-level healthchecks on api/frontend — all transparent to an image-based upgrade.Worth knowing for the trial deployment: this release carries the August 25 fix that makes "Create account" open the register form on a trial deployment (
f3d0a48f, previously filed under the phantom v4.11.1). vandalizer.uidaho.edu is on v4.11.0 and does not have it until this is cut and deployed.Checks
ci.yamlandrelease.yaml; the only workflow change since v4.11.0 is the newintegration-llm.yaml, which the tag workflow does not depend on.backend-static/cigatesmake release-checkruns on the tag.After merge
scripts/cut_release.sh --dry-runthenscripts/cut_release.shon a clean, syncedmain— your step, as before. It should printNext tag: v4.12.0; if it prints anything else, stop and tell me before confirming.🤖 Generated with Claude Code
https://claude.ai/code/session_01Qk88vvuDRJz5Nft2pRNpeY