Repository navigation
Pin the review workflow to code-review v0.3.1's commit SHA - #19
Conversation
There was a problem hiding this comment.
🤖 NCode Review at 8c260e4: 1 new finding on the changed lines.
Not on a changed line:
- 🟡 F2 Nit: Usage example still uses -Ref v0.3.0
.template/Update-Project.ps1:56. The script's usage example passes -Ref v0.3.0, while the workflow now pins v0.3.1. Fix: Is the example meant to show the current release? If so, change it to v0.3.1. If it's only illustrative, leave it.
🤖 Review completeVerdict: ✅ Approve — No findings. 3 reviewers run — 0 findings (run details)
Skipped: api-compat, architecture, completeness, correctness, data-model, infrastructure, intent, performance, security, tests Trial: findings are posted as review threads and in the check run. $0.12 on Amazon Bedrock, 23s, at de6aae0. (how to interact) |
|
F2 (not on a changed line, |
|
/review |
Pins
NCodeGroup/code-reviewto v0.3.1's full commit SHA,eaa9846049fdda1ce724fc34107391ba5f6d8708, with the tag in a comment, in place of the tagv0.3.0, and rewords the comment that explains the pin.A tag pin, even an immutable release's, makes CodeQL's
extendedsuite report the action as unpinned (actions/unpinned-tag) at every bump: NCodeGroup/identity-platform#26 tested v0.3.1, the first immutable release, and it was flagged the same way. A SHA is the one pin nobody can move, and Dependabot updates the SHA and the comment together. v0.3.1 has the same engine as v0.3.0.