I’ve been self-hosting Atuin for a while, but when it came time to upgrade to 18.13 I ran into a lack of semantic tags. There’s an issue ( Release 18.12.1 not tagged in Docker Registry · Issue #3202 · atuinsh/atuin · GitHub ) but I can’t find any discussion of why these stopped being created.
Much like ndrwstn on that thread, I’m happy to offer my time to fix the issue, if it is an issue, and it’s wanted to be fixed. I hope so!
Weird, right? We must not be the only people noticing that
I just merged your PR fixing this, thank you!
Bit of a mess with this one, originally we had it working fine with single-arch builds, then we changed some stuff to get multi-arch and never got the tagging working in an automated + reliable way.
One possible issue, it’s tagging for the main branch: chore(ci): Tag docker images with semantic versions on tag creation (… · atuinsh/atuin@f42068e · GitHub
If you want to exclude that, I can look into how to get that not to happen.
I think that’s fine - it is accurate. I’d be concerned about people following HEAD with a deployment, but it sounds like lots of people basically automate that anyway
It seems this didn’t fix the problem; i also mentioned in the (now closed) issue, but 18.13.4 and 18.13.5, both recently released, can’t be downloaded from ghcr.io.
could you share any error you’re getting please? the tag is most certainly there, as I have just pulled it on a number of systems.
I forgot to put this info here (added it to the ticket, though). It seems that for a while the v prefix disappeared from the docker (and release?) tags which i didn’t notice until now, so i guess it’s working fine now.