chore(release): open 2.3.0-SNAPSHOT - #606
Open
DemchaAV wants to merge 1 commit into
Open
Conversation
The cycle open on develop was numbered 2.2.3, a patch. The Stable tier promises that behaviour is preserved across patch releases and additive in minor ones (docs/api-stability.md), and the work queued for this cycle changes rendered output for existing documents, so the release it ships in has to be a minor. Renames the open CHANGELOG entry, bumps every module pom -- including the qa and coverage aggregator children, whose inherited parent version the release cut does not touch on its own -- and points the README release status at the new number. The entries already written under the heading move with it: they ship from the same branch, so they ship in the same release. No published coordinate changes: 2.2.2 remains the latest release, and the README install snippets keep pointing at it.
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.
Why
The cycle open on
developwas numbered2.2.3, a patch.docs/api-stability.md§ 1puts
ParagraphBuilderand the rest of the canonical authoring surface in the Stabletier, and § 2 spells out what that promises: "behaviour is preserved across patch
releases and additive in minor releases."
The work queued for this cycle changes rendered output for documents that already
compile and run today, so the release it ships in has to be a minor. Renaming the
heading is not enough on its own:
VersionConsistencyGuardTest.theOpenChangelogEntryNamesTheVersionUnderDevelopmentreads the real
CHANGELOG.mdagainst the realcore/pom.xmland fails when the openentry and the pom name different releases, or when two entries are open at once. The
heading and the poms have to move together, which is why this is its own change rather
than a line inside the PR that needs it.
What changed
CHANGELOG.md: the open heading becomes## v2.3.0 — Planned. The two entriesalready written under it — the Monogram Sidebar employer fix and the preset-caps
documentation — move with it. They ship from this branch, so they ship in this
release; nothing about them changed.
2.3.0-SNAPSHOT: the root,core,render-pdf,render-docx,render-pptx,templates,testing,wrapper,bundle,examples,benchmarks, and theqaandcoverageaggregator children whoseinherited parent version the release cut does not rewrite on its own.
README.md: the release-status line points atv2.3.0. The install snippets areuntouched — they name the latest published release, which is still
2.2.2.No published coordinate changes and nothing is deployed by this PR.
Verification
Full reactor gate from the root pom:
BUILD SUCCESS, 11 modules. The two guards this change could plausibly break are greenon the new numbers:
VersionConsistencyGuardTest(20 tests) andChangelogVersionParsingTest(25 tests), which together cover both the pom/CHANGELOGagreement and the "second open entry is ambiguous" rejection. japicmp still resolves its
baselines against the published
2.0.0floor and2.2.2, unaffected by the SNAPSHOTnumber.