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

Run Yarn with --frozen-lockfile #1858

Merged
merged 1 commit into from Feb 24, 2020
Merged

Run Yarn with --frozen-lockfile #1858

merged 1 commit into from Feb 24, 2020

Conversation

sonicdoe
Copy link
Contributor

Runs yarn with --frozen-lockfile similar to how npm ci is ran instead of npm install.

This was already implemented in March 2017 with #997, however, it was reverted in #1000 because not all Yarn versions understand this option. Instead of simply reintroducing --frozen-lockfile, this pull request only runs yarn --frozen-lockfile if the Yarn version is at least 0.19.0. npm ci was introduced in a similar way in #1355.

Resolves travis-ci/travis-ci#7395 and this forum post.

@BanzaiMan
Copy link
Contributor

Looks reasonable. Could you open a corresponding docs PR? We can deploy next week.

@sonicdoe
Copy link
Contributor Author

Of course, I’ve opened travis-ci/docs-travis-ci-com#2694.

@BanzaiMan BanzaiMan merged commit ed407cd into travis-ci:master Feb 24, 2020
gitandhub1 pushed a commit to gitandhub1/docs-travis-ci-com that referenced this pull request Jun 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants