Match more than one digit for version numbers

[eread]

As suggested here: #1833 (comment) by @thomas-zahner, let's test the result of #1881.

[eread]

@thomas-zahner Ok, I think we need one more minor change based on this commit: 68cbed0, and these runs:

• https://github.com/lycheeverse/lychee/actions/runs/18862068098/job/53822174152#step:3:56
• https://github.com/lycheeverse/lychee/actions/runs/18862068098/job/53822174152#step:4:85

Basically, /d will match only a single digit, whereas the minor version number for Lychee right now is more than one digit, so the regular expression as it currently is doesn't quite catch it.

I'll refactor this PR to just make that change, and I think the Docker images will be properly tagged for the next release!

[eread]

@thomas-zahner Could you review? I believe this change is required (see: #1889 (comment)).

[thomas-zahner]

Glad to hear that you could test the changes in your local repository and thank you for testing and submitting this PR.

[eread]

Glad to hear that you could test the changes in your local repository and thank you for testing and submitting this PR.

Thanks for the review @thomas-zahner 🙇🏻

I thought you might ask for all three parts of the version number to be similarly handled.

Here's a commit for testing: 6c48cfc

Here's the test run with results:

• https://github.com/lycheeverse/lychee/actions/runs/18891603745/job/53920314460#step:3:56
• https://github.com/lycheeverse/lychee/actions/runs/18891603745/job/53920314460#step:4:85

I'll now refactor the PR to just have the required changes.

[nobkd]

Normally when I see . in a regex, I would expect it to match anything. Is this applicable here, and has to be escaped to be a real dot (like \.)?
(just, if this is applicable here, the regex dot would probably have coincidentally matched the real dot beforehand)

(edit: It doesn't really matter that much, as the match is not used very often, but the group would match something like 123-1/1, not only 123.1.1, and this might not be the desired match)

[eread]

Normally when I see . in a regex, I would expect it to match anything. Is this applicable here, and has to be escaped to be a real dot (like \.)? (just, if this is applicable here, the regex dot would probably have coincidentally matched the real dot beforehand)

(edit: It doesn't really matter that much, as the match is not used very often, but the group would match something like 123-1/1, not only 123.1.1, and this might not be the desired match)

Thanks for chiming in @nobkd. I agree that . normally acts as an operator of some kind. I didn't dig in to what sort of regex parser that the action uses, just looked at the documentation: https://github.com/docker/metadata-action?tab=readme-ov-file#typesemver.

[nobkd]

They use the unescaped version of the dots in many patterns, so this probably works as intended 🤷

[thomas-zahner]

True, for correctness we could replace . with \.. However, it shouldn't pose a problem as we only create tags with version numbers in the format of lychee-v1.2.3.