Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions .github/actionlint.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
paths:
".github/workflows/**/*.{yaml,yml}":
ignore:
- 'reusable workflow call "\$/\.github/workflows/security\.yml" at "uses" is not following the format'
4 changes: 2 additions & 2 deletions .github/workflows/release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ permissions: {}
jobs:
security:
name: Security
uses: ./.github/workflows/security.yml
uses: $/.github/workflows/security.yml
permissions:
contents: read
security-events: write
Expand Down Expand Up @@ -64,7 +64,7 @@ jobs:

- name: Govulncheck
run: |
go install golang.org/x/vuln/cmd/govulncheck@latest
go install golang.org/x/vuln/cmd/govulncheck@v1.8.0
govulncheck ./...

- name: Verify tag is on main
Expand Down
2 changes: 1 addition & 1 deletion seed/.github/workflows/release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ permissions: {}
jobs:
security:
name: Security scan
uses: ./.github/workflows/security.yml
uses: $/.github/workflows/security.yml

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch, and it changes the PR. The seed's comment (# @latest intentional — pinning delays scanning improvements and new Go version support for no meaningful reproducibility gain) is this repo's documented policy from #3, and the evidence backs it: govulncheck fetches its vulnerability database live regardless of the binary version, and the sibling repos that did pin have rotted (hey-sdk and fizzy-sdk sit on govulncheck v1.1.4 against a current v1.8.0). Pinning here while the seed says the opposite would be inconsistency for Scorecard's benefit. So eae7766 drops the pins from this repo's workflows rather than propagating them into the seed; the three Scorecard Pinned-Dependencies alerts are dismissed as won't-fix citing that policy, and the PR is retitled to what is left: the $/ self-repository change.

permissions:
contents: read
security-events: write
Expand Down
Loading