-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
feat: A way to consume multiple releases/release descriptions #197
Comments
ReVanced has no specific use case for "old" versions. This is not a concept we need because users should always use the latest version of patches. Similarly Google PlayStore for example only provides the latest versions of the apps. So this is a difficult request. |
How else can this be implemented to allow clients to display proper changelogs? |
I don't know, probably just the current changelogs of the release how else? |
@oSumAtrIX Any new ideas with a fresh mind? |
Unfortunately, past changelogs can't be shown without discussing a new contract between the patches project and the API. API could technically track and persist changelogs in a database, but this isn't quite elegant because it needs to copy them. With a contract, it could dynamically fetch the changelogs respectively, however for that the patches need to conform a specific requirement set by API and for that the contract would be needed. |
Feature description
To display all the changelogs between the current version and new version, currently it only displays the latest version's description
Motivation
To allow users to know what is new between the version they're on and the latest version, they would be unaware of major changes if the major change was followed by a quick hotfix for example
Acknowledgements
The text was updated successfully, but these errors were encountered: