Skip to content

ci: harden trusted publish workflow - #5099

Merged
JoviDeCroock merged 1 commit into
mainfrom
ci/disable-publish-workflow-cache
May 20, 2026
Merged

ci: harden trusted publish workflow#5099
JoviDeCroock merged 1 commit into
mainfrom
ci/disable-publish-workflow-cache

Conversation

@JoviDeCroock

@JoviDeCroock JoviDeCroock commented May 19, 2026

Copy link
Copy Markdown
Member

Summary

  • Explicitly disables setup-node package-manager auto-caching in the trusted publishing workflow.
  • Removes existing publish-workflow dependency cache usage where present.
  • Pins external GitHub Actions in the trusted publish workflow to full commit SHAs, keeping the original tag as a comment breadcrumb.

Why

Trusted publishing/OIDC workflows should not restore shared dependency caches, and tag-based action references can be retargeted after compromise. The StepSecurity advisory for actions-cool/issues-helper is the concrete failure mode: tags were moved to an imposter commit, while full-SHA pinned workflows were unaffected.

Verification

  • Parsed the edited workflow YAML locally with PyYAML.
  • Re-scanned release workflows for actions/setup-node without package-manager-cache: false and for actions/cache usage.
  • Re-scanned trusted publish workflow uses: entries and confirmed all external actions are pinned to 40-character commit SHAs.

@coveralls

Copy link
Copy Markdown

Coverage Status

coverage: 98.528%. remained the same — ci/disable-publish-workflow-cache into main

@JoviDeCroock JoviDeCroock changed the title ci: disable cache in publish workflow ci: harden trusted publish workflow May 19, 2026
@JoviDeCroock
JoviDeCroock merged commit f5c1bac into main May 20, 2026
5 checks passed
@JoviDeCroock
JoviDeCroock deleted the ci/disable-publish-workflow-cache branch May 20, 2026 04:55
@JoviDeCroock JoviDeCroock mentioned this pull request Jul 5, 2026
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.

3 participants