fix: release branches miss workspace dependencies#30472
Closed
grabbou wants to merge 1 commit into
Closed
Conversation
36 tasks
Contributor
|
This fix looks good to me. I can’t merge it at fb this week (holidaaays!) but if you make the same PR against the release branch I can merge that for now, then merge this PR into master later. |
cpojer
approved these changes
Nov 25, 2020
Contributor
Author
|
Thanks @cpojer, that was fast! It's okay for now, I am going to test it that we indeed remove |
dulmandakh
approved these changes
Nov 25, 2020
Contributor
|
Closing as we now moved to a proper monorepo and there is no need to cleanup |
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
On the CI, e.g. inside
publish-npm.js, we're missingshelljsdependency, which comes fromrepo-configpackage. This error started happening after introduction of Yarn workspaces.During
bump-oss-version.js, we removeprivateandworkspacessettings, preparing it for publishing. As a result, CI steps testing and running on0.64-stablebranch can potentially fail due to missing dependencies.Such case is
publish-npm.js. There might be other errors too (that we haven't run into yet), because we do some development on release branches as well.A better solution would be to not modify anything while doing
bump-oss-versions.js(just bump them) and remove extraneous properties frompackage.jsonwhile preparing a package.CC: @cpojer