App update not getting picked up

Trying to get an update to my app Releases - toz/MediLog - Codeberg.org picked up by the F-Droid updater.
I published build 5515 ~10 days ago and noticed that it didn’t get picked up when checking last week.
Turns out the merge request for build 5515 got stuck for some reason Merge requests · F-Droid / Data · GitLab
Now, instead of figuring out what has to be done for the now obsolete build, I decided to published a minor release instead, build 5519.

I published build 5519 on the 7th, a new “fdroid build” run started on the 8th and didn’t pick it up. And yet another “fdroid build” completed yesterday, but MediLog build 5519 still wasn’t picked up?
When checking here Merge requests · F-Droid / Data · GitLab I don’t see any new merge requests (stuck or accepted) either?
The metadata never got updated either: metadata/com.zell_mbc.medilog.fdroid.yml · master · F-Droid / Data · GitLab

Anyone got an idea what’s going on?

By the way, I did try Matrix first and got pointed to the stuck merge request, but didn’t get any further since. Hence I am trying my luck here as well.

Merge requests · F-Droid / Data · GitLab these ones?

we are using Debian Trixie now, so Java 21 is the default, can you update the code to work with it?

Well, yes, that’s the merge requests which got stuck, apparently requiring a rebase. Because I couldn’t figure out what I actually had to do I ignored those two and published a new build. That new build 5519 so far doesn’t show anywhere.

I can try to upgrade to Java 21, but I am not sure this is going to solve the issue given that things don’t get picked up at all rather than fail during the build?

those MRs wait for us to update them…

now, if we update and still fails with 17 then it’s not productive :slight_smile:

ping us there the Java 21 updated release is ready