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

Dockerfile: run yarn install with --frozen-lockfile #47517

Merged
merged 1 commit into from Feb 27, 2023

Conversation

casperisfine
Copy link
Contributor

Similar to BUNDLE_DEPLOYMENT, this flag make sure no package is upgraded or downgraded in the lockfile.

Ref: https://classic.yarnpkg.com/lang/en/docs/cli/install/

If you need reproducible dependencies, which is usually the
case with the continuous integration systems, you
should pass --frozen-lockfile flag.

FYI: @rubys @zzak @dhh @matthewd

Similar to BUNDLE_DEPLOYMENT, this flag make sure no package
is upgraded or downgraded in the lockfile.

Ref: https://classic.yarnpkg.com/lang/en/docs/cli/install/

> If you need reproducible dependencies, which is usually the
> case with the continuous integration systems, you
> should pass `--frozen-lockfile` flag.
@rails-bot rails-bot bot added the railties label Feb 27, 2023
@dhh
Copy link
Member

dhh commented Feb 27, 2023

This is a replacement for BUNDLE_DEPLOYMENT or?

@casperisfine
Copy link
Contributor Author

No, bundler and yarn are totally independent, what I was trying to say is that this is the same kind of option than BUNDLE_DEPLOYMENT but for yarn.

All packages managers have a similarlish option that should be used for CI / production etc.

@rubys
Copy link
Contributor

rubys commented Feb 27, 2023

Fine with me. Already included in #47506

@dhh
Copy link
Member

dhh commented Feb 27, 2023

Ha, I read "yarn" as "bundler" in my head! All good.

@byroot byroot merged commit 0d1927c into rails:main Feb 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants