javaLTSVersions not applying to docker tags from private registry

[cody-reibsome]

How are you running Renovate?

Self-hosted Renovate

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

GitLab - 39.9.3

Please tell us more about your question or problem

I have various references to eclipse-temurin docker images in my codebase, but only the ones that do not include a private registry prefix seem to respect the javaLTSVersions workaround.

i.e.

sample .gitlab-ci.yml snippet:

default:
  image: private.registry.io/eclipse-temurin:21-alpine@sha256:c63d8669d87e16bcee66c0379d1deedf844152da449ad48f2c8bd73a3705d36b

Renovate will suggest an upgrade from 21 (LTS) to 23 (non-LTS) when the image tag is prefixed with the private registry.

sample Dockerfile snippet:

FROM eclipse-temurin:21-alpine@sha256:c63d8669d87e16bcee66c0379d1deedf844152da449ad48f2c8bd73a3705d36b

but will keep non-prefixed images on LTS as expected. Do I need to configure something specifically for Renovate to understand that private registry provided images should still follow the workaround?

Logs (if relevant)

No response

[rarkins]

You'll need to customize

renovate/lib/config/presets/internal/workarounds.ts

Lines 131 to 153 in 416ab8e

	javaLTSVersions: {
	description: 'Limit Java runtime versions to LTS releases.',
	packageRules: [
	{
	allowedVersions: '/^(?:8|11|17|21)(?:\\.|-|$)/',
	description:
	'Limit Java runtime versions to LTS releases. To receive all major releases add `workarounds:javaLTSVersions` to the `ignorePresets` array.',
	matchDatasources: ['docker', 'java-version'],
	matchPackageNames: [
	'eclipse-temurin',
	'amazoncorretto',
	'adoptopenjdk',
	'openjdk',
	'java',
	'java-jre',
	'sapmachine',
	'/^azul/zulu-openjdk/',
	'/^bellsoft/liberica-openj(dk|re)-/',
	'/^cimg/openjdk/',
	],
	versioning:
	'regex:^(?<major>\\d+)?(\\.(?<minor>\\d+))?(\\.(?<patch>\\d+))?([\\._+](?<build>(\\d\\.?)+)(LTS)?)?(-(?<compatibility>.*))?$',
	},

(copy/paste/update into your own config)

[cody-reibsome]

sorry - just trying to make sure I understand: do I need to mimic this and add a registryUrls to the packageRules? or is there another change I'm missing?

[rarkins]

You need to copy and paste it and modify the package name list to suit your needs

[cody-reibsome]

OK, that worked. Thank you.

It seems odd that the private registry is not automatically detected and removed from the package name - this means I'll need to go in and edit the list of allowed versions manually whenever a new LTS release occurs rather than relying on inheriting those values from the default configs. Do you know if this is being tracked as an issue somewhere?