chore(deps): update stranske/workflows digest to a335f1a - #2513
chore(deps): update stranske/workflows digest to a335f1a#2513renovate[bot] wants to merge 1 commit into
Conversation
Workflow source neededPR #2513 needs either a linked GitHub issue or one valid non-issue Workflow Source before PR metadata automation can manage it safely. Please do one of:
Once a valid source is present, this warning will not be reposted. |
📝 WalkthroughWalkthroughTwo lines in Changesagents-guard workflow SHA bump
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning Tools execution failed with the following error: Failed to run tools: 13 INTERNAL: Received RST_STREAM with code 2 (Internal server error) Comment |
Automated Status SummaryHead SHA: c4bc79e
Coverage Overview
Updated automatically; will refresh on subsequent CI/Docker completions. Keepalive checklistScopeNo scope information available Tasks
Acceptance criteria
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b4414ce792
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| steps.eligibility.outputs.should-run == 'true' && | ||
| steps.api_client_base.outputs.available != 'true' | ||
| uses: "stranske/Workflows/.github/actions/setup-api-client@44965d8d784573c119fb63828c05c89256c5f3e1" # v1 | ||
| uses: "stranske/Workflows/.github/actions/setup-api-client@a335f1af2c35b8f35d2278f56e9af78792a09bf1" # v1 |
There was a problem hiding this comment.
Refresh the template-drift allowlist
When this consumer template changes, Health 74 Template Drift runs on templates/consumer-repo/.github/workflows/*.yml and compares the root/template pair against config/template-drift-allowlist.txt; the agents-guard.yml entry there still records the old template fingerprint (ff6f4a...) and reason for the previous 44965d8 pin, while this line changes the normalized template hash to 90fa914.... Any PR/push containing this commit will therefore report unallowlisted drift until the allowlist entry is re-baselined alongside the digest bump.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with 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.
Inline comments:
In `@templates/consumer-repo/.github/workflows/agents-guard.yml`:
- Line 114: The agents-guard.yml file in the consumer template repository is
sync-managed from the stranske/Workflows repository and should not be edited
directly. Revert the SHA changes made to the setup-api-client action reference
(at line 114 and line 183) in this file back to their original state. Instead,
make these updates in the source stranske/Workflows repository where the
agents-guard.yml workflow template originates, and then trigger a sync operation
to propagate the changes back to this consumer repository to avoid drift and
maintain consistency across deployments.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: ad70ffa2-67a0-49b5-8d5e-ed702925e9fd
📒 Files selected for processing (1)
templates/consumer-repo/.github/workflows/agents-guard.yml
🔗 Linked repositories identified
CodeRabbit considers these linked repositories for cross-repo context during reviews:
stranske/Template(auto-detected)stranske/Fine-Art-Archive(auto-detected)stranske/Ready(auto-detected)stranske/Workflows-Integration-Tests(auto-detected)
| steps.eligibility.outputs.should-run == 'true' && | ||
| steps.api_client_base.outputs.available != 'true' | ||
| uses: "stranske/Workflows/.github/actions/setup-api-client@44965d8d784573c119fb63828c05c89256c5f3e1" # v1 | ||
| uses: "stranske/Workflows/.github/actions/setup-api-client@a335f1af2c35b8f35d2278f56e9af78792a09bf1" # v1 |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟠 Major | 🏗️ Heavy lift
Do not update agents-*.yml directly in the consumer template repo.
This file path is sync-managed, so this SHA bump should be done in stranske/Workflows and then synced back; direct local edits here risk drift and overwrite on next sync.
As per coding guidelines, "templates/consumer-repo/.github/workflows/agents-*.yml: Do not edit agents-*.yml workflows locally; fix issues in stranske/Workflows and sync back to this consumer repository" and "templates/consumer-repo/{.github/workflows/agents-*.yml,...} ... do not edit locally unless documented as repo-specific."
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 `@templates/consumer-repo/.github/workflows/agents-guard.yml` at line 114, The
agents-guard.yml file in the consumer template repository is sync-managed from
the stranske/Workflows repository and should not be edited directly. Revert the
SHA changes made to the setup-api-client action reference (at line 114 and line
183) in this file back to their original state. Instead, make these updates in
the source stranske/Workflows repository where the agents-guard.yml workflow
template originates, and then trigger a sync operation to propagate the changes
back to this consumer repository to avoid drift and maintain consistency across
deployments.
Source: Coding guidelines
|
Closing as superseded by source fix #2514, which updates the root/template guard pins together and refreshes the template-drift allowlist. |
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update. You will not get PRs for the If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
This PR contains the following updates:
44965d8→a335f1aConfiguration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.