Fix npm publish build order - #4
Merged
Merged
Conversation
Yarn was resolving ^2.1.0 from the registry during build, before those versions existed. Keep workspace links for the build, then rewrite ranges for the published tarball. Co-authored-by: Cursor <cursoragent@cursor.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
publish.shrewroteworkspace:*to^2.1.0beforeyarn build, so Yarn tried to fetch versions that are not on npm yet (and hid the logs).NODE_AUTH_TOKENso OIDC trusted publishing is not blocked.Test plan
main(do not re-run the failed tag job — it still has the old script)@mui-flexy/core,v5,v6,v7, andv9publish at 2.1.0Made with Cursor