docs(changelog): drop the premature v2.0.1 Planned entry#398
Merged
Conversation
The 2.0.1 development line carries no user-facing change — its only note was the japicmp binary-compatibility enforcement, which is repo-internal tooling already documented in docs/api-stability.md. Advertising a "v2.0.1 — Planned" release with nothing installable is misleading, so drop the entry; the CHANGELOG top is the dated v2.0.0 again. develop stays on 2.0.1-SNAPSHOT — the japicmp gate needs a working version distinct from the 2.0.0 baseline — and a version entry is added when a real user-facing change lands.
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
developis on2.0.1-SNAPSHOT, but the## v2.0.1 — PlannedCHANGELOG entry's only content was one internal### Buildnote about the japicmp binary-compatibility gate. That's repo-internal tooling — no user-facing change — and the policy is already documented indocs/api-stability.md. Advertising a "v2.0.1 — Planned" release with nothing installable is misleading, and it contradicts the hardening plan's conclusion that no 2.0.1 release is warranted.What
Remove the
## v2.0.1 — Plannedentry. The CHANGELOG top is the dated## v2.0.0 — 2026-07-13again.developstays on2.0.1-SNAPSHOT— the japicmp gate short-circuits when the working version equals its2.0.0baseline, so the dev line must remain distinct from the release. A concrete version entry is added when a real user-facing change lands.Tests
VersionConsistencyGuardTest12/12 — the guard anchors install snippets to the latest dated release (2.0.0) for a-SNAPSHOTworking version, so the (undated) Planned entry was never used; removing it changes nothing. No pom or install-snippet touched.