Repository navigation
fix(canary): compact nx affected JSON for GITHUB_OUTPUT - #1213
Merged
Merged
Conversation
ryanmcafee
enabled auto-merge
October 7, 2026 18:40
VDubber
approved these changes
Oct 7, 2026
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.
Canary release on #1212 fails at "Detect affected packages":
nx show projects --jsonprints multi-line JSON andGITHUB_OUTPUTrejects it (Invalid format). #1193 fixed this under lerna; the nx switch in #1196 regressed it. Pipe throughjq -cand stop masking nx errors as "no changes".Since
issue_commentworkflows run frommain, this must merge before/canary-releaseon #1212 can succeed.Failed run: https://github.com/JupiterOne/sdk/actions/runs/37663172433
JIRA: https://jupiterone.atlassian.net/browse/PLATENG-1343