From 2421533b1d0b1aeedd18644e2dd5a9bfd9c46107 Mon Sep 17 00:00:00 2001 From: npayfebot Date: Thu, 2 Jul 2026 02:30:44 +0000 Subject: [PATCH] =?UTF-8?q?=F0=9F=93=A6=20bump=20changed=20packages=20vers?= =?UTF-8?q?ion?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .changeset/commit-helper-passthrough.md | 9 --------- packages/commit-helper/CHANGELOG.md | 10 ++++++++++ packages/commit-helper/package.json | 2 +- 3 files changed, 11 insertions(+), 10 deletions(-) delete mode 100644 .changeset/commit-helper-passthrough.md diff --git a/.changeset/commit-helper-passthrough.md b/.changeset/commit-helper-passthrough.md deleted file mode 100644 index 00fc85b..0000000 --- a/.changeset/commit-helper-passthrough.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -"@naverpay/commit-helper": major ---- - -Add `passthrough` for Jira/Linear-style issue keys, and make re-tagging match only your branch's own tag. - -**`passthrough`** — list your project keys, and branches that already contain the full key are tagged as-is. With `{ "passthrough": ["PROJ"] }`, branch `feature/PROJ-1871` becomes `[PROJ-1871]`. Only the keys you list are tagged, so unrelated text like `UTF-8` is never mistaken for an issue. Key detection matches [Jigit](https://marketplace.atlassian.com/apps/1217129), so a branch links the same way in Jira and here. - -**Breaking change** — commit-helper skips a commit that is already tagged, and what counts as "already tagged" changed. Before, *any* `[#…]` tag in the message stopped it. Now, only *your current branch's own* tag does. For example, on branch `feature/123`, a message you wrote as `[#999] fix` used to be left alone, but now becomes `[#123] [#999] fix`. Re-running the hook or `git commit --amend` still never adds your tag twice — this now includes verbatim keys like `[PROJ-1871]`, which the old check could not detect. diff --git a/packages/commit-helper/CHANGELOG.md b/packages/commit-helper/CHANGELOG.md index 63ad3fd..c3526e6 100644 --- a/packages/commit-helper/CHANGELOG.md +++ b/packages/commit-helper/CHANGELOG.md @@ -1,5 +1,15 @@ # @naverpay/commit-helper +## 2.0.0 + +### Major Changes + +- c0c01ef: Add `passthrough` for Jira/Linear-style issue keys, and make re-tagging match only your branch's own tag. + + **`passthrough`** — list your project keys, and branches that already contain the full key are tagged as-is. With `{ "passthrough": ["PROJ"] }`, branch `feature/PROJ-1871` becomes `[PROJ-1871]`. Only the keys you list are tagged, so unrelated text like `UTF-8` is never mistaken for an issue. Key detection matches [Jigit](https://marketplace.atlassian.com/apps/1217129), so a branch links the same way in Jira and here. + + **Breaking change** — commit-helper skips a commit that is already tagged, and what counts as "already tagged" changed. Before, _any_ `[#…]` tag in the message stopped it. Now, only _your current branch's own_ tag does. For example, on branch `feature/123`, a message you wrote as `[#999] fix` used to be left alone, but now becomes `[#123] [#999] fix`. Re-running the hook or `git commit --amend` still never adds your tag twice — this now includes verbatim keys like `[PROJ-1871]`, which the old check could not detect. + ## 1.2.2 ### Patch Changes diff --git a/packages/commit-helper/package.json b/packages/commit-helper/package.json index ef06359..bc59b01 100644 --- a/packages/commit-helper/package.json +++ b/packages/commit-helper/package.json @@ -1,6 +1,6 @@ { "name": "@naverpay/commit-helper", - "version": "1.2.2", + "version": "2.0.0", "description": "help your commit in git", "main": "./dist/index.js", "repository": {