Skip to content

chore(release-notes): mark v0.414.0 released - #689

Open
bh679 wants to merge 1 commit into
mainfrom
chore/mark-v0.414.0-released
Open

chore(release-notes): mark v0.414.0 released#689
bh679 wants to merge 1 commit into
mainfrom
chore/mark-v0.414.0-released

Conversation

@bh679

@bh679 bh679 commented Jul 10, 2026

Copy link
Copy Markdown
Owner

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:

burn-without-reading-advancement (logged for v0.415.0, merged to main after v0.414.0 was already built/published) is intentionally left released: false for the next release.

No code changes — changelog.json only.

Test plan

  • Diff reviewed: exactly 3 entries flip to 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.
  • N/A build/tests — data-only ledger fix.

🤖 Generated with Claude Code

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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant