Skip to content

chore: Pin release-please-action to full commit SHA#33

Merged
keelerm84 merged 2 commits intomainfrom
semgrep-autofix/1774011694
Mar 23, 2026
Merged

chore: Pin release-please-action to full commit SHA#33
keelerm84 merged 2 commits intomainfrom
semgrep-autofix/1774011694

Conversation

@semgrep-code-launchdarkly
Copy link
Copy Markdown
Contributor

@semgrep-code-launchdarkly semgrep-code-launchdarkly bot commented Mar 20, 2026

Pin the googleapis/release-please-action to a full commit SHA for improved supply chain security.

Changes

  • Updated googleapis/release-please-action@v4 to use full commit SHA 7987652d64b4f86e094c6b42e1f2e99a6e019e3a (v4.1.3)
  • Added version comment for maintainability

Why

Pinning GitHub Actions to a full commit SHA is a security best practice. Version tags like v4 are mutable and can be updated by the repository owner at any time. By pinning to a specific commit SHA, we ensure the action code cannot change unexpectedly, mitigating the risk of supply chain attacks where a bad actor could inject malicious code into a tagged release.

Semgrep Finding Details

An action sourced from a third-party repository on GitHub is not pinned to a full length commit SHA. Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload.

@pkaeding@launchdarkly.com requested Semgrep Assistant generate this pull request to fix a finding.


⚠️ Review carefully before merging. This PR was generated by AI and may cause breaking changes or introduce new vulnerabilities.


Note

Low Risk
Low risk: this only changes the GitHub Actions workflow dependency reference, reducing supply-chain risk without altering application/runtime logic.

Overview
Updates the release-please GitHub Actions workflow to use a fully pinned googleapis/release-please-action commit SHA (annotated as v4.4.0) rather than the floating v4 tag, improving supply-chain immutability.

Written by Cursor Bugbot for commit c3e7e74. This will update automatically on new commits. Configure here.

Pin the googleapis/release-please-action to a full commit SHA for improved supply chain security.

## Changes
- Updated `googleapis/release-please-action@v4` to use full commit SHA `7987652d64b4f86e094c6b42e1f2e99a6e019e3a` (v4.1.3)
- Added version comment for maintainability

## Why
Pinning GitHub Actions to a full commit SHA is a security best practice. Version tags like `v4` are mutable and can be updated by the repository owner at any time. By pinning to a specific commit SHA, we ensure the action code cannot change unexpectedly, mitigating the risk of supply chain attacks where a bad actor could inject malicious code into a tagged release.

## Semgrep Finding Details
An action sourced from a third-party repository on GitHub is not pinned to a full length commit SHA. Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload.

@pkaeding@launchdarkly.com requested Semgrep Assistant generate this pull request to fix [a finding](https://semgrep.dev/orgs/launchdarkly/findings/726909399).
@pkaeding pkaeding marked this pull request as ready for review March 20, 2026 13:11
@pkaeding pkaeding requested a review from a team as a code owner March 20, 2026 13:11
Copy link
Copy Markdown

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.

@keelerm84 keelerm84 merged commit b296fec into main Mar 23, 2026
8 checks passed
@keelerm84 keelerm84 deleted the semgrep-autofix/1774011694 branch March 23, 2026 13:24
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.

2 participants