docs(release): backfill CHANGELOG + CHANGELOG-at-release standard (v1.23.2)#52
Merged
Conversation
…-at-release standard - Add missing main CHANGELOG entries for v1.22.0 and v1.23.0 - release-process.md §5: entry authored on dev before promotion (single source) - Non-blocking promotion-status advisory when a pending minor lacks an entry - Bump plugin.json to 1.23.2
Owner
Author
|
Squash-merge message (copy verbatim): |
2 tasks
misnaej
added a commit
that referenced
this pull request
Jun 17, 2026
- Bring CHANGELOG v1.22.0/v1.23.0 entries onto dev (matches main after #52) - Bring release-process.md §5 (CHANGELOG-at-release standard) + promotion advisory - dev plugin.json → 1.23.2; one-time catch-up reconciliation per §5
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.
Patch hotfix to
main: repairs the CHANGELOG gap left when v1.22.0/v1.23.0 promoted without entries, and documents+enforces (softly) the steady-state standard so it can't recur.Why a hotfix to main
mainalready shipped v1.22.0 and v1.23.0 (via the #51 lump promotion) butCHANGELOG.mdstopped at v1.21.0 — nothing enforces CHANGELOG updates at release. This is the one-time catch-up (see release-process.md §5 'one-time catch-up exception'). The steady-state flow (below) needs no hotfix.Changes
devbefore promotion; the release branch carries it tomain.devis the single source — never hotfix/back-merge in steady state.--promotion-statusadvisory (origin/dev. Silent for repos with no CHANGELOG. Patch-safe (Pattern C).After merge
v1.23.2on main's squash commit (rolling-next).main → dev(feature branch from dev, merge main) so dev's CHANGELOG matches — the one-time reconciliation. Then both branches align at 1.23.2.Breaking changes
None — advisory is non-blocking, additive.