chore(release-notes): mark v0.414.0 released - #689
Open
bh679 wants to merge 1 commit into
Open
Conversation
release.yml's automated mark-released step failed on this release (rebase conflict against a concurrently-merged changelog append) — recreating its intended effect by hand, scoped to exactly the 3 entries shipped in v0.414.0 (bookshelf-default-loot, antizombiesroom-min-level, book-carriage-signature). Leaves burn-without-reading-advancement (v0.415.0, merged after this release was already built/published) untouched for the next release. Co-Authored-By: Claude Sonnet 5 <[email protected]>
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
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.
Summary
release.yml's automated "Mark changelog entries released" step failed on the v0.414.0 release run — the GitHub Release, wiki, Modrinth, CurseForge, and both modpacks all published successfully, but the final ledger-flip commit hit a rebase conflict against a concurrently-merged changelog append and never landed. Discord notification was also skipped as a downstream consequence.This PR recreates that step's intended effect by hand, scoped to exactly the 3 entries that were actually in the v0.414.0 build:
bookshelf-default-loot(feat: default bookshelf loot + texture sync #682)antizombiesroom-min-level(feat: default bookshelf loot + texture sync #682)book-carriage-signature(feat: stamp signed books with the carriage they were signed in #683)burn-without-reading-advancement(logged for v0.415.0, merged to main after v0.414.0 was already built/published) is intentionally leftreleased: falsefor the next release.No code changes —
changelog.jsononly.Test plan
released: true/released_in: "v0.414.0"/ stamped with the real GitHub Release publish timestamp (2026-07-10T08:02:14Z); the 4th (newer) unreleased entry is untouched.🤖 Generated with Claude Code