Dry-runs, an upgrade confirmation prompt, and an option to view the changelog about ferium

[JustSimplyKyle]

Yep, normally release description are served as small changelogs

[theRookieCoder]

But this would just print out the changelog of the latest version? It wouldn't actually print the changes made since the version that was previously installed. And should this be normal behaviour, or an opt-in through a --verbose flag?

[JustSimplyKyle]

--verbose
Yes, just the latest version would be enough
Also, it would be great if this behavious can be enabled in config, instead of having to pass the --verbose time every time

[theRookieCoder]

it would be great if this behavious can be enabled in config

Sure I'll do that then

[theRookieCoder]

would it be possible to NOT do this on first download

How would this be done though? I guess it's the same issue with figuring out the mod from the file

[JustSimplyKyle]

Ah yes the age old problem
I guess it's ok to print out the first download
Since it's not that big of an issue

[theRookieCoder]

How would this be implemented for GitHub Releases? They only have the release description right?

[theRookieCoder]

As this Redditor suggested, we can also ask the user on whether to update or not (like most Linux package managers). And of course a --force option for automatic upgrades