Skip to content

fix(ci): pin EricCrosson/retry to exact version and SHA256 digest#8978

Merged
gokulhost merged 1 commit into
masterfrom
gokuldevaraju330/wcn-865-fix-flaky-yarn-audit-ci-step-with-retry-logic
Jun 10, 2026
Merged

fix(ci): pin EricCrosson/retry to exact version and SHA256 digest#8978
gokulhost merged 1 commit into
masterfrom
gokuldevaraju330/wcn-865-fix-flaky-yarn-audit-ci-step-with-retry-logic

Conversation

@gokulhost

Copy link
Copy Markdown
Contributor

Summary

Follow-up to #8975: addresses supply-chain security concern raised by @Louis-Varin in code review.

  • Pins EricCrosson/retry from floating @v1 to exact @v1.4.8 in both npmjs-release.yml and publish.yml
  • Adds SHA256 digest (sha256-15224553...) of the x86_64-unknown-linux-gnu binary so BitGo/install-github-release-binary verifies the download before executing it

Note: BitGo/retry is @bitgo-private/retry, a TypeScript npm library with no binary release assets — it cannot be used as a target for install-github-release-binary. Pinning the EricCrosson binary with a digest is the equivalent supply-chain control.

Linear: WCN-865

Test plan

  • CI passes on this PR
  • Confirm install-github-release-binary checksum validation passes on the runner

🤖 Generated with Claude Code

@gokulhost gokulhost requested review from a team as code owners June 9, 2026 22:29
@linear-code

linear-code Bot commented Jun 9, 2026

Copy link
Copy Markdown

WCN-865

Pins the retry binary to an exact version and checksum to address
supply-chain security concerns in the npm publish pipeline.

WCN-865
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@gokulhost gokulhost force-pushed the gokuldevaraju330/wcn-865-fix-flaky-yarn-audit-ci-step-with-retry-logic branch from 58f8dbf to 326cc6e Compare June 9, 2026 22:32
@gokulhost gokulhost merged commit 5b03033 into master Jun 10, 2026
22 checks passed
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