Use timestamp-optional on GHA digest updates#24
Merged
Phil Bates (philbates35) merged 1 commit intomainfrom Jan 15, 2026
Merged
Use timestamp-optional on GHA digest updates#24Phil Bates (philbates35) merged 1 commit intomainfrom
Phil Bates (philbates35) merged 1 commit intomainfrom
Conversation
Alexis Coles (AlexisColes)
approved these changes
Jan 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I discovered that GHA digest updates don't provide a release timestamp so the PRs get stuck pending.
Take this PR for example https://github.com/Lendable/renovate-config/pull/77 (happens to be on a renovate repo but that's just coincidence, its just the first example I came across), its stuck pending but its updating to 93cb6efe18208431cddfb8368fd83d5badbf9bfd which was released on November 13.