[BUG] Semver tags not published for Jellyfin 12.1: SEMVER not detected for X.Y+suffix versions

[Gigitsu]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Builds of the current Jellyfin release don't publish the semver image tags (<SEMVER>, amd64-<SEMVER>, arm64v8-<SEMVER>).

The upstream version found by custom_version_command (jenkins-vars.yml) is 12.1+ubu2604. In the Sanitize tag stage of the Jenkinsfile:

1. The sanitize sed (s/[~,%@+;:/ ]//g) removes the +, so EXT_RELEASE_CLEAN becomes 12.1ubu2604.
2. The first regex /(\d+)\.(\d+)\.(\d+)/ doesn't match, because there are only two version components.
3. The fallback regex /(\d+)\.(\d+)(?:\.(\d+))?(.*)/ matches, but group 4 is ubu2604. The fallback only sets SEMVER when group 4 is empty (!semver[0][3] && !semver[0][4]), so SEMVER is never set.

Previous X.Y.Z releases weren't affected: the first regex isn't anchored, so 10.10.7ubu2404 still produced 10.10.7.

Expected Behavior

For 12.1+ubu2604, SEMVER should be set the same way it is for a bare X.Y version and the semver tags should be published to all registries.

Steps To Reproduce

--

Environment

--

CPU architecture

x86-64

Docker creation

--

Container logs

--

[aptalca]

Tell your LLM to search through existing issues before blindly checking that box.

[Gigitsu]

I admit that I only looked through the open issues, not the closed ones. I apologize for that.

However, there is no need to be so harsh. I manually looked into the Jenkins file, ran the curl commands, and tested the regular expression to identify the issue.