Skip to content

chore(deps): update stranske/workflows digest to a335f1a - #2513

Closed
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/stranske-workflows-digest
Closed

chore(deps): update stranske/workflows digest to a335f1a#2513
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/stranske-workflows-digest

Conversation

@renovate

@renovate renovate Bot commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
stranske/Workflows (changelog) action digest 44965d8a335f1a

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the dependencies Dependency updates label Jun 23, 2026
@renovate
renovate Bot temporarily deployed to agent-standard June 23, 2026 09:43 Inactive
@github-actions github-actions Bot added the agents:allow-change Permit workflow edits when justification provided label Jun 23, 2026
@agents-workflows-bot

Copy link
Copy Markdown
Contributor

Workflow source needed

PR #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:

  • Add <!-- meta:issue:123 --> or a normal Closes #123 / Related to #123 line.
  • Check one Workflow Source option in the PR body.
  • Add a hidden marker such as <!-- workflow-source:local_request -->, <!-- workflow-source:manual_remote -->, <!-- workflow-source:review_followup -->, <!-- workflow-source:sync_campaign -->, or <!-- workflow-source:dependabot -->.
  • Add a workflow source label such as workflow:source-direct-pr, workflow:source-local-request, workflow:source-review-followup, workflow:source-sync, or workflow:no-automation.

Once a valid source is present, this warning will not be reposted.

@coderabbitai

coderabbitai Bot commented Jun 23, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

Two lines in templates/consumer-repo/.github/workflows/agents-guard.yml are updated to pin the stranske/Workflows/.github/actions/setup-api-client fallback action to a newer commit SHA (a335f1af... replacing 44965d8d...), applied identically to both the pull_request_target and pull_request trigger paths.

Changes

agents-guard workflow SHA bump

Layer / File(s) Summary
Update fallback action SHA for both workflow triggers
templates/consumer-repo/.github/workflows/agents-guard.yml
The pinned commit SHA for the stranske/Workflows/.github/actions/setup-api-client fallback step is updated from 44965d8d... to a335f1af... at lines 114 and 183, covering both the pull_request_target and pull_request paths.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • stranske/Workflows#2471: Updates the same agents-guard.yml fallback step by repinning the same setup-api-client action to a different commit SHA.
  • stranske/Workflows#2472: Also modifies the agents-guard.yml "Setup API client (Workflows fallback)" steps with a different pinned revision of the same action.
  • stranske/Workflows#2503: Performs the same repinning pattern in agents-guard.yml for both pull_request_target and pull_request fallback paths.

Suggested labels

agents:allow-change

Suggested reviewers

  • stranske
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: updating a dependency digest to a specific version hash, which matches the actual changeset.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch renovate/stranske-workflows-digest

Warning

Tools execution failed with the following error:

Failed to run tools: 13 INTERNAL: Received RST_STREAM with code 2 (Internal server error)


Comment @coderabbitai help to get the list of available commands.

@stranske-keepalive

stranske-keepalive Bot commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

Automated Status Summary

Head SHA: c4bc79e
Latest Runs: ⏳ pending — Gate
Required contexts: Gate / gate, Health 45 Agents Guard / guard
Required: core tests (3.12): ⏳ pending, core tests (3.13): ⏳ pending, docker smoke: ⏳ pending, gate: ⏳ pending

Workflow / Job Result Logs
(no jobs reported) ⏳ pending

Coverage Overview

  • Coverage history entries: 0

Updated automatically; will refresh on subsequent CI/Docker completions.


Keepalive checklist

Scope

No scope information available

Tasks

  • No tasks defined

Acceptance criteria

  • No acceptance criteria defined

@renovate
renovate Bot temporarily deployed to agent-standard June 23, 2026 09:44 Inactive

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 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

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge 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 👍 / 👎.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

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

📥 Commits

Reviewing files that changed from the base of the PR and between a335f1a and b4414ce.

📒 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

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

📐 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

@stranske

Copy link
Copy Markdown
Owner

Closing as superseded by source fix #2514, which updates the root/template guard pins together and refreshes the template-drift allowlist.

@stranske stranske closed this Jun 23, 2026
@stranske
stranske deleted the renovate/stranske-workflows-digest branch June 23, 2026 10:33
@renovate

renovate Bot commented Jun 23, 2026

Copy link
Copy Markdown
Contributor Author

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for the stranske/Workflows a335f1a update again.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

agents:allow-change Permit workflow edits when justification provided dependencies Dependency updates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant