Missing releaseTimestamp for GitHub Actions digest updates
#39781
-
How are you running Renovate?A Mend.io-hosted app Which platform you running Renovate on?GitHub.com Which version of Renovate are you using?42.32.2 Please tell us more about your question or problemI set Now GitHub action digest updates are always pending, eg. Looking at the logs (https://developer.mend.io/github/phi-ag/argon2/-/job/019ae797-b015-7608-9ba3-7fa3bb84954d): {
"autoReplaceStringTemplate": "{{depName}}@{{#if newDigest}}{{newDigest}}{{#if newValue}} # {{newValue}}{{/if}}{{/if}}{{#unless newDigest}}{{newValue}}{{/unless}}",
"commitMessageTopic": "{{{depName}}} action",
"currentDigest": "2028fbc5c25fe9cf00d9f06a71cc4710d4507903",
"currentValue": "v6",
"currentVersion": "v6",
"currentVersionAgeInDays": 1,
"currentVersionTimestamp": "2025-12-03T03:06:19.000Z",
"datasource": "github-tags",
"depName": "actions/setup-node",
"depType": "action",
"fixedVersion": "v6",
"isAbandoned": false,
"mostRecentTimestamp": "2025-12-03T03:06:19.000Z",
"packageName": "actions/setup-node",
"registryUrl": "https://github.com",
"replaceString": "actions/setup-node@2028fbc5c25fe9cf00d9f06a71cc4710d4507903 # v6",
"sourceUrl": "https://github.com/actions/setup-node",
"versioning": "docker",
"warnings": [],
"updates": [
{
"updateType": "digest",
"newValue": "v6",
"newDigest": "395ad3262231945c25e8478fd5baf05154b1d79f",
"branchName": "renovate/actions-setup-node-digest"
}
]
},There is no Reading this comment I assumed this should work? #39058 (comment) The documentation packageFiles with updates debug log example shows the log output of a working action digest update, but it's a major update (v4.4.0 -> v6.0.0), not a digest update (v6 -> v6). Logs (if relevant)Logs |
Beta Was this translation helpful? Give feedback.
Answered by
RahulGautamSingh
Dec 4, 2025
Replies: 1 comment 4 replies
-
|
Set |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
I understand that I can workaround this issue, but |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, but we do not support it for digests yet. As you can the version remains the same ie, There are other discussions open to add support for extracting release timestamps for digest only updates as well. You can comment there for related disucssions. It is a missing feature rather than a bug. |
Beta Was this translation helpful? Give feedback.
Answer selected by
jamietanna
-
|
Related docs: https://docs.renovatebot.com/key-concepts/minimum-release-age/#which-update-types-take-minimumreleaseage-into-account Do we have an existing issue for the feature request for release timestamps for |
Beta Was this translation helpful? Give feedback.
-
|
I'm now using this as a workaround "packageRules": [
...
{
"description": "Disable minimum release age checks for docker",
"matchDatasources": ["docker"],
"minimumReleaseAge": null
},
{
"description": "Disable minimum release age checks for lock file maintenance and digest updates",
"matchUpdateTypes": ["lockFileMaintenance", "digest"],
"minimumReleaseAge": null
}
] |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Yeah, but we do not support it for digests yet. As you can the version remains the same ie,
v6There are other discussions open to add support for extracting release timestamps for digest only updates as well. You can comment there for related disucssions.
It is a missing feature rather than a bug.