🚀 version changed packages#81
Merged
Merged
Conversation
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
2 participants
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.
Releases
@naverpay/commit-helper@2.0.0
Major Changes
c0c01ef: Add
passthroughfor 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"] }, branchfeature/PROJ-1871becomes[PROJ-1871]. Only the keys you list are tagged, so unrelated text likeUTF-8is never mistaken for an issue. Key detection matches Jigit, 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 branchfeature/123, a message you wrote as[#999] fixused to be left alone, but now becomes[#123] [#999] fix. Re-running the hook orgit commit --amendstill never adds your tag twice — this now includes verbatim keys like[PROJ-1871], which the old check could not detect.