Repository navigation
ci: pin ovsds actions to releases with no nested tag refs - #84
Merged
Merged
Conversation
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
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.
🤖 AI-generated description
https://github.com/ovsds/github-watcher/pull/84 pin the ovsds actions to releases with no tag refs inside. [S, config, code +4/−4]
The previous releases of these four actions use other actions by tag inside, a tag ref nested under a SHA pin, which GitHub rejects in a repository that requires SHA pinning. Their new releases pin every action inside by SHA; the issue action also drops
actions-cool/issues-helper, which GitHub now blocks.create-or-update-unique-issue-actionv1.1.1 looks up the scan issue among open issues only: after a clean scan closes it, the next scan with findings opens a new issue instead of reopening the old one.Changes
check-pr-title.yaml:ovsds/commitlint-pr-title-actionv1.2.1; its check now runs commitlint 21, the version the local hook already uses, on Node 24github-watcher.yaml:ovsds/github-watcher-actionv1.4.1, with the same inputs, defaults and cache key as v1.4.0release-pr.yamlandrelease-scan.yaml:ovsds/create-or-update-unique-comment-actionv1.1.1 andovsds/create-or-update-unique-issue-actionv1.1.1Testing
mise run init,lint-fix(no changes),lint- passaction.yamlread at the tag: everyuses:pinned by SHA, every input these workflows pass unchangedRelated