Skip to content

chore(deps): bump the actions group with 10 updates#938

Closed
dependabot[bot] wants to merge 1951 commits intodevelopfrom
dependabot/github_actions/actions-fc489eec64
Closed

chore(deps): bump the actions group with 10 updates#938
dependabot[bot] wants to merge 1951 commits intodevelopfrom
dependabot/github_actions/actions-fc489eec64

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github Apr 11, 2026

Bumps the actions group with 10 updates:

Package From To
actions/checkout 4.3.1 6.0.2
dorny/paths-filter 3.0.2 4.0.1
actions/github-script 8.0.0 9.0.0
actions/upload-artifact 4.6.2 7.0.1
actions/cache 4.3.0 5.0.4
docker/build-push-action 7.0.0 7.1.0
github/codeql-action 3.35.1 4.35.1
actions/setup-python 5.6.0 6.2.0
goreleaser/goreleaser-action 9a127d869fb706213d29cdf8eef3a4ea2b869415 ec59f474b9834571250b370d4735c50f8e2d1e29
ossf/scorecard-action 2.4.0 2.4.3

Updates actions/checkout from 4.3.1 to 6.0.2

Release notes

Sourced from actions/checkout's releases.

v6.0.2

What's Changed

Full Changelog: actions/checkout@v6.0.1...v6.0.2

v6.0.1

What's Changed

Full Changelog: actions/checkout@v6...v6.0.1

v6.0.0

What's Changed

Full Changelog: actions/checkout@v5.0.0...v6.0.0

v6-beta

What's Changed

Updated persist-credentials to store the credentials under $RUNNER_TEMP instead of directly in the local git config.

This requires a minimum Actions Runner version of v2.329.0 to access the persisted credentials for Docker container action scenarios.

v5.0.1

What's Changed

Full Changelog: actions/checkout@v5...v5.0.1

v5.0.0

What's Changed

⚠️ Minimum Compatible Runner Version

v2.327.1
Release Notes

... (truncated)

Changelog

Sourced from actions/checkout's changelog.

Changelog

v6.0.2

v6.0.1

v6.0.0

v5.0.1

v5.0.0

v4.3.1

v4.3.0

v4.2.2

v4.2.1

v4.2.0

v4.1.7

v4.1.6

... (truncated)

Commits

Updates dorny/paths-filter from 3.0.2 to 4.0.1

Release notes

Sourced from dorny/paths-filter's releases.

v4.0.1

What's Changed

New Contributors

Full Changelog: dorny/paths-filter@v4.0.0...v4.0.1

v4.0.0

What's Changed

New Contributors

Full Changelog: dorny/paths-filter@v3.0.3...v4.0.0

v3.0.3

What's Changed

New Contributors

Full Changelog: dorny/paths-filter@v3...v3.0.3

Changelog

Sourced from dorny/paths-filter's changelog.

Changelog

v4.0.0

v3.0.3

v3.0.2

v3.0.1

v3.0.0

v2.11.1

v2.11.0

v2.10.2

v2.10.1

v2.10.0

v2.9.3

v2.9.2

v2.9.1

v2.9.0

... (truncated)

Commits
  • fbd0ab8 feat: add merge_group event support
  • efb1da7 feat: add dist/ freshness check to PR workflow
  • d8f7b06 Merge pull request #302 from dorny/issue-299
  • addbc14 Update README for v4
  • 9d7afb8 Update CHANGELOG for v4.0.0
  • 782470c Merge branch 'releases/v3'
  • d1c1ffe Update CHANGELOG for v3.0.3
  • ce10459 Merge pull request #294 from saschabratton/master
  • 5f40380 feat: update action runtime to node24
  • 668c092 Merge pull request #279 from wardpeet/patch-1
  • Additional commits viewable in compare view

Updates actions/github-script from 8.0.0 to 9.0.0

Release notes

Sourced from actions/github-script's releases.

v9.0.0

New features:

  • getOctokit factory function — Available directly in the script context. Create additional authenticated Octokit clients with different tokens for multi-token workflows, GitHub App tokens, and cross-org access. See Creating additional clients with getOctokit for details and examples.
  • Orchestration ID in user-agent — The ACTIONS_ORCHESTRATION_ID environment variable is automatically appended to the user-agent string for request tracing.

Breaking changes:

  • require('@actions/github') no longer works in scripts. The upgrade to @actions/github v9 (ESM-only) means require('@actions/github') will fail at runtime. If you previously used patterns like const { getOctokit } = require('@actions/github') to create secondary clients, use the new injected getOctokit function instead — it's available directly in the script context with no imports needed.
  • getOctokit is now an injected function parameter. Scripts that declare const getOctokit = ... or let getOctokit = ... will get a SyntaxError because JavaScript does not allow const/let redeclaration of function parameters. Use the injected getOctokit directly, or use var getOctokit = ... if you need to redeclare it.
  • If your script accesses other @actions/github internals beyond the standard github/octokit client, you may need to update those references for v9 compatibility.

What's Changed

New Contributors

Full Changelog: actions/github-script@v8.0.0...v9.0.0

Commits
  • 3a2844b Merge pull request #700 from actions/salmanmkc/expose-getoctokit + prepare re...
  • ca10bbd fix: use @​octokit/core/types import for v7 compatibility
  • 86e48e2 merge: incorporate main branch changes
  • c108472 chore: rebuild dist for v9 upgrade and getOctokit factory
  • afff112 Merge pull request #712 from actions/salmanmkc/deployment-false + fix user-ag...
  • ff8117e ci: fix user-agent test to handle orchestration ID
  • 81c6b78 ci: use deployment: false to suppress deployment noise from integration tests
  • 3953caf docs: update README examples from @​v8 to @​v9, add getOctokit docs and v9 brea...
  • c17d55b ci: add getOctokit integration test job
  • a047196 test: add getOctokit integration tests via callAsyncFunction
  • Additional commits viewable in compare view

Updates actions/upload-artifact from 4.6.2 to 7.0.1

Release notes

Sourced from actions/upload-artifact's releases.

v7.0.1

What's Changed

Full Changelog: actions/upload-artifact@v7...v7.0.1

v7.0.0

v7 What's new

Direct Uploads

Adds support for uploading single files directly (unzipped). Callers can set the new archive parameter to false to skip zipping the file during upload. Right now, we only support single files. The action will fail if the glob passed resolves to multiple files. The name parameter is also ignored with this setting. Instead, the name of the artifact will be the name of the uploaded file.

ESM

To support new versions of the @actions/* packages, we've upgraded the package to ESM.

What's Changed

New Contributors

Full Changelog: actions/upload-artifact@v6...v7.0.0

v6.0.0

v6 - What's new

[!IMPORTANT] actions/upload-artifact@v6 now runs on Node.js 24 (runs.using: node24) and requires a minimum Actions Runner version of 2.327.1. If you are using self-hosted runners, ensure they are updated before upgrading.

Node.js 24

This release updates the runtime to Node.js 24. v5 had preliminary support for Node.js 24, however this action was by default still running on Node.js 20. Now this action by default will run on Node.js 24.

What's Changed

Full Changelog: actions/upload-artifact@v5.0.0...v6.0.0

v5.0.0

What's Changed

... (truncated)

Commits
  • 043fb46 Merge pull request #797 from actions/yacaovsnc/update-dependency
  • 634250c Include changes in typespec/ts-http-runtime 0.3.5
  • e454baa Readme: bump all the example versions to v7 (#796)
  • 74fad66 Update the readme with direct upload details (#795)
  • bbbca2d Support direct file uploads (#764)
  • 589182c Upgrade the module to ESM and bump dependencies (#762)
  • 47309c9 Merge pull request #754 from actions/Link-/add-proxy-integration-tests
  • 02a8460 Add proxy integration test
  • b7c566a Merge pull request #745 from actions/upload-artifact-v6-release
  • e516bc8 docs: correct description of Node.js 24 support in README
  • Additional commits viewable in compare view

Updates actions/cache from 4.3.0 to 5.0.4

Release notes

Sourced from actions/cache's releases.

v5.0.4

What's Changed

New Contributors

Full Changelog: actions/cache@v5...v5.0.4

v5.0.3

What's Changed

Full Changelog: actions/cache@v5...v5.0.3

v.5.0.2

v5.0.2

What's Changed

When creating cache entries, 429s returned from the cache service will not be retried.

v5.0.1

[!IMPORTANT] actions/cache@v5 runs on the Node.js 24 runtime and requires a minimum Actions Runner version of 2.327.1.

If you are using self-hosted runners, ensure they are updated before upgrading.


v5.0.1

What's Changed

v5.0.0

What's Changed

... (truncated)

Changelog

Sourced from actions/cache's changelog.

Releases

How to prepare a release

[!NOTE]
Relevant for maintainers with write access only.

  1. Switch to a new branch from main.
  2. Run npm test to ensure all tests are passing.
  3. Update the version in https://github.com/actions/cache/blob/main/package.json.
  4. Run npm run build to update the compiled files.
  5. Update this https://github.com/actions/cache/blob/main/RELEASES.md with the new version and changes in the ## Changelog section.
  6. Run licensed cache to update the license report.
  7. Run licensed status and resolve any warnings by updating the https://github.com/actions/cache/blob/main/.licensed.yml file with the exceptions.
  8. Commit your changes and push your branch upstream.
  9. Open a pull request against main and get it reviewed and merged.
  10. Draft a new release https://github.com/actions/cache/releases use the same version number used in package.json
    1. Create a new tag with the version number.
    2. Auto generate release notes and update them to match the changes you made in RELEASES.md.
    3. Toggle the set as the latest release option.
    4. Publish the release.
  11. Navigate to https://github.com/actions/cache/actions/workflows/release-new-action-version.yml
    1. There should be a workflow run queued with the same version number.
    2. Approve the run to publish the new version and update the major tags for this action.

Changelog

5.0.4

  • Bump minimatch to v3.1.5 (fixes ReDoS via globstar patterns)
  • Bump undici to v6.24.1 (WebSocket decompression bomb protection, header validation fixes)
  • Bump fast-xml-parser to v5.5.6

5.0.3

5.0.2

  • Bump @actions/cache to v5.0.3 #1692

5.0.1

  • Update @azure/storage-blob to ^12.29.1 via @actions/cache@5.0.1 #1685

5.0.0

[!IMPORTANT] actions/cache@v5 runs on the Node.js 24 runtime and requires a minimum Actions Runner version of 2.327.1.

... (truncated)

Commits

Updates docker/build-push-action from 7.0.0 to 7.1.0

Release notes

Sourced from docker/build-push-action's releases.

v7.1.0

Full Changelog: docker/build-push-action@v7.0.0...v7.1.0

Commits
  • bcafcac Merge pull request #1509 from docker/dependabot/npm_and_yarn/vite-7.3.2
  • 18e62f1 Merge pull request #1510 from docker/dependabot/npm_and_yarn/lodash-4.18.1
  • 46580d2 chore: update generated content
  • 3f80b25 chore(deps): Bump lodash from 4.17.23 to 4.18.1
  • efeec95 Merge pull request #1505 from crazy-max/refactor-git-context
  • ddf04b0 Merge pull request #1511 from docker/dependabot/github_actions/crazy-max-dot-...
  • db08d97 chore(deps): Bump the crazy-max-dot-github group with 2 updates
  • ef1fb96 Merge pull request #1508 from docker/dependabot/github_actions/docker/login-a...
  • 2d8f2a1 chore: update generated content
  • 919ac7b fix test since secrets are not written to temp path anymore
  • Additional commits viewable in compare view

Updates github/codeql-action from 3.35.1 to 4.35.1

Release notes

Sourced from github/codeql-action's releases.

v4.35.1

v4.35.0

v4.34.1

  • Downgrade default CodeQL bundle version to 2.24.3 due to issues with a small percentage of Actions and JavaScript analyses. #3762

v4.34.0

  • Added an experimental change which disables TRAP caching when improved incremental analysis is enabled, since improved incremental analysis supersedes TRAP caching. This will improve performance and reduce Actions cache usage. We expect to roll this change out to everyone in March. #3569
  • We are rolling out improved incremental analysis to C/C++ analyses that use build mode none. We expect this rollout to be complete by the end of April 2026. #3584
  • Update default CodeQL bundle version to 2.25.0. #3585

v4.33.0

  • Upcoming change: Starting April 2026, the CodeQL Action will skip collecting file coverage information on pull requests to improve analysis performance. File coverage information will still be computed on non-PR analyses. Pull request analyses will log a warning about this upcoming change. #3562

    To opt out of this change:

    • Repositories owned by an organization: Create a custom repository property with the name github-codeql-file-coverage-on-prs and the type "True/false", then set this property to true in the repository's settings. For more information, see Managing custom properties for repositories in your organization. Alternatively, if you are using an advanced setup workflow, you can set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.
    • User-owned repositories using default setup: Switch to an advanced setup workflow and set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.
    • User-owned repositories using advanced setup: Set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.
  • Fixed a bug which caused the CodeQL Action to fail loading repository properties if a "Multi select" repository property was configured for the repository. #3557

  • The CodeQL Action now loads custom repository properties on GitHub Enterprise Server, enabling the customization of features such as github-codeql-disable-overlay that was previously only available on GitHub.com. #3559

  • Once private package registries can be configured with OIDC-based authentication for organizations, the CodeQL Action will now be able to accept such configurations. #3563

  • Fixed the retry mechanism for database uploads. Previously this would fail with the error "Response body object should not be disturbed or locked". #3564

  • A warning is now emitted if the CodeQL Action detects a repository property whose name suggests that it relates to the CodeQL Action, but which is not one of the properties recognised by the current version of the CodeQL Action. #3570

v4.32.6

  • Update default CodeQL bundle version to 2.24.3. #3548

v4.32.5

  • Repositories owned by an organization can now set up the github-codeql-disable-overlay custom repository property to disable improved incremental analysis for CodeQL. First, create a custom repository property with the name github-codeql-disable-overlay and the type "True/false" in the organization's settings. Then in the repository's settings, set this property to true to disable improved incremental analysis. For more information, see Managing custom properties for repositories in your organization. This feature is not yet available on GitHub Enterprise Server. #3507
  • Added an experimental change so that when improved incremental analysis fails on a runner — potentially due to insufficient disk space — the failure is recorded in the Actions cache so that subsequent runs will automatically skip improved incremental analysis until something changes (e.g. a larger runner is provisioned or a new CodeQL version is released). We expect to roll this change out to everyone in March. #3487
  • The minimum memory check for improved incremental analysis is now skipped for CodeQL 2.24.3 and later, which has reduced peak RAM usage. #3515
  • Reduced log levels for best-effort private package registry connection check failures to reduce noise from workflow annotations. #3516
  • Added an experimental change which lowers the minimum disk space requirement for improved incremental analysis, enabling it to run on standard GitHub Actions runners. We expect to roll this change out to everyone in March. #3498
  • Added an experimental change which allows the start-proxy action to resolve the CodeQL CLI version from feature flags instead of using the linked CLI bundle version. We expect to roll this change out to everyone in March. #3512
  • The previously experimental changes from versions 4.32.3, 4.32.4, 3.32.3 and 3.32.4 are now enabled by default. #3503, #3504

v4.32.4

  • Update default CodeQL bundle version to 2.24.2. #3493
  • Added an experimental change which improves how certificates are generated for the authentication proxy that is used by the CodeQL Action in Default Setup when private package registries are configured. This is expected to generate more widely compatible certificates and should have no impact on analyses which are working correctly already. We expect to roll this change out to everyone in February. #3473
  • When the CodeQL Action is run with debugging enabled in Default Setup and private package registries are configured, the "Setup proxy for registries" step will output additional diagnostic information that can be used for troubleshooting. #3486
  • Added a setting which allows the CodeQL Action to enable network debugging for Java programs. This will help GitHub staff support customers with troubleshooting issues in GitHub-managed CodeQL workflows, such as Default Setup. This setting can only be enabled by GitHub staff. #3485
  • Added a setting which enables GitHub-managed workflows, such as Default Setup, to use a nightly CodeQL CLI release instead of the latest, stable release that is used by default. This will help GitHub staff support customers whose analyses for a given repository or organization require early access to a change in an upcoming CodeQL CLI release. This setting can only be enabled by GitHub staff. #3484

v4.32.3

  • Added experimental support for testing connections to private package registries. This feature is not currently enabled for any analysis. In the future, it may be enabled by default for Default Setup. #3466

... (truncated)

Changelog

Sourced from github/codeql-action's changelog.

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

[UNRELEASED]

  • The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable is deprecated and will be removed in May 2026. If you are affected by this, we recommend disabling TRAP caching by passing the trap-caching: false input to the init Action. #3795
  • The Git version 2.36.0 requirement for improved incremental analysis now only applies to repositories that contain submodules. #3789
  • Python analysis on GHES no longer extracts the standard library, relying instead on models of the standard library. This should result in significantly faster extraction and analysis times, while the effect on alerts should be minimal. #3794
  • Fixed a bug in the validation of OIDC configurations for private registries that was added in CodeQL Action 4.33.0 / 3.33.0. #3807

4.35.1 - 27 Mar 2026

4.35.0 - 27 Mar 2026

4.34.1 - 20 Mar 2026

  • Downgrade default CodeQL bundle version to 2.24.3 due to issues with a small percentage of Actions and JavaScript analyses. #3762

4.34.0 - 20 Mar 2026

  • Added an experimental change which disables TRAP caching when improved incremental analysis is enabled, since improved incremental analysis supersedes TRAP caching. This will improve performance and reduce Actions cache usage. We expect to roll this change out to everyone in March. #3569
  • We are rolling out improved incremental analysis to C/C++ analyses that use build mode none. We expect this rollout to be complete by the end of April 2026. #3584
  • Update default CodeQL bundle version to 2.25.0. #3585

4.33.0 - 16 Mar 2026

  • Upcoming change: Starting April 2026, the CodeQL Action will skip collecting file coverage information on pull requests to improve analysis performance. File coverage information will still be computed on non-PR analyses. Pull request analyses will log a warning about this upcoming change. #3562

    To opt out of this change:

    • Repositories owned by an organization: Create a custom repository property with the name github-codeql-file-coverage-on-prs ...

      Description has been truncated

arcavenai and others added 30 commits March 18, 2026 01:39
Investigates why GitHub labels are not being applied to PRs (never)
and inconsistently to issues (only when envoy is running). Identifies
root causes: PR labeling was never assigned to any agent, envoy has
no startup catch-up for issues missed during downtime. Provides
concrete agent definition changes for merge-queue, envoy, and
supervisor.
docs: label usage gap analysis — research artifact
…72.4)

Based on label usage gap analysis (PR #806). Wire label application into
agent workflows: merge-queue PR labeling (title-prefix inference), envoy
startup catch-up + context exhaustion warning + mutual exclusivity,
supervisor label discipline, and retroactive cleanup.

Agent definition and operational doc changes only — no application code.
docs: plan Epic 72 — Operationalize GitHub Label Usage (4 stories)
… mutual exclusivity (Story 72.2)

- Add startup catch-up scan to envoy rhythm: scan open issues for zero
  labels, apply triage.new + type.* to catch issues created during downtime
- Add Context Exhaustion Risk section matching merge-queue/pr-shepherd format
- Add Label Mutual Exclusivity enforcement subsection with remove-before-add
  protocol for exclusive scopes (type.*, priority.*, triage.*, scope.*, resolution.*)
feat: Story 72.2 — Envoy Label Resilience
Add PR Labeling section to merge-queue.md with rules for inferring
type.*, scope.in-scope, and agent.worker labels from PR metadata.
Update the Labels reference table, Authority table, and
label-authority.md to reflect merge-queue's new labeling capabilities.
…tory 71.1)

Drop Apple Intel (darwin/amd64) build targets from:
- .goreleaser.yml: added darwin/amd64 to ignore list
- justfile: removed amd64 line from build-all recipe
- ci.yml: removed amd64 builds, signing, notarization, app bundles,
  DMG, pkg, artifact uploads, release notes, and Homebrew formula
  Intel branch

Only darwin/arm64 (Apple Silicon) and linux/amd64 remain as targets.
Saves CI runner minutes by eliminating expensive macOS Intel signing.
docs: Story 72.1 — Merge-Queue PR Labeling
docs: governance sync — Stories 72.1, 72.2 Done (Epic 72 2/4)
chore: sync operational data
…on (#813)

* docs: supervisor label discipline & resolution.wontfix label (Story 72.3)

Add label discipline section to supervisor agent definition with
instructions for applying agent.worker, scope.*, and resolution.*
labels during issue lifecycle. Create missing resolution.wontfix
label on GitHub. Update label-authority.md summary table to include
resolution.* in supervisor's Can Set column.

* docs: mark Story 72.3 Done (PR #813)
feat: Story 71.1 — Remove darwin/amd64 from CI build and alpha release pipeline
* docs: retroactive label cleanup — fix mutual exclusivity violations (Story 72.4)

Fixed mutual exclusivity violations on three closed issues:
- #330: removed triage.in-progress (kept triage.complete)
- #296: removed type.bug (kept type.infra)
- #283: removed type.bug (kept type.infra)

All seven originally unlabeled issues were already closed; per dev
notes, retroactive labeling of closed issues was skipped.

Final scan of all issues: zero violations remaining.

* docs: update story 72.4 status with PR number (Story 72.4)
Remove all darwin/amd64 references from the sign-stable job in
release.yml. Since only arm64 remains, loops are eliminated in favor
of direct commands for: download, sign, notarize, pkg build, pkg
notarize, checksums, and re-upload steps.
…tests, and agent definitions (#817)

* docs: remove darwin/amd64 (Intel Mac) references from docs, tests, and agent definitions (Story 71.3)

After Stories 71.1 and 71.2 dropped Intel builds from the build and release
pipelines, remaining references to darwin/amd64 in documentation, test tables,
and agent definitions are now stale. This cleans them up:

- README.md: Remove Intel rows from pkg installer and binary download tables
- docs-site installation page: Remove Intel mention from pre-built binary tab
- Architecture doc: Remove darwin/amd64 from cross-compile target lists
- codesign_test.go: Remove amd64 test case from SignMultipleBinaries
- pkg_builder_test.go: Remove amd64 test case from Build_PerArchitecture
- release-manager.md: Remove darwin-amd64 from cross-compile description

* docs: update Story 71.3 status to Done (PR #817)
arcaven and others added 24 commits March 30, 2026 01:49
feat: Warning threshold engine (Story 76.3)
…plete

docs: governance sync — Epic 76 3/6, Epic 77 COMPLETE
…6.5)

Implement SnapshotRecord type and SnapshotWriter for recording quota usage
snapshots to docs/operations/quota-usage.jsonl. Snapshots contain aggregated
metrics (usage %, per-agent breakdown, tier, peak flag, window timing) — no
raw per-interaction duplication. OTEL metric mapping documented in type comments
for Phase 3 Marvel portability.

Provenance: L3
feat: /stats usage data integration (Story 76.5)
- Story 76.3 (Warning Threshold Engine): Not Started → Done (PR #883)
- Epic 76 progress: 3/6 → 4/6
docs: governance sync — Story 76.3 Done, Epic 76 4/6
Research investigating how to install BMAD as a shared sidecar across
multiple repos. Evaluates 7 techniques (symlinks, overlayfs, git
submodules, --add-dir wrappers, MCP server, user-level commands).

Recommends two-phase approach: Phase 1 copies command stubs to
~/.claude/commands/ for instant global availability; Phase 2 adds
symlinks to shared runtime files for power users with 3+ repos.

Provenance: L3
docs: BMAD sidecar installation architecture research
- SC2015: Replace A && B || C with if/then in test-cron-scripts.sh
- SC2317/SC2329: Suppress false-positive unreachable function warnings
  in test-verify-mcp-bridge.sh (caused by exit in heredocs)
- SC2034: Remove unused variables (QUOTA_SCRIPT, OUTPUT, SESSION,
  YELLOW, recent_work_commands, TOTAL_TOKENS)
- SC2034: Suppress for color vars used in embedded Python (quota-status.sh)
- SC2086: Double-quote variable in date flag (sm-sprint-health.sh)
- SC2001: Suppress for sed backreference (handover-history.sh)
- SC2016: Suppress for intentional literal template tokens (validate-alpha-formula.sh)

All scripts now pass shellcheck cleanly.

Provenance: L3
fix: resolve pre-existing ShellCheck warnings in test scripts
The git-safety.sh hook from Story 73.3 (PR #840) blocked sync operations
(fetch, pull, rebase, merge) universally for ALL Claude agents. This was
over-broad -- persistent agents (merge-queue, pr-shepherd) and the
multiclaude CLI itself need these operations.

Two failure modes:
1. Persistent agents couldn't update PR branches or stay current with main
2. multiclaude CLI couldn't spawn workers (fetch is used internally to
   create worktrees), creating a catch-22 where the system couldn't
   self-heal

Fix: detect worker worktrees via path pattern (~/.multiclaude/wts/) and
only enforce sync restrictions there. Universal protections (unsigned
commits, push to main, Co-Authored-By) remain enforced in all contexts.

Test suite expanded from 38 to 68 cases covering both worker and main
checkout contexts with explicit edge cases for context detection.

Provenance: L3
- SC2016: disable for intentional literal ${VAR} patterns in validate-alpha-formula.sh
- SC2034: disable for color vars used in embedded Python (quota-status.sh),
  remove genuinely unused TOTAL_TOKENS and QUOTA_SCRIPT vars
- SC2034: remove unused YELLOW from rollcall.sh, recent_work_commands from shift-clock.sh
- SC2086: quote variable in date expansion (sm-sprint-health.sh)
- SC2069: fix redirect order in test-shift-snapshot.sh
- SC2001: replace sed with shell builtins in handover-history.sh
- SC2329: suppress false positive for indirectly-invoked function (test-verify-mcp-bridge.sh)

Provenance: L3
fix: scope git safety hook to worker worktrees only (Story 73.8)
Layer 1: 35 ADR nodes (34 bedrock + 1 frontier/deferred)
Layer 2: 26 BOARD nodes (18 open questions + 8 research/recommendations)
Layer 3: 4 incident report nodes (bedrock — validated by failure)

65 nodes total, 0 validation warnings. Key early signal:
adr-0026 (self-driving pipeline) contradicted by 3 of 4 incidents.
All incidents share a pattern: assumptions about isolation, atomicity,
or message routing never architecturally enforced.

Layers 4-6 (architecture, PRD, dark factory) pending.
Switch CI from trunk-based (main) to gitflow (develop + main):
- Push trigger: main -> develop for CI, docs, alpha releases
- PR trigger: main -> [develop, main] for CI and scope-check
- Remove stable binary builds from CI (stable releases via tag-triggered release.yml)
- Alpha-only signing: remove installer cert, app bundle, dmg, pkg steps
- Update release-verify to watch develop instead of main for alpha tap
Signed-off-by: StepSecurity Bot <bot@stepsecurity.io>
Bumps the actions group with 10 updates:

| Package | From | To |
| --- | --- | --- |
| [actions/checkout](https://github.com/actions/checkout) | `4.3.1` | `6.0.2` |
| [dorny/paths-filter](https://github.com/dorny/paths-filter) | `3.0.2` | `4.0.1` |
| [actions/github-script](https://github.com/actions/github-script) | `8.0.0` | `9.0.0` |
| [actions/upload-artifact](https://github.com/actions/upload-artifact) | `4.6.2` | `7.0.1` |
| [actions/cache](https://github.com/actions/cache) | `4.3.0` | `5.0.4` |
| [docker/build-push-action](https://github.com/docker/build-push-action) | `7.0.0` | `7.1.0` |
| [github/codeql-action](https://github.com/github/codeql-action) | `3.35.1` | `4.35.1` |
| [actions/setup-python](https://github.com/actions/setup-python) | `5.6.0` | `6.2.0` |
| [goreleaser/goreleaser-action](https://github.com/goreleaser/goreleaser-action) | `9a127d869fb706213d29cdf8eef3a4ea2b869415` | `ec59f474b9834571250b370d4735c50f8e2d1e29` |
| [ossf/scorecard-action](https://github.com/ossf/scorecard-action) | `2.4.0` | `2.4.3` |


Updates `actions/checkout` from 4.3.1 to 6.0.2
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@v4.3.1...de0fac2)

Updates `dorny/paths-filter` from 3.0.2 to 4.0.1
- [Release notes](https://github.com/dorny/paths-filter/releases)
- [Changelog](https://github.com/dorny/paths-filter/blob/master/CHANGELOG.md)
- [Commits](dorny/paths-filter@de90cc6...fbd0ab8)

Updates `actions/github-script` from 8.0.0 to 9.0.0
- [Release notes](https://github.com/actions/github-script/releases)
- [Commits](actions/github-script@ed59741...3a2844b)

Updates `actions/upload-artifact` from 4.6.2 to 7.0.1
- [Release notes](https://github.com/actions/upload-artifact/releases)
- [Commits](actions/upload-artifact@v4.6.2...043fb46)

Updates `actions/cache` from 4.3.0 to 5.0.4
- [Release notes](https://github.com/actions/cache/releases)
- [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md)
- [Commits](actions/cache@v4.3.0...6682284)

Updates `docker/build-push-action` from 7.0.0 to 7.1.0
- [Release notes](https://github.com/docker/build-push-action/releases)
- [Commits](docker/build-push-action@d08e5c3...bcafcac)

Updates `github/codeql-action` from 3.35.1 to 4.35.1
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](github/codeql-action@5c8a8a6...c10b806)

Updates `actions/setup-python` from 5.6.0 to 6.2.0
- [Release notes](https://github.com/actions/setup-python/releases)
- [Commits](actions/setup-python@a26af69...a309ff8)

Updates `goreleaser/goreleaser-action` from 9a127d869fb706213d29cdf8eef3a4ea2b869415 to ec59f474b9834571250b370d4735c50f8e2d1e29
- [Release notes](https://github.com/goreleaser/goreleaser-action/releases)
- [Commits](goreleaser/goreleaser-action@9a127d8...ec59f47)

Updates `ossf/scorecard-action` from 2.4.0 to 2.4.3
- [Release notes](https://github.com/ossf/scorecard-action/releases)
- [Changelog](https://github.com/ossf/scorecard-action/blob/main/RELEASE.md)
- [Commits](ossf/scorecard-action@62b2cac...4eaacf0)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-version: 6.0.2
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: actions
- dependency-name: dorny/paths-filter
  dependency-version: 4.0.1
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: actions
- dependency-name: actions/github-script
  dependency-version: 9.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: actions
- dependency-name: actions/upload-artifact
  dependency-version: 7.0.1
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: actions
- dependency-name: actions/cache
  dependency-version: 5.0.4
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: actions
- dependency-name: docker/build-push-action
  dependency-version: 7.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: actions
- dependency-name: github/codeql-action
  dependency-version: 4.35.1
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: actions
- dependency-name: actions/setup-python
  dependency-version: 6.2.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: actions
- dependency-name: goreleaser/goreleaser-action
  dependency-version: ec59f474b9834571250b370d4735c50f8e2d1e29
  dependency-type: direct:production
  dependency-group: actions
- dependency-name: ossf/scorecard-action
  dependency-version: 2.4.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: actions
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Apr 11, 2026
@dependabot dependabot Bot requested a review from arcaven as a code owner April 11, 2026 04:51
@arcaven arcaven closed this Apr 12, 2026
@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github Apr 12, 2026

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml

@dependabot dependabot Bot deleted the dependabot/github_actions/actions-fc489eec64 branch April 12, 2026 02:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants