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

Subcommand update should tell you what packages are outdated and be able to rewrite your manifest file accordingly. #149

Open
u-train opened this issue Jun 12, 2023 · 2 comments

Comments

@u-train
Copy link
Contributor

u-train commented Jun 12, 2023

We should notify the user if there is a newer semver incompatible version of a package which we can't auto upgrade to. The thought process behind this is people will usually wally update blind and may be unaware there is a new major version of a package.

We should also add convenience flags to allow the user to specify if they want to upgrade everything to the latest possible version even if they are semver incompatible or if they do not want any semver incompatible choices. They might have many dependencies and saying yes or no is annoying!

Originally posted by @magnalite in #140 (review)

@magnalite
Copy link
Member

We should maybe move manifest changing into a wally upgrade command to make the behaviour obvious. This is similar to what people have implemented for cargo (via cargo-upgrade as it isn't a native command).

@yrifl
Copy link

yrifl commented Aug 4, 2024

When will UpliftGames implement the update subcommand? 😥😭😭😭

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

No branches or pull requests

3 participants