Add bellsoft/liberica-runtime-container to workarounds:javaLTSVersions

[HonkingGoose]

Describe the proposed change(s).

Add bellsoft/liberica-runtime-container image to workarounds:javaLTSVersions preset.

Only copy/paste the needed bits from the full config below. 😉

    {
      "description": "Enable JDK updates of bellsoft/liberica-runtime-container.",
      "matchCurrentValue": "/^jdk-/",
      "matchDatasources": [
        "docker"
      ],
      "matchPackageNames": [
        "bellsoft/liberica-runtime-container"
      ],
      "versioning": "regex:^jdk-(?<major>\\d+)?(\\.(?<minor>\\d+))?(\\.(?<patch>\\d+))?([\\._+](?<build>(\\d\\.?)+))?(-(?<compatibility>.*))?$"
    },
    {
      "description": "Enable JRE updates of bellsoft/liberica-runtime-container.",
      "matchCurrentValue": "/^jre-/",
      "matchDatasources": [
        "docker"
      ],
      "matchPackageNames": [
        "bellsoft/liberica-runtime-container"
      ],
      "versioning": "regex:^jre-(?<major>\\d+)?(\\.(?<minor>\\d+))?(\\.(?<patch>\\d+))?([\\._+](?<build>(\\d\\.?)+))?(-(?<compatibility>.*))?$"
    },
    {
      "allowedVersions": "/^(jdk|jre)-(?:8|11|17|21)(?:\\.|-|$)/",
      "description": "Limit bellsoft/liberica-runtime-container versions to LTS releases.",
      "matchDatasources": [
        "docker"
      ],
      "matchPackageNames": [
        "bellsoft/liberica-runtime-container"
      ]
    }

Source:

• How to fix versioning for docker images with multiple compatibility parts #30366 (reply in thread)

[mvitz]

@HonkingGoose thanks for converting my question/answer into this issue.
I'll implement that today and create a PR for that.

I have just one additional question.

Technically, the config above contains two parts.
The first two are required to enable correct updates for the Docker Image because it contains two variable parts within the label, and the third one is a limitation to only update to long-term support (LTS) versions.
Therefore, the third part could be merged into the existing workarounds:javaLTSVersions preset.
However, the first two are required to be in place even when I want to update to non LTS versions and therefore exclude the workarounds:javaLTSVersions preset from my config.
Should these two be placed in its own preset (maybe a little bit like workarounds:nodeDockerVersioning)?

[HonkingGoose]

Where to put the base parts?

However, the first two [parts] are required to be in place even when I want to update to non-LTS versions and therefore exclude the workarounds:javaLTSVersions preset from my config.
Should these two be placed in its own preset (maybe a little bit like workarounds:nodeDockerVersioning)?

Putting the two base parts in a new preset seems best. Then we can extend from the basic preset in the workarounds:javaLTSVersions.

I don't know if that preset should be group:, monorepo: or something else. @rarkins what do you prefer?

Thank you for working on the issue

@HonkingGoose thanks for converting my question/answer into this issue.
I'll implement that today and create a PR for that.

Thank you! ❤️

[renovate-release]

🎉 This issue has been resolved in version 38.63.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)
• 38.63.0

Your semantic-release bot 📦🚀