Skip to content

ci: pin semantic-release workflow actions to commit SHAs - #51

Merged
aquemy merged 1 commit into
mainfrom
ci/pin-release-actions-to-sha
Jun 16, 2026
Merged

ci: pin semantic-release workflow actions to commit SHAs#51
aquemy merged 1 commit into
mainfrom
ci/pin-release-actions-to-sha

Conversation

@aquemy

@aquemy aquemy commented Jun 16, 2026

Copy link
Copy Markdown
Member

The org now enforces full-length SHA pinning for GitHub Actions. The Semantic Release workflow still referenced six actions by tag, so it fails immediately ("all actions must be pinned to a full-length commit SHA") and no release can run.

Pins the six remaining refs in semantic-release.yml to commit SHAs (version kept in trailing # vN comments), matching the convention already used across the other workflows:

  • actions/create-github-app-token@…d72941d # v1
  • actions/checkout@…34e1148 # v4 (×2)
  • actions/setup-python@…a26af69 # v5
  • crazy-max/ghaction-import-gpg@…e89d409 # v6
  • orhun/git-cliff-action@…f50e115 # v4
  • pypa/gh-action-pypi-publish@…cef2210 # release/v1

Once merged, the push to main will trigger Semantic Release, which will cut v0.4.0 (minor — backlog since v0.3.6 includes feat(prompts) #45).

Org policy now enforces full-length SHA pinning for all actions. Pin the
six remaining tag-based refs in the release workflow so it can run:
create-github-app-token, checkout, setup-python, ghaction-import-gpg,
git-cliff-action, and gh-action-pypi-publish (version retained in trailing
comments).
@aquemy
aquemy merged commit 831d176 into main Jun 16, 2026
4 checks passed
@aquemy
aquemy deleted the ci/pin-release-actions-to-sha branch June 16, 2026 07:04
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.

1 participant