-
Notifications
You must be signed in to change notification settings - Fork 0
tests: property-based action-pin assertions (unbreak Dependabot bumps) #90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+39
−4
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,15 @@ | ||
| ### Changed | ||
|
|
||
| - CI security-contract tests now assert action-pin *properties* instead of | ||
| exact pin fixtures: the Gitleaks, CodeQL init/analyze, and upload-artifact | ||
| assertions require a real `uses:` line pinned to a full 40-hex commit SHA | ||
| with a version comment, but no longer freeze WHICH SHA or major version. | ||
| The frozen fixtures broke every Dependabot actions-group PR by construction | ||
| (#9, #29, #67) while adding no enforcement beyond the repo-wide | ||
| full-SHA pin test and CODEOWNERS review of workflow diffs — Dependabot | ||
| cannot update test fixtures that mirror the workflow it bumps. The | ||
| replacement regexes are anchored to `uses:` lines (a comment or string | ||
| mentioning an action no longer satisfies them — a strictness *increase* | ||
| over the old substring assertions, per Codex cross-family review) and | ||
| accept dotted version comments (`# v3.0.0`) as Dependabot writes them. | ||
| Test infrastructure only — no version bump. |
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When an inline version comment is removed or moved, Python's
\s+can consume the newline, so a pinneduses:line followed by a separate# v4comment still satisfies this assertion;^\s*similarly allows matching an action-looking line inside a YAML block scalar. The same construction is used for all four new assertions, so they do not actually guarantee a realuses:line with an inline version comment as documented. Use horizontal whitespace such as[ \t]around the tokens so the multiline anchors remain line-local.Useful? React with 👍 / 👎.