ci: track the main branch of Homebrew/actions - #76
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
Renovate still reports a lookup failure for the release workflow after #75:
The github-actions manager reads at most three version parts from the pin comment, so
# 2026.09.13.1becomes2026.09.13, a tag that does not exist. Homebrew/actions tags always have four parts, so no tag works here.This pins the step to the head of
mainwith a# maincomment. Renovate resolves the digest of a branch through the commits API, which answers formainand returns 404 for the renamedmasterbranch that caused the first warning.