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

fix(upgrade): Always upgrade compatible dependencies #786

Merged
merged 1 commit into from
Sep 9, 2022

Conversation

epage
Copy link
Collaborator

@epage epage commented Sep 9, 2022

As part of feedback on cargo-upgrade being merged into cargo, we are looking into how we can make upgrade fit into update or be a direct replacement for update. In doing so, the "skip compatible by default" workflow doesn't quite fit the same. Similarly, manifests, in theory, will always match the lock file, so there will be less of a reason to upgrade the manifests only.

We'll need to re-open #552 and #297 until we figure out how we want to handle this.

As part of feedback on `cargo-upgrade` being merged into `cargo`, we are
looking into how we can make `upgrade` fit into `update` or be a direct
replacement for `update`.  In doing so, the "skip compatible by default"
workflow doesn't quite fit the same.  Similarly, manifests, in theory,
will always match the lock file, so there will be less of a reason to
upgrade the manifests only.

We'll need to re-open killercup#552 and killercup#297 until we figure out how we want to
handle this.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant