The way the update repository has been set up via automation only allows for the most current release to be shown to the user via Kodi. Unless there are backend or Kodi related breaking changes provided in a given release, the user should be given the option to reinstall the previous version of the addon as well.
I'm thinking this will probably be a new build tool (https://github.com/djp952/build-tools) that would be added as a dependency to the repository git, something command-line based. After copying the new update repository data for the current release, something I could run that indicates how many prior versions I'd like to merge in and make available. Doesn't need to be fancy or user friendly, I'd be the only person to use it.
Just want to document this as a to-do since it's been bugging me for a while now.
The way the update repository has been set up via automation only allows for the most current release to be shown to the user via Kodi. Unless there are backend or Kodi related breaking changes provided in a given release, the user should be given the option to reinstall the previous version of the addon as well.
I'm thinking this will probably be a new build tool (https://github.com/djp952/build-tools) that would be added as a dependency to the repository git, something command-line based. After copying the new update repository data for the current release, something I could run that indicates how many prior versions I'd like to merge in and make available. Doesn't need to be fancy or user friendly, I'd be the only person to use it.
Just want to document this as a to-do since it's been bugging me for a while now.