Conversation
SummaryThis PR unpins the What reviewers should knowScope: Single line change in Key consideration: Moving from a pinned commit SHA to a floating version tag means the action's behavior may change unexpectedly when v3 gets new releases. If stability is preferred, the pinned approach is safer; if staying current with fixes is priority, this is the right approach. Context: The vault-action-wrapper is used to retrieve secrets for the dogfood workflow, so review whether the team is comfortable with automatic updates to this security-sensitive component.
|
There was a problem hiding this comment.
LGTM! ✅
Clean, correct alignment change. Every other workflow in the repository (build.yml, RequestReview.yml, PullRequestClosed.yml, PullRequestCreated.yml, ToggleLockBranch.yml, SubmitReview.yml, releasability.yaml) already uses SonarSource/vault-action-wrapper@v3. This PR brings dogfood.yml into line with the rest of the codebase — it was the only remaining workflow still on the old pinned commit SHA.
|





No description provided.