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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Informational (pre-existing, not introduced by this PR): this reusable workflow runs via
workflow_runwithcontents: write/issues: write/pull-requests: writebut is pinned to a mutable tag (@v1.0.4). A tag can be force-moved upstream, so it doesn't give the integrity guarantee of a commit SHA. For a write-privileged third-party workflow, consider pinning to a full commit SHA (e.g....publish.yml@<40-char-sha> # v1.0.4). The same applies tobenchmark.yml:81; out of scope for this bump, just flagging.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Addressed in db03150. Both the benchmark recorder and the write-privileged reusable publisher are now pinned to the full v1.0.4 release commit SHA, with the version comment retained for Dependabot.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Restored both references to @v1.0.4 in 1b8c114. These repositories share the xgo-dev trust boundary, and this PR remains focused on the publisher bug fix; commit pinning can be considered separately if the project adopts it consistently.