Give CLI 7.1.0 its own changelog section - #4814
Open
allister-beamable wants to merge 1 commit into
Open
Conversation
cli-7.1.0 (2026-04-16) shipped 166 commits and 750 files - Portal Extensions, zstd websocket compression, inter-service communication and event handling, the content history command suite, Unreal replacement types - with no changelog section of its own. Its entries were written under a heading spelled "## Unreleased" (no brackets) and never promoted to "## [7.1.0]"; when 7.2.0 was cut in June that same block was renamed to [7.2.0], so the content was misfiled rather than lost. Splits it back apart. The 7.1.0 entry set is taken verbatim from the Unreleased block present at the cli-7.1.0 tag, so nothing is invented. The truncated summary-tag bullet is dropped rather than duplicated: it is a cherry-pick twin already documented under [7.0.1], where it actually shipped. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
|
Lightbeam link |
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.
cli-7.1.0(2026-04-16) shipped 166 commits, 750 files, +30185/-2643 - Portal Extensions (proof of concept, planning/deployment, performance tracking), zstd websocket compression, inter-service communication and event handling, thecontent historycommand suite, Unreal replacement types and stubs - with no changelog section of its own.The entries were written. At the
cli-7.1.0tag they sat under a heading spelled## Unreleased, without brackets, and were never renamed to## [7.1.0] - 2026-04-16. When7.2.0was cut in June that same block was renamed to## [7.2.0] - 2026-06-16, so the content was misfiled rather than lost.Surfaced by the changelog backfill of existing production GitHub Releases (see #4812):
cli-7.1.0was one of only two production releases whose Release body could not be populated, and the other (cli-2.0.0) simply predates the changelog. An audit of every production tag against its lane changelog found no other primary-package gaps in the whole history.What this changes
Splits the block back apart. The
[7.1.0]entry set is taken verbatim from theUnreleasedblock present at thecli-7.1.0tag, so nothing is invented and nothing is reworded.The truncated-summary-tag bullet is dropped rather than duplicated: it is a cherry-pick twin already documented under
[7.0.1], where it actually shipped. That is the-twin case runbook step 2 warns about.Companion changes
fix/cli-710-changelog-61x- the same split onrelease/unity-6.1.x.cli-7.1.0GitHub Release body will be regenerated from the corrected changelog.release/unity-6.0.xandrelease/unity-5.1.xcarry the same uncorrected block. Left alone per the runbook rule of backporting only if a line cuts another patch; worth doing if either does.beamable/Changelogs(production branch, feeding changes.beamable.com) also carries it. It is force-overwritten wholesale by the next production release, so it self-heals - but not until then.Prevention
Runbook step 3 already says to rename the
[Unreleased]heading to the version and date it; that runbook postdates this release. With #4812, a version with no changelog section now emits a::warningin the release job, so the next occurrence surfaces at release time rather than years later.