Fix renovate actions/*-artifact updates#2956
Merged
AlexWaygood merged 1 commit intomainfrom Mar 4, 2026
Merged
Conversation
The same as astral-sh/ruff#23675: > The intention here is that this should be a regex match. But that evidently is not working (astral-sh/ruff#23656 and astral-sh/ruff#23655 were filed as separate PRs rather than one combined PR). Looking at the renovate docs, it's possible that we need to surround the string with `/` in order for it to be considered a regular expression -- i.e., `/actions/.*-artifact/` rather than `actions/.*-artifact`. But a regex here also just feels like it's overcomplicating things anyway -- the only ones we aare about are `upload-artifact` and `download-artifact`! The same problem evidently exists on this repo too: see #2933 and #2934
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.
The same as astral-sh/ruff#23675:
The same problem evidently exists on this repo too: see #2933 and #2934