From aa93c4ad57b57fc3afcf209509fb994c1f9d184e Mon Sep 17 00:00:00 2001 From: DemchaAV Date: Mon, 13 Jul 2026 15:19:45 +0100 Subject: [PATCH] docs(changelog): drop the premature v2.0.1 Planned entry MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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. --- CHANGELOG.md | 11 ----------- 1 file changed, 11 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index c5403c24..e1bcf89e 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -3,17 +3,6 @@ All notable changes to GraphCompose are documented here. Versions follow semantic versioning; release dates are ISO 8601. -## v2.0.1 — Planned - -### Build - -- The binary-compatibility gate (japicmp) now **enforces** backward compatibility - against the published `2.0.0` baseline: an accidental binary-incompatible change to - the public API fails the build instead of only being reported. Development proceeds - on the `2.0.1-SNAPSHOT` line, so the gate compares the working tree against that - baseline and catches a regression before it can ship in a 2.x update. Source-level - incompatibilities remain report-only for now. - ## v2.0.0 — 2026-07-13 The 2.0 development line. Binary-breaking by design — japicmp runs report-only