Skip to content
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

Build: Disable yarn immutable install by default during E2E tests #14568

Merged
merged 1 commit into from
Apr 12, 2021

Conversation

gaetanmaisse
Copy link
Member

What I did

When running the E2E tests we are doing a fresh install of Yarn using the latest version; as of Yarn 3.0.0 rc1 a behaviour on dep install has been updated:

The enableImmutableInstalls will now default to true on CI (we still recommend to explicitly use --immutable on the CLI).
You can re-allow mutations by adding YARN_ENABLE_IMMUTABLE_INSTALLS=false in your environment variables.

So I updated the Yarn config used in the E2E to be able to properly bootstrap the different projects.

For details, see https://github.com/yarnpkg/berry/blob/master/CHANGELOG.md#300-rc1

How to test

  • CI should be back to 🟢

@gaetanmaisse gaetanmaisse added the maintenance User-facing maintenance tasks label Apr 12, 2021
@gaetanmaisse
Copy link
Member Author

@shilman, self-merging to fix CircleCI checks on next, other CI improvements and fixes will be done with #14522

@gaetanmaisse gaetanmaisse merged commit c64bccb into next Apr 12, 2021
@gaetanmaisse gaetanmaisse deleted the tech/fix-yarn-config-in-e2e branch April 12, 2021 18:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance User-facing maintenance tasks
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants