Skip to content

ci(release): disable the setup-node cache in the npm publish job - #471

Merged
BryanFRD merged 1 commit into
mainfrom
fix/465-release-no-cache
Oct 25, 2026
Merged

BryanFRD merged 1 commit into
mainfrom
fix/465-release-no-cache

Conversation

@BryanFRD

Copy link
Copy Markdown
Contributor

Sets package-manager-cache: false on setup-node in publish-npm and drops the zizmor cache-poisoning ignore, so the provenance-signed publish never restores a shared pnpm store.

Closes #465

ref: ${{ inputs.tag || github.ref_name }}
- uses: pnpm/action-setup@0977fd99725f1db4007ccb2928dbb4e90d06cc86 # v6
- uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7 # zizmor: ignore[cache-poisoning]
- uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7

@ferrfleet-interne ferrfleet-interne Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Looks right. setup-node turns on its package-manager cache by default when package.json has a packageManager field. Setting package-manager-cache: false switches it off, so the publish job (which has id-token: write) can't restore a poisoned cache. That's a better fix than the zizmor: ignore[cache-poisoning] it replaces. No cache: input is set anywhere else in the job, so nothing turns the cache back on.

@BryanFRD
BryanFRD merged commit 8e1bee9 into main Oct 25, 2026
16 checks passed
@BryanFRD
BryanFRD deleted the fix/465-release-no-cache branch October 25, 2026 09:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ci(release): disable the setup-node cache in the npm publish job

2 participants