Skip to content

chore(deps): update stranske/workflows digest to 62ed0a8 #779

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
renovate wants to merge 1 commit into from
Closed

chore(deps): update stranske/workflows digest to 62ed0a8 #779

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .github/workflows/agents-guard.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -111,7 +111,7 @@ jobs:
github.event_name == 'pull_request_target' &&
steps.eligibility.outputs.should-run == 'true' &&
steps.api_client_base.outputs.available != 'true'
uses: "stranske/Workflows/.github/actions/setup-api-client@c2537cc959f2ce05926c4639d25b90678abc97bc" # v1
uses: "stranske/Workflows/.github/actions/setup-api-client@62ed0a86b5d57062ac3d04f4519e3998858e2d96" # v1

@coderabbitai coderabbitai Bot Jun 22, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major | 🏗️ Heavy lift

Do not patch this synced workflow locally; update upstream first.

This file is in the synced agents-*.yml set, so changing pinned SHAs here violates the sync contract and can be overwritten/drift from source-of-truth. Please apply this SHA bump in stranske/Workflows and sync it back through the manifest-managed flow.

As per coding guidelines: “Synced workflows … are managed through .github/sync-manifest.yml … do not edit them locally unless fixing upstream first” and “Do not edit synced workflows (agents-*.yml …) locally; fix them in stranske/Workflows first.”

Also applies to: 183-183

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/agents-guard.yml at line 114, The pinned SHA for the
stranske/Workflows/.github/actions/setup-api-client action in agents-guard.yml
is part of a synced workflow set managed through .github/sync-manifest.yml and
should not be edited locally. Instead of updating the SHA directly in this file,
apply the change upstream in the stranske/Workflows repository first, then
trigger the sync process through the manifest-managed flow to bring the changes
back into agents-guard.yml. This applies to both line 114 and line 183 where the
setup-api-client action is referenced.

Source: Coding guidelines

with:
secrets: ${{ toJSON(secrets) }}
github_token: ${{ github.token }}
Expand Down Expand Up @@ -180,7 +180,7 @@ jobs:
steps.eligibility.outputs.should-run == 'true' &&
github.event_name == 'pull_request' &&
steps.api_client_head.outputs.available != 'true'
uses: "stranske/Workflows/.github/actions/setup-api-client@c2537cc959f2ce05926c4639d25b90678abc97bc" # v1
uses: "stranske/Workflows/.github/actions/setup-api-client@62ed0a86b5d57062ac3d04f4519e3998858e2d96" # v1
with:
secrets: ${{ toJSON(secrets) }}
github_token: ${{ github.token }}
Expand Down
Loading