Add isCurrentBranch and publishTo to status --json#40
Merged
Conversation
Enhances the JSON output of `bumpy status --json` with two new fields:
- `isCurrentBranch`: indicates which bump files/releases belong to the
current branch (only present when not on the base branch)
- `publishTo`: array of publish targets per release ("npm", "custom", or empty)
These enable workflows like preview package publishing where you need to
know which npm packages are being changed in the current PR.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Collaborator
|
The changes in this PR will be included in the next version bump.
|
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <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
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
inCurrentBranchfield to bump files and releases inbumpy status --jsonoutput — only present when running on a non-base branch, indicates which items belong to the current PRpublishTargetsfield to each release — an array of publish targets ("npm","custom", or empty for private/skipped packages)inCurrentBranch === true && publishTargets.includes("npm")Test plan
bumpy status --jsonon main (noinCurrentBranchfields present)bumpy status --jsonon a feature branch (fields present with correct values)publishTargetscorrectly reflectspublishCommand,skipNpmPublish, and private package config🤖 Generated with Claude Code