Publish Docker tags with semver

[bdovaz]

For example, alpine tags are published in the format: sha-7c4b132-alpine.

This makes it impossible to make it work with renovate.

Are commit hashes supported?
No, Renovate ignores Docker image tags that look like a Git commit hash.

Why is it not published in semver format (like on github releases)? For example: 0.18.0-alpine.

Thanks.

[mre]

We used to publish tagged versions. E.g. see 0.15.1-alpine.

Currently, the pipeline seems to be broken.

We listen on releases in the Docker pipeline (see here), but there are no release builds at the moment.

I didn't find the time to look into it, but if you know how to fix it, a pull request would be greatly appreciated.

We tried to fix it in #1568
Also see #1432

@eread fyi

[bdovaz]

Similar examples in case it helps you to fix it:

https://github.com/hadolint/hadolint/blob/4ab5d7809325c8de23956a44ca5a1f3c25907faf/.github/workflows/release.yml#L60

https://github.com/rhysd/actionlint/blob/2ab3a12c7848f6c15faca9a92612ef4261d0e370/.github/workflows/release.yaml#L57

[mre]

We use release-plz, so our process is a bit different: Rust release binaries get automatically created; the problem is, that it doesn't trigger the Docker build on release tags. It's important that the Docker build runs after release-plz has finished, because it depends on the release binaries. That's the tricky part.

Here's the release-plz pipeline:
https://github.com/lycheeverse/lychee/blob/master/.github/workflows/release-plz.yml

@marcoieni, maybe you came across this issue before?

[marcoieni]

No, I haven't. Couldn't you build the docker image after you build the binary (in the same workflow file)

[eread]

@marcoieni @bdovaz @mre This commit was added to the repo: a94a712, but there hasn't been a release since then to see if it makes the difference.

[mre]

Oh right, let's release a new version then to see if it works.

[bdovaz]

The 0.18.1 has been released and I see that it still doesn't have the tags right:

https://hub.docker.com/r/lycheeverse/lychee/tags

[mre]

Didn't work. It only built latest and master.
So it doesn't trigger a proper release build.

I triggered this Docker workflow run manually with the lychee-v0.18.1 tag:
https://github.com/lycheeverse/lychee/actions/runs/13265745175

The first attempt failed, because the release binaries didn't exist.
After 'Release Binary' was finished (https://github.com/lycheeverse/lychee/actions/runs/13265682405), I triggered it again, and it still didn't work. It still did not use the release name from the tag (e.g. if the tag is lychee-0.18.1). I was hoping that it would pick that up, but it didn't.

So I see two more required changes:

• we have to trigger the Docker build workflow after the 'Release Binary' workflow.
• we have to adjust the Docker image tags. My hope is that we can strip the lychee- prefix for that.

I've created #1631 to try and fix those issues.