fix(playwright): bump packages upon new release #29596
Merged
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
thetaPC
changed the title
Sltaaa3bergar
approved these changes
Jun 11, 2024
sean-perkins
approved these changes
Jun 11, 2024
brandyscarney
approved these changes
Jun 11, 2024
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.
Issue number: N/A
What is the current behavior?
Renovate updates the Playwright packages. It's important that the Playwright within Docker and within core are the same version. However, the Playwright version within core does not update when Docker does.
What is the new behavior?
bumpto the Renovate config, this should allow Playwright within core to update regardless if the new version satisfies the range.Does this introduce a breaking change?
Other information
I was unable to test it locally since it will only trigger when the code is within
main.