Skip to content

chore(deps): update stranske/workflows digest to 44965d8 - #2035

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

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 62ed0a844965d8

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.

Summary by CodeRabbit

  • Chores
    • Updated internal continuous integration workflow infrastructure to use a newer version of a shared build action component.

@renovate
renovate Bot requested a review from stranske as a code owner June 23, 2026 06:50
@renovate
renovate Bot had a problem deploying to agent-standard June 23, 2026 06:50 Failure
@coderabbitai

coderabbitai Bot commented Jun 23, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

Two lines in .github/workflows/agents-guard.yml update the pinned commit SHA of the stranske/Workflows/.../setup-api-client GitHub Action used in the "Workflows fallback" steps for both the pull_request_target and pull_request event paths.

Changes

Action Pin Bump

Layer / File(s) Summary
Bump pinned SHA in both fallback steps
.github/workflows/agents-guard.yml
Lines 114 and 183 update the pinned commit SHA of the setup-api-client fallback action for the pull_request_target and pull_request jobs; all other step configuration remains unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • stranske/Portable-Alpha-Extension-Model#2023: Updates the same "Workflows fallback" setup-api-client step(s) in agents-guard.yml for both pull_request_target and pull_request, changing the pinned SHA from an older value to a newer one — the same pattern as this PR.

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 clearly and specifically describes the main change: updating a GitHub Action dependency with the exact digest reference.
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

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

@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: 80efea9a67

ℹ️ 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@62ed0a86b5d57062ac3d04f4519e3998858e2d96" # v1
uses: "stranske/Workflows/.github/actions/setup-api-client@44965d8d784573c119fb63828c05c89256c5f3e1" # 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 Fix the Workflows-owned guard pin at the source

This repo's AGENTS.md says agents-*.yml files are Workflows-owned and must be fixed in stranske/Workflows first; this updates only the consumer copy. I checked the upstream Workflows compare for 62ed0a8..44965d8, and the source consumer template still pins this fallback action to 62ed0a8, so this change creates template drift that the next sync will revert or keep reporting as divergence. Please update the Workflows template/sync source first, then sync this file.

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 @.github/workflows/agents-guard.yml:
- Line 114: The pin bump modification to the setup-api-client action in
agents-guard.yml at line 114 (and line 183) should not be edited locally in this
consumer repository since this is a synced workflow file. Instead, revert both
of these pin changes in agents-guard.yml and make the same pin bump change in
the source repository at stranske/Workflows, then allow the workflow
synchronization mechanism to propagate the update to this consumer copy
automatically.
🪄 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: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: b50561c6-2df6-4f0d-bf9e-5250180a5ba3

📥 Commits

Reviewing files that changed from the base of the PR and between ee67b38 and 80efea9.

📒 Files selected for processing (1)
  • .github/workflows/agents-guard.yml
🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

  • stranske/Workflows (auto-detected)
  • stranske/Template (auto-detected)
📜 Review details
⏰ Context from checks skipped due to timeout. (1)
  • GitHub Check: Integration Tests
🧰 Additional context used
📓 Path-based instructions (3)
.github/workflows/**/*.yml

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

Do not use top-level permissions block on workflow_call reusable workflows as it conflicts with caller permissions

Files:

  • .github/workflows/agents-guard.yml
.github/workflows/*.yml

📄 CodeRabbit inference engine (CLAUDE.md)

Reference reusable workflows with @main by default unless intentionally pinning to a specific commit SHA for a controlled reason

Reference reusable workflows with @main in first-party consumers unless intentionally pinning to an exact commit SHA for a documented reason

Files:

  • .github/workflows/agents-guard.yml
.github/workflows/agents-*.yml

📄 CodeRabbit inference engine (CLAUDE.md)

Synced workflows (agents-*.yml), autofix logic, prompts, scripts, and consumer docs are managed through .github/sync-manifest.yml in stranske/Workflows and should not be edited locally — fix issues in the Workflows source repository instead

Edit agent workflow files (agents-*.yml) in stranske/Workflows, not in the consumer repo

Files:

  • .github/workflows/agents-guard.yml
🔀 Multi-repo context stranske/Workflows, stranske/Template

Linked repositories findings

stranske/Workflows [::stranske/Workflows::]

GitHub Action: setup-api-client

The PR updates a pinned reference to stranske/Workflows/.github/actions/setup-api-client. This action was updated as part of commit dfe0854 (fix: harden synced design system helpers #2511``), which synchronized the action definition across the Workflows repository and its consumer template.

Action Interface (Backward Compatible):

Inputs (all required: false):

  • secrets: JSON-encoded secrets object
  • github_token: Primary GitHub token
  • Individual secret fallbacks: service_bot_pat, actions_bot_pat, owner_pr_pat, agents_automation_pat
  • App credentials: workflows_app_id, workflows_app_private_key, keepalive_app_id, keepalive_app_private_key, gh_app_id, gh_app_private_key, app_1_id/id_private_key, app_2_id/id_private_key
  • Configuration: install_dir, skip_deps (default: 'false'), verbose (default: 'false')

Outputs (unchanged):

  • token_count: Number of tokens exported to environment
  • available_tokens: Comma-separated list of available token names
  • setup_contract: Redacted machine-readable setup/auth/dependency contract JSON

Template Drift Tracking (config/template-drift-allowlist.txt):

reason = Intentional divergence re-baselined 2026-06-23: root and consumer guard workflows differ for pinned consumer actions/App-token setup; root and consumer setup-api-client pins were refreshed to the current Workflows main digest 44965d8.

This confirms the version pin update was a deliberate, coordinated sync operation.

stranske/Template [::stranske/Template::]

Fallback Usage in agents-guard.yml:

The setup-api-client action is referenced as a fallback step in two scenarios:

  1. pull_request_target event: Used only when steps.api_client_base.outputs.available != 'true'
  2. pull_request event: Used only when steps.api_client_head.outputs.available != 'true'

Current pinned reference:

uses: "stranske/Workflows/.github/actions/setup-api-client@62ed0a86b5d57062ac3d04f4519e3998858e2d96" # v1

Local Copy Status: Template maintains its own synced copy at ./.github/actions/setup-api-client/action.yml (572 lines, identical to Workflows version). The remote reference is only invoked as a fallback when local execution is unavailable.

Invocation Pattern (both occurrences):

with:
  secrets: ${{ toJSON(secrets) }}
  github_token: ${{ github.token }}

Risk Assessment

No Breaking Changes: All action inputs are optional; outputs remain unchanged.

Backward Compatible: Existing calls to the old version (62ed0a8) will work identically with the new version (44965d8).

Coordinated Sync: The drift allowlist confirms this was part of a synchronized update (commit dfe0854) across both repositories, reducing risk of misalignment.

Minimal Exposure: Template repo's dependence on the remote action is limited to fallback scenarios, as it maintains its own local copy.

steps.eligibility.outputs.should-run == 'true' &&
steps.api_client_base.outputs.available != 'true'
uses: "stranske/Workflows/.github/actions/setup-api-client@62ed0a86b5d57062ac3d04f4519e3998858e2d96" # v1
uses: "stranske/Workflows/.github/actions/setup-api-client@44965d8d784573c119fb63828c05c89256c5f3e1" # 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

Move this pin bump to the Workflows source repo, not this consumer copy.

Line 114 and Line 183 modify a synced agents-*.yml workflow locally. This change should be made in stranske/Workflows and propagated via sync; otherwise it risks drift/overwrite in consumers.

As per coding guidelines: “Edit agent workflow files (agents-*.yml) in stranske/Workflows, not in the consumer repo” and “Synced workflows (agents-*.yml) ... should not be edited locally — fix issues in the Workflows source repository instead.”

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 pin bump modification to
the setup-api-client action in agents-guard.yml at line 114 (and line 183)
should not be edited locally in this consumer repository since this is a synced
workflow file. Instead, revert both of these pin changes in agents-guard.yml and
make the same pin bump change in the source repository at stranske/Workflows,
then allow the workflow synchronization mechanism to propagate the update to
this consumer copy automatically.

Source: Coding guidelines

@stranske

Copy link
Copy Markdown
Owner

Closing as superseded: this Renovate PR directly edits the managed synced workflow file .github/workflows/agents-guard.yml at the pre-fix Workflows digest 44965d8. The source-of-truth fix landed in stranske/Workflows#2511, and replacement sync was dispatched via stranske/Workflows Maint 68 run 28012899382.

@stranske stranske closed this Jun 23, 2026
@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 44965d8 update again.

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

@renovate
renovate Bot deleted the renovate/stranske-workflows-digest branch June 23, 2026 08:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant