chore(ci): Opt out of Yarn 4 security for our internal packages on e2e CI tests#12046
Merged
Conversation
✅ [V2]
To edit notification comments on pull requests, go to your Netlify project configuration. |
⚡️ Lighthouse report for the deploy preview of this PR
|
Collaborator
Author
|
It installs now, the Yarn PnP failures are something else |
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.
Motivation
Our Yarn Berry tests are failing on CI: https://github.com/facebook/docusaurus/actions/runs/26219679740/job/77151106100?pr=12045
Yarn recently added
npmMinimalAgeGate: 1dby default:npmMinimalAgeGate: 1dthe default yarnpkg/berry#7135Our own packages are safe and do not need to be quarantined when downloaded from our e2e test Verdaccio repository.
Related:
Test Plan
CI