Repository navigation
fix: keep stage publish JSON parseable for jq - #4
Merged
Merged
Conversation
stderr WARN lines were merged into the captured --json output and broke jq after a successful stage. Also bump package.json to 4.1.2 to match the already-staged release.
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
pnpm stage publish --jsonstderr out of the captured stdout sojqcan parse the resultpackage.jsonto4.1.2— staging already succeeded on fix: stage npm release outside the git working tree #3 merge (stageId6f228f95-d8b3-45c0-835a-817ccc5ec90d); only the post-stage bump/dist-tag steps were skippedTest plan
prereleasepasses4.1.2:pnpm stage approve 6f228f95-d8b3-45c0-835a-817ccc5ec90d4.1.3without a jq parse failure