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
v7.22.1 #15209
v7.22.1 #15209
Changes from 2 commits
4cd3117
a1201b5
a5eb9e2
5dc0f4e
4a2cc53
4c6e1d5
84a6668
19d1bbe
4abbdd6
f4262ea
bd793b8
f2f12ee
1a0082b
ffc80d6
58628a4
822ecd1
dbd3249
18ca254
02ce159
f3e42ca
618ee17
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check warning on line 10 in CHANGELOG.md
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.
Is it done automatically? because I don't see what modification happend
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.
Agreed, doesn't look like anything changed between
7.22.0
and now. 🤷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'd rather do an empty release and keep all the version numbers in sync, wdyt?
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.
Feel like we are having this debate every two weeks 😆
Our decision in the general meeting a few month ago was to just follow what Lerna updates, to at least be consistent everytime.
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.
Last time when I was releasing we "agreed" to release all packages regardless
#14910 (comment)
Script was updated to reflect that
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.
Ok, the problem/question in this case is clear.
We have two cases:
This difference in approach is somewhat confusing and leads to unstable results. 🤔
This is why I slightly prefer the more manual approach—releasing only the packages with changes to it and skipping in case of dependency bumping.
WDYT about the compromise of not listing the package in the changelog if it doesn't have any changes in the 2nd case? 🤔
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.
That's not what I understand from this discussion.
Lerna can release packages without PR tight to it (if you have a dep that was updated for example).
See #14910 (comment)
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 think we should list the package in the changelog if it was released, even if there are no notable changes.
And whether we should release the package or not – determined by Lerna.
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.
Gotcha, I'm fine with that as well.
But this approach is still creating debates, that is why we can possibly improve it. 👍 🤔
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.
Here we go again 😅
I've opened #15219 to clarify this in the release instructions.
I'm gonna need each team's approval on it to make sure we're on the same page.
If there's anything to discuss or clarify further – leave a comment in #15219