-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Update Lock Files #162
Labels
🎸 Feature
New feature or request
Comments
For anyone running into it, here's a workaround: after each This should prevent it from ever desynchronizing until this issue is fixed. |
For a more minimal command that won't update your dependencies, try |
0.18.0 will have support for |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now, only the metadata file (
Cargo.toml
,pyproject.toml
,package.json
) is updated and not the equivalent lockfile (cargo.lock
,poetry.lock
,package-lock.json
) (the last one might not keep the package version). This leaves inconsistencies that will get updated the next time a user does anything with the package which is less than ideal.Any supported package manager (so Cargo, Poetry, and NPM right now) should not leave any work to-do after bumping a version.
The text was updated successfully, but these errors were encountered: