autoupdate.strategy = "latest_github_release"

[OniriCorpe]

I added autoupdate strategy for calibreweb and kepubify to automate the updating process when a new version is available

So with it, when there is a new version, the yunohost-bot should made a PR within 24 hours

(Note that this will activated when this PR will be merged in the ‘master’ branch)

PR Status

• [x] Code finished and ready to be reviewed/tested
• [ ] The fix/enhancement were manually tested (if applicable)

Automatic tests

Automatic tests can be triggered on https://ci-apps-dev.yunohost.org/ after creating the PR, by commenting "!testme", "!gogogadgetoci" or "By the power of systemd, I invoke The Great App CI to test this Pull Request!". (N.B. : for this to work you need to be a member of the Yunohost-Apps organization)

[Krakinou]

Well, I purposely did not set the autoupdate on this package for 2 main reasons:

• The first one is just that they are some patches in the sources/patches folder that need to be adapted from time to time, I guess this could be done easily on the PR from the autoupdate, but this ensures no one will push a PR a little to fast before I had time to adjust them
• The second one is linked to a stupid mistake I made when I packaged this for the first time : The upstream calibreweb did not have version number at the time, so I randomly set one on the package and choose... 0.9. And then the maintainer decided it would be great to use github versionning and set 0.6... Aaaand that's how I got stuck with a package version greater than the upstream version. I guess I could manually changed both (patches and version number) on the PR from the autoupdate, but I have a small script that more or less automated it on my desktop and I'm good with it as it is not more work than updating this PR. Unless you know a way to circumvent the automatic numbering from the script?

[OniriCorpe]

it's fine!

if you want, you can just add the autoupdater for kepubify and maintain current functioning for the calibre part :)