-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[7.17][Ops] Sync babel-related versions with main #161278
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
f7ba584
chore: sync babel-related versions with main
delanni 83c8cdd
chore: add some more dependencies, and add them to kbn dev utils
delanni 2d130b9
[CI] Auto-commit changed files from 'yarn kbn run build -i @kbn/pm'
kibanamachine 344ad5c
chore: add fix for storybook for babel 7.21
delanni 5eb0a47
chore: sync a few more babel-related deps from main, fix tests
delanni f2c9118
Merge branch '7.17' into sync-babel-version-with-main
delanni File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
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.
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.
Should these versions match
@babel/core
? Its the same onmain
so maybe we address it there first and backport?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.
Maybe you're right - I wonder why it is not in sync on master - @mistic do you have any opinions on syncing the
@babel/*
versions to that of the core?What I also wonder, the specifiers with
^
should be able to move around within the same major version, in theory they could resolve all to the same version.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.
Thats a good point. I think we can move on with this PR as it is and then open a fix on main to this mismatch with babel/core that we can then backport to the other branches.
Regarding the second question and after thinking a little about this, I think whats is more important is to keep at least what we define in the package.json in sync across the branches, having that said we can keep the
^
and afford to have little differences in the yarn.lock because if we upgrade those things at the same time they will tend to be exact the same in every branch without us to have to be completely strict in the package.json.Let me know what you think about 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.
👍 I believe the versions aren't always in sync (e.g. core is 7.22.8 and register is 7.22.5 currently), no-op releases are skipped but future releases will skip numbers to align, if anyone's curious as to why.