From b46d64b1dde5d481afaa316b9cce46f894079dfc Mon Sep 17 00:00:00 2001 From: Naveen Kumar Date: Thu, 10 Sep 2026 20:33:31 +0800 Subject: [PATCH] git-stats CHANGELOG: the release is 0.1.2, not 0.1.1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The entry was written as 0.1.1 and the release came out as 0.1.2, so the file named a version that does not exist while the one on npm had no entry. `bump=patch` computes off the newest `git-stats-v*` tag, which was `git-stats-v0.1.1-beta.1`. release.yml strips the prerelease suffix and bumps the base, so a beta of 0.1.1 consumes the 0.1.1 number and the next patch is 0.1.2. That is defensible — a beta is a promise about a version — but it means the release a beta anticipated has to be cut with an explicit `-f version=`, never `bump=patch`. Recorded as a comment in the file so the gap between 0.1.0 and 0.1.2 does not read as a lost release. --- packages/git-stats/CHANGELOG.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/packages/git-stats/CHANGELOG.md b/packages/git-stats/CHANGELOG.md index b646668..98f0294 100644 --- a/packages/git-stats/CHANGELOG.md +++ b/packages/git-stats/CHANGELOG.md @@ -1,6 +1,11 @@ # Changelog -## 0.1.1 — 2026-09-10 +## 0.1.2 — 2026-09-10 + + - **Clicking a chip now opens the pull request.** It never did. The label was rendered as an OSC 8 hyperlink and the escape sequence really was in the output —