renovate pin digests#115
Merged
Merged
Conversation
Repo policy requires all actions to be pinned to a full commit SHA. Without this, Renovate PRs fail CI immediately causing an open/close loop every hour. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Contributor
Author
|
If the SHA-pinning policy is rolled out to other repos (and we observe same thrashing behaviour there), pinDigests: true should be added to the shared Renovate config in uptick/renovate-config (referenced from tf-infrastructure) so all repos get it automatically. For now just fixing here to see if we have the correct fix. |
jarekwg
approved these changes
May 13, 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.
Changes
Why
A repo-level GitHub Actions policy requires all actions to be pinned to a full commit SHA. This was causing Renovate to thrash on PR #114 — CI would fail immediately on every Renovate PR (because Renovate uses tag-based refs like @v4.0.0 by default), Renovate would see the failure ~30 minutes later and autoclose the PR, then reopen it on the next hourly run. This has been looping since the policy was introduced.
pinDigests: true tells Renovate to use commit SHAs instead of tags (e.g. astral-sh/ruff-action@abc123 # v4.0.0), satisfying the policy so CI passes. The workflow files are also updated so master itself is compliant — previously the actions there were also violating the policy but not being flagged since they weren't in an open PR.