chore: migrate digicert signing action to Node.js 24 successor - BED-8168#196
chore: migrate digicert signing action to Node.js 24 successor - BED-8168#196StranDutton wants to merge 1 commit into
Conversation
WalkthroughSwaps the DigiCert code-signing action in ChangesPublish workflow updates
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…8168 digicert/ssm-code-signing has been deprecated by the upstream maintainer and will not receive further updates, including a Node.js 24 runtime upgrade. Per the maintainer's guidance, migrate to the successor action digicert/code-signing-software-trust-action@v1.2.1, which runs on Node.js 24 and preserves the PKCS11_CONFIG output our sign job consumes. Upstream notice: digicert/ssm-code-signing#60
8f741ad to
be00a7d
Compare
|
Pushed a temporary commit to confirm that the signing step still works as expected with the update! Link to workflow run (successful sign steps are evidence): https://github.com/SpecterOps/AzureHound/actions/runs/25814411820 |
digicert/ssm-code-signing has been deprecated by the upstream maintainer and will not receive further updates, including a Node.js 24 runtime upgrade. Per the maintainer's post, migrate to the successor action
digicert/code-signing-software-trust-action@v1.2.1, which runs on Node.js 24. Needed because our runners will stop being able to run node20 dependencies later this yearSummary by CodeRabbit