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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v5.0.0-alpha.24 #24614
v5.0.0-alpha.24 #24614
Changes from 6 commits
85513d3
8874739
76c3d0b
9ccb911
f1e9e93
5730cee
2aaf1d1
02e35d5
98760d6
554b2a9
d000668
6c3ee6c
3fcb3f5
4070002
751eb26
72672e0
19c0a25
6eaae08
49c5b2c
e0e9596
4d48ff1
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The current behavior seems broken to me. It prompts to update every single package. Might be due to lightweight tag usage. We'll see next time if that is the case.
If
lerna
expects to not bump any packages I would expect an explicit option for that. Right now I can only trick it by entering the same version but that's tedious.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lerna is configured to treat the version of the packages individually.
@material-ui/types
needed a different one.In this mode and from what I could gather, Lerna needs one tag per managed version in order to only bump the correct packages in the next release. This was flooding the "Tags" tab view on GitHub. The current situation is the result of a tradeoff: bump everything (cons) in exchange for packages with multiple versions and a single tag (pros).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not talking about tagging but updating
version
in thepackage.json
. I don't understand whylerna
thinks e.g.@material-ui/envinfo
was changed.I suspect it's either caused by lightweight tags or the last tag pointing to a commit that doesn't exist on the
mui-org/material-ui
remote. Hopefully it's not just bad DX.