ci: keep release builds off the npm cache; week-long Dependabot cooldown
zizmor (workflow-lint) flagged three things: - cache-poisoning: setup-node v7 restores the npm cache unless told not to, and the release workflows publish what they build. They now set `package-manager-cache: false`, so a cache written by another workflow can never reach a release artifact. - dependabot-cooldown: raise every ecosystem to 7 days. - dangerous-triggers: the two `workflow_run` notifiers are ignored with the reason in zizmor.yml; the shared workflows only read run metadata and pass untrusted fields through `env:`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
a70580e703
commit
1b5051beaa
4 files changed
+26
-3
No files matched your search
@@ -5,7 +5,7 @@
|
||||
# below add scheduled VERSION updates so the tree does not silently rot between
|
||||
# advisories, and carry the ignore rules that keep unfixable alerts quiet.
|
||||
#
|
||||
# `cooldown` holds version updates back for a few days after a release is
|
||||
# `cooldown` holds version updates back for a week after a release is
|
||||
# published. Most npm supply-chain compromises are caught and yanked within
|
||||
# that window; security updates ignore the cooldown and still arrive at once.
|
||||
#
|
||||
@@ -34,7 +34,7 @@ updates:
|
||||
schedule:
|
||||
interval: "weekly"
|
||||
cooldown:
|
||||
default-days: 3
|
||||
default-days: 7
|
||||
open-pull-requests-limit: 5
|
||||
commit-message:
|
||||
prefix: "chore(deps)"
|
||||
@@ -101,6 +101,8 @@ updates:
|
||||
# No version-update PRs; this entry only feeds ignore rules to security
|
||||
# updates. The Rust side moves with tauri (see the note at the top).
|
||||
open-pull-requests-limit: 0
|
||||
cooldown:
|
||||
default-days: 7
|
||||
ignore:
|
||||
- dependency-name: "glib"
|
||||
|
||||
@@ -109,7 +111,7 @@ updates:
|
||||
schedule:
|
||||
interval: "weekly"
|
||||
cooldown:
|
||||
default-days: 3
|
||||
default-days: 7
|
||||
open-pull-requests-limit: 3
|
||||
commit-message:
|
||||
prefix: "ci"
|
||||
|
||||
@@ -26,6 +26,9 @@ jobs:
|
||||
- uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
|
||||
with:
|
||||
node-version-file: .node-version
|
||||
# Release artifacts are built from a clean install: a cache written
|
||||
# by any other workflow must not be able to feed into them.
|
||||
package-manager-cache: false
|
||||
- run: npm ci
|
||||
- run: npm run typecheck
|
||||
- run: npm run test:run
|
||||
@@ -56,6 +59,9 @@ jobs:
|
||||
- uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
|
||||
with:
|
||||
node-version-file: .node-version
|
||||
# Release artifacts are built from a clean install: a cache written
|
||||
# by any other workflow must not be able to feed into them.
|
||||
package-manager-cache: false
|
||||
|
||||
- uses: actions/setup-java@de7274f081f381c8f8158605e0321c36c376e2e6 # v6.0.1
|
||||
with:
|
||||
|
||||
@@ -30,6 +30,9 @@ jobs:
|
||||
- uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
|
||||
with:
|
||||
node-version-file: .node-version
|
||||
# Release artifacts are built from a clean install: a cache written
|
||||
# by any other workflow must not be able to feed into them.
|
||||
package-manager-cache: false
|
||||
- run: npm ci
|
||||
- run: npm run typecheck
|
||||
- run: npm run test:run
|
||||
@@ -93,6 +96,9 @@ jobs:
|
||||
- uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
|
||||
with:
|
||||
node-version-file: .node-version
|
||||
# Release artifacts are built from a clean install: a cache written
|
||||
# by any other workflow must not be able to feed into them.
|
||||
package-manager-cache: false
|
||||
- uses: dtolnay/rust-toolchain@6bed0761d98439e5a578e2877258200ad565ba87 # stable
|
||||
with:
|
||||
toolchain: stable
|
||||
|
||||
@@ -9,3 +9,12 @@ rules:
|
||||
"poli0981/*": any
|
||||
# Everything else must be pinned to a full commit SHA.
|
||||
"*": hash-pin
|
||||
dangerous-triggers:
|
||||
ignore:
|
||||
# Both run on `workflow_run` so a failure (or a release build) anywhere
|
||||
# can be reported to Discord. Neither checks out the triggering run's
|
||||
# code nor downloads its artifacts: the shared workflows only read run
|
||||
# metadata, and pass every untrusted field (branch, commit message,
|
||||
# actor) to the notifier script through `env:`, never by interpolation.
|
||||
- notify-ci-failure.yml
|
||||
- notify-release-pipeline.yml
|
||||
Reference in new issue
Block a user