minimumReleaseAge blocks update for Red Hat UBI images even when release is older than threshold

[andymaddio-lang]

How are you running Renovate?

Docker

Which platform you running Renovate on?

Azure DevOps

Which version of Renovate are you using?

43.76.4

Please tell us more about your question or problem

Description

When using minimumReleaseAge with Red Hat UBI Docker images, Renovate does not
propose updates even when the image has been published longer than the configured threshold.

Removing minimumReleaseAge from the config immediately fixes the issue and the update is proposed correctly.

Config

{
  "matchManagers": ["dockerfile"],
  "matchDatasources": ["docker"],
  "matchPackageNames": ["/^registry\\.access\\.redhat\\.com\\/[\\w\\/-]+/"],
  "minimumReleaseAge": "2 days",
  "groupName": "auto",
  "enabled": true,
  "addLabels": ["patch"],
  "automerge": true,
  "automergeStrategy": "squash",
  "autoApprove": true,
  "separateMajorMinor": false,
  "versioning": "redhat"
}

Expected behavior

registry.access.redhat.com/ubi9/ubi-minimal:9.7-1773204619 was published 5 days ago.
With minimumReleaseAge: "2 days", Renovate should propose this update.

Actual behavior

Renovate does not propose the update as long as minimumReleaseAge is set.
Commenting it out immediately restores the expected behavior.

Question

Is Renovate able to retrieve the releaseTimestamp for Red Hat registry images
(registry.access.redhat.com) when using versioning: "redhat"?

If the timestamp cannot be resolved, is there a workaround to make minimumReleaseAge
work correctly with this datasource, or should it be explicitly documented as unsupported?

Environment

• Renovate version: 43.76.4
• Platform: Azure DevOps
• Datasource: docker
• Registry: registry.access.redhat.com

Logs (if relevant)

Logs

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