security(NOJIRA-1234): replace compromised codfish/semantic-release-a… - #101
Merged
davidsalvador-tf merged 1 commit intoJun 30, 2026
Merged
Conversation
…ction with cycjimmy/semantic-release-action
|
🥷 Code experts: pannago pannago has most 👩💻 activity in the files. See details
Activity based on git-commit:
Knowledge based on git-blame: ✨ Comment |
ivanilves
approved these changes
Jun 30, 2026
davidsalvador-tf
deleted the
security/replace-codfish-semantic-release-action
branch
June 30, 2026 12:05
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
codfish/semantic-release-actionwas the target of a supply chain attackon 2026-06-24 — its version tags (
v2–v5) were repointed to a commitcontaining a credential-stealing payload (the Miasma toolkit), targeting
GITHUB_TOKENandNPM_TOKENsecrets in CI runners. The upstreamrepository has since been disabled by GitHub for ToS violations.
This PR replaces it with
cycjimmy/semantic-release-action, awell-maintained, widely-used alternative, pinned to a commit SHA
rather than a floating tag, to remove this class of risk going forward.
What changed
codfish/semantic-release-action@vX→cycjimmy/semantic-release-action@b12c8f6015dc215fe37bc154d4ad456dd3833c90(v6.0.0)Verification
No functional change is expected —
cycjimmy/semantic-release-actionexposes the same inputs/outputs/env var contract (
GITHUB_TOKEN,NPM_TOKEN,branches,extra_plugins, etc.) as the action it replaces.Please re-run this workflow on a test branch before merging to confirm.
Created by Sourcegraph batch change
david.salvador/replace-codfish-semantic-release-action.