Badge should be reset for unchecked new versions

[jskov]

Such as this

Or repo owners (and users) will get a false sense of security.

[hboutemy]

we have auto-detection of new releases in place
I just added rebuild by CI in #202 when PR is provided
now I need to add auto-merge for a PR when result is 100% reproducible
and auto-creation of PRs

does it match your expectations?
do you have any other idea?
(this WE, I waited before doing the rebuild of your plugin because I was working on #202: I wanted to do #204 :)

[jskov]

Ah, ok. Makes sense to hold back builds to test something.

The idea I tried to communicate is that the badge data should (automatically) be something like (color:orange, text:unverified) when a new version has been found but not yet reproduced (whatever the reason).

Super idea in #202 btw.

Cheers!

[hboutemy]

The idea I tried to communicate is that the badge data should (automatically) be something like (color:orange, text:unverified) when a new version has been found but not yet reproduced (whatever the reason).

any idea on how to trigger such a magic discovery and update of badge before auto-detection of new releases to do the rebuild?

[jskov]

Oh, no magic. You already detect the new release, and when I created this issue, the table row entry for mada-style was empty (except for the version).
That is all I meant; in that case, render unchecked badge.

Not that it should happen magically instantaneously on new releases in random projects 😀

[jskov]

How about this trick instead of magic; let the badge test include the tested version.

Then viewers will know if it applies to latest release, regardless of auto detection scheduling.