Updating digest with customDatasource

[faenschi]

What would you like help with?

I would like help with my configuration

How are you running Renovate?

Self-hosted

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

Gitlab

Please tell us more about your question or problem

Hi all!
i'm trying to update a checksum in a yaml file:

resources:
    zipArtifact:
        sha256sum: 7f643cd5478d09340e749a8d112322cc1179171b01721890e300504aed4fb6c8

To achieve that i tried with a customManager and customDatasource:

 "customManagers": [
    {
      "customType": "regex",
      "fileMatch": ["my.yaml"],
      "matchStrings": ["sha256sum:\\s(?<currentDigest>.*)"],
      "depNameTemplate": "sha256sum",
      "datasourceTemplate": "custom.sha256",
      "currentValueTemplate": "1",
      "versioningTemplate": "regex:^(?<patch>[0-9a-f]{1,64})$"  <--- DO I NEED THE VERSIONING TEMPLATE? 
    }
  ],
  "customDatasources": {
    "sha256": {
      "defaultRegistryUrlTemplate": "<myregistrycall>",
      "format": "json",
      "transformTemplates": [
        "{\"releases\":[{\"version\": \"1\", \"digest\": \"$string(checksums.sha256)\"}]}"
      ]
    }
  }

The response from my registry looks like:

 "mimeType" : "application/zip",
  "size" : "24467908",
  "checksums" : {
    "sha1" : "7f84c390fd6eba653899c5d6c7a2893f8fd90f44",
    "md5" : "8b14812bacb34d3133f7305dd4c6b2ff",
    "sha256" : "7f643cd5478d09340e749a8d112322cc1179171b01721890e300504aed4fb6c8"
  },

But this does not work. It seems like it doesnt compare the new and old digests. I also tried to write the digest in the version field. But then, i don't know which versioning i should use for a digest.

I tried to follow the example here:
#25149

any help appreciated
thx & regards angela

Logs (if relevant)

Logs

Replace this text with your logs, between the starting and ending triple backticks

[acortelyou]

Running into this exact same issue: I can't seem to get custom manager/datasource to create a digest update.

The foundations for handling this were merged in #26007 but even when configured as shown in #25197 it doesn't work.

latest and main are the ideal scenario, but throw unsupported/unversioned value which explains why they are being ignored even though that seems like it should be valid for docker versioning.

I have tried several versioning types including git, docker, and loose but get the same results.

1 => 1 should work: it's not an ignored version and the digest has changed.

abc123/def456 represent full 40 character commit id's.

currentValue: main
currentDigest: abc123

releases:
- version: main 
  digest: def456

no update

currentValue: latest
currentDigest: abc123

releases:
- version: latest
  digest: def456

no update

currentValue: 0000000000000000000000000000000000000000
currentDigest: abc123

releases:
- version: 0000000000000000000000000000000000000000
  digest: def456

no update

currentValue: 1
currentDigest: abc123

releases:
- version: 1
  digest: def456

no update

currentValue: 1.0.0
currentDigest: abc123

releases:
- version: 1.0.1
  digest: def456

patch update

currentValue: 2
currentDigest: abc123

releases:
- version: 3
  digest: def456

major update

[acortelyou]

Should have checked open PRs first, looks like the support for this functionality is being implemented here: #26299

thanks @fstehle hope it can get merged

[marcoesters]

I think #28760 has had unintended consequences. renovate now emits warnings because getDigest returns null here: https://github.com/renovatebot/renovate/blob/main/lib/workers/repository/process/lookup/index.ts#L543-L546

Before this PR, it would retrieve the digest from the releases array.

Compare the following PR ContinuumIO/docker-images#497 (created before the PR) with this one ContinuumIO/docker-images#512.

For reference, the renovate config defining the transform template: https://github.com/anaconda/renovate-config/blob/main/anaconda-installers.json

And a pretty-printed version here: https://github.com/anaconda/renovate-config/blob/main/docs/anaconda-installers.md#developers-understanding-the-transform-templates

The template currently returns this:

{
  "releases": [
    {
      "digest": "832d48e11e444c1a25f320fccdd0f0fabefec63c1cd801e606836e1c9c76ad51",
      "version": "py312_24.4.0-0",
      "changeLogUrl": "https://docs.anaconda.com/free/miniconda/miniconda-release-notes/#miniconda-24-4-0-0",
      "sourceUrl": "https://repo.anaconda.com/miniconda/Miniconda3-py312_24.4.0-0-Linux-aarch64.sh",
      "releaseTimestamp": "2024-05-20T17:02"
    }
  ],
  "sourceUrl": "https://repo.anaconda.com/miniconda/",
  "homepage": "https://anaconda.com"
}

From that, the value for update.newDigest used to be the digest value, but it's null now.

[rarkins]

@faenschi can you create a minimal reproduction which we can debug/test against?

[faenschi]

@rarkins My issue has been solved with PR #28760

[rarkins]

Sorry, I'd meant to tag @marcoesters

[marcoesters]

Thanks for the very quick response! I created a reproducer repo: https://github.com/marcoesters/renovate-miniconda-digest-reproducer

I am attaching log files for three dry runs of renovate: the current main branch, the 37.331.0 tag, and the 37.332.0 tag.

As you can see, there is no warning in 37.331.0, but it appears in 37.332.0 and still appears in main. In three runs, the update is still performed correctly.

renovate_main.log
renovate_37.331.0.log
renovate_37.332.0.log

[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. Discussions without reproductions are less likely to be converted to Issues.

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

Good luck,

The Renovate team