Fix npm bin metadata and publish 1.0.2 - #7
Merged
Merged
Conversation
Use an npm-compatible bin path so publish keeps the git-tasks executable and roll the package forward to 1.0.2 after the failed 1.0.1 publish attempt. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.
Summary
git-tasksexecutable1.0.1to1.0.2Test plan
Context
v1.0.1release run reached npm publish but npm warned thatbin[git-tasks]was invalid and removed it during publish preparation1.0.2avoids reusing the failedv1.0.1tag while preserving a publishable CLI package🤖 Generated with Claude Code