Repository navigation
Separate playwright deps into a dedicated tag - #324
Merged
Merged
Conversation
AdrienClairembault
force-pushed
the
remove-npx-cache
branch
from
October 6, 2026 08:49
560cb60 to
c59527b
Compare
Member
Author
|
I think the CI failures are expected here? |
Member
|
Not totally certain by looking at the outpute errors : I assume it's because the first image isn't build/publish yet |
cedric-anne
approved these changes
Oct 6, 2026
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.
Split playwright into a separate tag so we don't include 400mb of dependencies into the base image.
This will speed up CI jobs that do not need them as the image will be much lower to download (the size is reduced by almost half).
No changes for the plugin CI (it will use the playwright variant so we are sure to not break them, the plugins maintainers can make another PR later if they wish to benefit from it).
For the core CI, I guess it will go red once we merge this for the e2e step but we can update it quickly after.