-
Notifications
You must be signed in to change notification settings - Fork 16
[Question] Using with yarn's ---frozen-lockfile #195
Comments
Checked renovate's source code, and it turns out that dependency versions are changed using string replace in Hopefully yarn stops the install command from making changes to the lock file, so we get more predictable results. Until then, we simply remove the |
Can we massage the |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed soon if no further activity occurs. |
Can you copy in your exact yarnrc file here so I can use it in testing? |
|
Faced the same problem and it is not clear how to solve it. RenovateBot launched, created 2 PRs, but cannot update artifacts because yarn is launched with a flag |
@Shub1nk Please create an issue in github.com/renovatebot/config-help with logs, exact |
Which Renovate are you using? CLI, App, or Pro
Self-hosted
Which platform are you using? GitHub, GitLab, Bitbucket Azure DevOps
Github
Context
Based on yarnpkg/yarn#4147, we're using
.yarnrc
file in which we set--install.frozen-lockfile true
. This prevents us from introducing changes toyarn.lock
when only installing already added dependencies.However, this requires that to update the
yarn.lock
file when adding or upgrading dependencies we need to useyarn add
oryarn upgrade
command.Today, we noticed that renovate PRs in our codebase fail, with:
What is your question?
Does Renovate Bot simply modify contents of
package.json
without running commands likeyarn upgrade
? Is there a way to change that behavior, or otherwise solve this?I tried replicating locally, and run
yarn add foo
, which updatesyarn.lock
andpackage.json
. I then tried only changing thepackage.json
to add that new package and runningyarn
in that scenario causes, as expected,Your lockfile needs to be updated, but yarn was run with --frozen-lockfile.
The text was updated successfully, but these errors were encountered: