Newer version of Affine not detected on Github

[githubkusi]

From https://github.com/toeverything/affine I have deployed version 0.26.1. There is a newer version available
https://github.com/toeverything/AFFiNE/pkgs/container/affine/715565955?tag=0.26.4
Tags look fine but it doesn't seem to be detected by PatchPanda. Why?

The image lacks the label "org.opencontainers.image.source", is this the reason?

[dkorecko]

Hey, sorry for the late response!

No. The missing org.opencontainers.image.source label is not the cause.

PatchPanda already derives toeverything/affine from the GHCR image name (ghcr.io/toeverything/affine:0.26.1), as seen in your screenshot. It then checks GitHub Releases, not GHCR package tags.

0.26.4 is published as a GHCR container tag, but it does not have a corresponding GitHub Release (or Git tag) in toeverything/AFFiNE. Therefore PatchPanda sees no eligible newer release and reports “Up to date.”

Support for direct container-registry tag checking would be needed to detect this type of release.

[githubkusi]

...but it does not have a corresponding GitHub Release (or Git tag)

Indeed, for 0.26.1 there was no release on Github (however there was a Github tag v0.26.1). I now updated manually to v0.27.0. For this version, there is a release and a tag

https://github.com/toeverything/AFFiNE/releases/tag/v0.27.0

Now, the newer release 0.27.1 is not detected by PatchPanda

Shouldn't 0.27.1 be detected by PatchPanda since there is a proper Github release (in contrast to my initial example with v0.26.1)?

https://github.com/toeverything/AFFiNE/releases/tag/v0.27.1

(@dkorecko )

[githubkusi]

It seems like the most recent Github release for Affine is  v0.27.4-beta.1 and the resulting regex wouldn't match v0.27.3. Would it be an idea to use the regex based on the installed version, or would it be possible to define my own regex?