Feature: Show release / changelog notes prior to triggering an update if a user clicks the update option when a new update is available

Preflight Checklist

• I have read the Contributing Guidelines for this project.
• I agree to follow the Code of Conduct that this project adheres to.
• I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Problem Description

Currently it seems that with “Enable updates” and “Include pre-releases” enabled that it is very easy to accidentally be unaware of a change, problem or something else.

Proposed Solution

If there were a method to show the release notes / changelog prior to the user accepting to actually install an update, that might be good insomuch that it will act as a warning and/or make users aware of what to expect (such as the last update that included the horizontal bar change and requirement to toggle off and on).

Another thing that may be useful would be to, instead of - with PRE-RELEASE ONLY - triggering an auto-update, perhaps require the user to click the “Check for updates” function (eg, on macOS under menubar: Ferdium → Check for updates) to use more awareness and thoughtfulness before blasting in an update…

Alternatives Considered

Another choice, that wouldn’t get as much testing for the (auto)update system would be to just force manual updates for pre-release vs allowing users to just trigger it.

Yet another choice would be, in the same manual line as above, when they click auto-update function on the bottom popup updater bar, it would lead them over to the releases page to be forced to have the release notes more readily available.

Additional Information

No response

[vraravam]

@meiphoo7-Mae -

1. please do not hijack tickets
2. Yes - i knew that, but i also know that @SpecialAro has implemented some code in his branch - which was waiting for this functionality. Imo, the original ticket’s asks will be addressed by his upcoming PR. Since the original requirements are over (waiting for the PR), I removed the “good first issue” and added the “upstream dependency”. If you can create a new ticket for those pieces that you had wanted, we can move that upstream dependency tag to yours and remove from this one. That way, we can cleanly close this ticket.

[meiphoo7-Mae]

@SpecialAro Thanks. That sounds good to me. Skipping a version is already possible to a certain extent by dismissing the blue bar. However for some reason this works only temporary because in the end the blue bar shows up again. Is it necessary or useful to open a new issue ticket for this, that way this issue can be closed cleanly as suggested by @vraravam, or is it going to be solved anyway by your pull request?