Backport workflow-hardening fix (excessive-permissions) to 3 release branches
Author: CharlieMCYCreated Jun 29, 2026Updated Sep 28, 2026
LabelsStale
Summary
The default branch already hardened .github/workflows/build-test.yml against the issue(s) below, but 3 release branches still carry it. This proposes the same, minimal, scanner-verified fix for each.
What's flagged (by zizmor)
excessive-permissions— workflow/job granted broaderpermissionsthan needed
Already resolved on the default branch in:
Affected release branches (3)
release-3.16(still present as of HEAD7877b45b)release-3.14(still present as of HEAD81c902a1)release-3.15(still present as of HEADfa9efb07)
Suggested per-branch patches
Each diff below was checked locally with zizmor and actionlint: the flagged finding(s) are cleared on the affected construct and no new lint or security findings are introduced. (Whitespace is normalized; only security-relevant lines change.)
release-3.16 — excessive-permissionsFile .github/workflows/build-test.yml; suggested edits:
- permissions.contents = 'read'
--- a/.github/workflows/build-test.yml
+++ b/.github/workflows/build-test.yml
@@ -25,3 +25,5 @@
run: make test-coverage
- name: Test build
run: make build
+permissions:
+ contents: readrelease-3.14 — excessive-permissionsFile .github/workflows/build-test.yml; suggested edits:
- permissions.contents = 'read'
--- a/.github/workflows/build-test.yml
+++ b/.github/workflows/build-test.yml
@@ -24,3 +24,5 @@
run: make test-coverage
- name: Test build
run: make build
+permissions:
+ contents: readrelease-3.15 — excessive-permissionsFile .github/workflows/build-test.yml; suggested edits:
- permissions.contents = 'read'
--- a/.github/workflows/build-test.yml
+++ b/.github/workflows/build-test.yml
@@ -24,3 +24,5 @@
run: make test-coverage
- name: Test build
run: make build
+permissions:
+ contents: readHappy to open pull requests instead if that's preferred.
Source: helm/helm