ci: fix release flow in case of more than one package modified#213
Merged
Conversation
5a4ec7c to
046fa5b
Compare
DayTF
approved these changes
Apr 24, 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.
Fix CI release flow to publish each affected package individually on main
Replaces the single
npx nx print-affectedpublish command in build.yml with a bash script that iterates over each affected project and runsnpx nx run "$PROJECT:publish:package"for each one. The script exits early with a message when no packages are affected, and usesset -eto stop on the first failure.Macroscope summarized 046fa5b.