Understanding Configuration for Correct Fetching of Release Notes

[mstoetzer-jambit]

How are you running Renovate?

Self-hosted

If you're self-hosting Renovate, tell us what version of Renovate you run.

docker.io/renovate/renovate:37.35.2

If you're self-hosting Renovate, select which platform you are using.

GitLab self-hosted

Was this something which used to work for you, and then stopped?

I never saw this working

Wanted end result.

I want renovate to fetch release notes for Dockerimage Sonatype Nexus.

The Dockerimage is provided here: https://github.com/sonatype/docker-nexus3

The actual source code and release notes (just link to the official sonatype website) for certain version is provided here: https://github.com/sonatype/nexus-public/releases

The Dockerimage does not provide a label org.opencontainers.image.source.

Dockerimage tag: 3.62.0

Source Code release (git tag): release-3.62.0-01

I want renovate to fetch the release notes for Dockerimage 3.62.0 from the repository https://github.com/sonatype/nexus-public/releases.

I'm not sure, when to use extractVersion or versioning / versioningTemplate. As I understood, extractVersioning should something like "extractVersion": "^release-(?<major>\\d+)\\.(?<minor>\\d+)\\.(?<patch>\\d+)-(?<build>[^.]+)?$", but it didn't work

What you tried so far.

Preset container-image-release-notes.json

{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "packageRules": [
    {
      "matchPackageNames": ["sonatype/nexus3"],
      "matchDatasources": ["docker"],
      "sourceUrl": "https://github.com/sonatype/nexus-public"
    }
  ]
}

Main configuration renovate.json

{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "extends": [
    "local>username/renovate-configuration-presets:container-image-release-notes"
  ],
  "regexManagers": [
    {
      "description": "Update Nexus Docker Image",
      "fileMatch": [
        "nexus\\.service$"
      ],
      "matchStrings": [
        "(?<depName>sonatype\\/nexus3):(?<currentValue>[a-z0-9.-]+)(?:@(?<currentDigest>sha256:[a-f0-9]+))?"
      ],
      "datasourceTemplate": "docker"
    }
  ]
}

Given the Systemd unit file that contains the docker image.

nexus.service

<REDACTED>

[Service]
<REDACTED>
ExecStart=/usr/bin/docker run --rm \
  <REDACTED>
  docker.io/sonatype/nexus3:3.61.0

<REDACTED>

Relevant debug logs

Logs

Copy/paste the relevant log(s) here, between the starting and ending backticks

[rarkins]

If Renovate can't locate the source repo then the first step would be to teach it by contributing the sourceUrl for this image to here:

renovate/lib/modules/datasource/metadata-manual.ts

Line 67 in c8c0e1b

docker: {

[mstoetzer-jambit]

Thanks, this could be the first step.

I don't understand, how release notes can be fetched.
Please have a look at this discussion: #12179
It seems to be vice versa. The version will be found on github-releases and than major, minor and patch got extracted from it.

Source Code release (git tag): kustomize/v5.2.1

On my problem above, I want to add release- and -build to major, minor and patch (found via the docker datasource). Is this even possible?

Dockerimage tag: 3.62.0

Source Code release (git tag): release-3.62.0-01

[rarkins]

I'm not sure it will be possible, but creation of a reproduction is necessary for anyone to debug it

[github-actions[bot]]

Hi there,

Get your discussion fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible.

Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this.

To get started, please read our guide on creating a minimal reproduction.

We may close the discussion if you, or someone else, haven't created a minimal reproduction within two weeks. If you need more time, or are stuck, please ask for help or more time in a comment.

Good luck,

The Renovate team

[mstoetzer-jambit]

Sure.

Please see the following PR: mstoetzer-jambit/renovate-nexus-update-demo#1

Renovate.json: https://github.com/mstoetzer-jambit/renovate-nexus-update-demo/blob/main/renovate.json

Nexus.txt: https://github.com/mstoetzer-jambit/renovate-nexus-update-demo/blob/main/nexus.txt

Preset containing sourceUrl: https://github.com/mstoetzer-jambit/renovate-config-presets/blob/main/container-image-release-notes.json

[rarkins]

Based on this PR, we can see that Renovate does have a source url/repo. Then it seems that Renovate does not correlate the new version 3.62.0 with release-3.62.0-01 in the repo. Most likely it is the -01 suffix causing it to think they are not the same.

Maybe some massaging can be added as a fallback when releases aren't found. e.g there's already some basic ones in

renovate/lib/workers/repository/update/pr/changelog/release-notes.ts

Lines 143 to 152 in 8401943

	if (is.undefined(matchedRelease)) {
	// no exact match of a release then check other cases
	matchedRelease = releases.find(
	(r) =>
	r.tag === version ||
	r.tag === `v${version}` ||
	r.tag === gitRef ||
	r.tag === `v${gitRef}`,
	);
	}