ci: bump and pin third-party actions to commit SHAs - #188
Draft
GuillaumeLagrange wants to merge 2 commits into
Draft
ci: bump and pin third-party actions to commit SHAs#188GuillaumeLagrange wants to merge 2 commits into
GuillaumeLagrange wants to merge 2 commits into
Conversation
Every `uses:` reference is now pinned to a full commit SHA with a version comment, managed by pinact (`.pinact.yaml`). This removes the mutable-tag supply-chain risk and clears the Node 20 deprecation warning, which came from `actions/checkout@v4`, not from CodSpeedHQ/action. `CodSpeedHQ/action@main` is deliberately left unpinned so CI keeps exercising the action's unreleased changes; pinact ignores it. Replace `actions/upload-release-asset@v1.0.2` with `gh release upload`: that action is archived and still targets Node 12, which current runners no longer execute. The release tag now flows from the `publish` job as a `tag` output instead of the `upload_url` output it replaces. Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: Guillaume Lagrange <guillaume@glagrange.eu>
GuillaumeLagrange
force-pushed
the
chore/pin-github-actions
branch
from
August 18, 2026 13:42
b4c5d5f to
dccdc66
Compare
Hooray! CodSpeed harness just leveled up!The base and head of this comparison were measured with different runner settings, so their benchmark values are not directly comparable. What changed between base and head:
Re-run the base with the same settings to get a valid performance comparison. Comparing 
|
Unable to generate the flame graphsThe performance report has correctly been generated, but there was an internal error while generating the flame graphs for this run. We're working on fixing the issue. Feel free to contact us on Discord or at support@codspeed.io if the issue persists. |
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
1 participant
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.
Every
uses:reference is now pinned to a full commit SHA with a version comment, managed by pinact (.pinact.yaml). This removes the mutable-tag supply-chain risk and clears the Node 20 deprecation warning, which came fromactions/checkout@v4, not from CodSpeedHQ/action.CodSpeedHQ/action@mainis deliberately left unpinned so CI keeps exercising the action's unreleased changes; pinact ignores it.Replace
actions/upload-release-asset@v1.0.2withgh release upload: that action is archived and still targets Node 12, which current runners no longer execute. The release tag now flows from thepublishjob as atagoutput instead of theupload_urloutput it replaces.