chore(deps): bump the github-actions group with 4 updates

[dependabot]

Bumps the github-actions group with 4 updates: taiki-e/install-action, github/codeql-action, github/gh-aw and sigstore/cosign-installer.

Updates taiki-e/install-action from 2.69.7 to 2.70.2

Release notes

Sourced from taiki-e/install-action's releases.

2.70.2

• Update vacuum@latest to 0.25.3.

• Update tombi@latest to 0.9.11.

2.70.1

• Update cargo-insta@latest to 1.47.1.

• Update cargo-binstall@latest to 1.17.9.

• Update tombi@latest to 0.9.10.

2.70.0

• Install uv, uvw (Windows-only), and uvx binaries when installing uv. Previously, only uv binary was installed. (#1632)

2.69.14

• Update just@latest to 1.48.1.

• Update wasm-bindgen@latest to 0.2.115.

2.69.13

• Update mise@latest to 2026.3.17.

• Update cargo-insta@latest to 1.47.0.

2.69.12

• Update uv@latest to 0.11.2.

2.69.11

• Update dprint@latest to 0.53.1.

• Update mise@latest to 2026.3.16.

2.69.10

• Update biome@latest to 2.4.9.

• Update mise@latest to 2026.3.15.

2.69.9

• Update uv@latest to 0.11.1.

• Update osv-scanner@latest to 2.3.5.

• Update mise@latest to 2026.3.14.

2.69.8

• Update just@latest to 1.48.0.

• Update uv@latest to 0.11.0.

... (truncated)

Changelog

Sourced from taiki-e/install-action's changelog.

Changelog

All notable changes to this project will be documented in this file.

This project adheres to Semantic Versioning.

[Unreleased]

[2.70.2] - 2026-03-30

• Update vacuum@latest to 0.25.3.

• Update tombi@latest to 0.9.11.

[2.70.1] - 2026-03-29

• Update cargo-insta@latest to 1.47.1.

• Update cargo-binstall@latest to 1.17.9.

• Update tombi@latest to 0.9.10.

[2.70.0] - 2026-03-28

• Install uv, uvw (Windows-only), and uvx binaries when installing uv. Previously, only uv binary was installed. (#1632)

[2.69.14] - 2026-03-28

• Update just@latest to 1.48.1.

• Update wasm-bindgen@latest to 0.2.115.

[2.69.13] - 2026-03-27

• Update mise@latest to 2026.3.17.

• Update cargo-insta@latest to 1.47.0.

[2.69.12] - 2026-03-27

• Update uv@latest to 0.11.2.

[2.69.11] - 2026-03-26

• Update dprint@latest to 0.53.1.

... (truncated)

Commits

• e9e8e03 Release 2.70.2
• f225969 Update vacuum@latest to 0.25.3
• 2e8700a Update tombi@latest to 0.9.11
• 41213fb zizmor: Apply more lints
• fd0f63e Release 2.70.1
• 7487d40 Update cargo-insta@latest to 1.47.1
• ea3bdd4 Update cargo-binstall@latest to 1.17.9
• 7d31177 ci: Test ubuntu 26.04 container
• b933e42 Update tombi@latest to 0.9.10
• 3eeb0f9 tools: Update tidy.sh
• Additional commits viewable in compare view

Updates github/codeql-action from 4.34.1 to 4.35.1

Release notes

Sourced from github/codeql-action's releases.

v4.35.1

• Fix incorrect minimum required Git version for improved incremental analysis: it should have been 2.36.0, not 2.11.0. #3781

v4.35.0

• Reduced the minimum Git version required for improved incremental analysis from 2.38.0 to 2.11.0. #3767
• Update default CodeQL bundle version to 2.25.1. #3773

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]

No user facing changes.

4.35.1 - 27 Mar 2026

• Fix incorrect minimum required Git version for improved incremental analysis: it should have been 2.36.0, not 2.11.0. #3781

4.35.0 - 27 Mar 2026

• Reduced the minimum Git version required for improved incremental analysis from 2.38.0 to 2.11.0. #3767
• Update default CodeQL bundle version to 2.25.1. #3773

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

4.32.6 - 05 Mar 2026

• Update default CodeQL bundle version to 2.24.3. #3548

4.32.5 - 02 Mar 2026

• 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

... (truncated)

Commits

• c10b806 Merge pull request #3782 from github/update-v4.35.1-d6d1743b8
• c5ffd06 Update changelog for v4.35.1
• d6d1743 Merge pull request #3781 from github/henrymercer/update-git-minimum-version
• 65d2efa Add changelog note
• 2437b20 Update minimum git version for overlay to 2.36.0
• ea5f719 Merge pull request #3775 from github/dependabot/npm_and_yarn/node-forge-1.4.0
• 45ceeea Merge pull request #3777 from github/mergeback/v4.35.0-to-main-b8bb9f28
• 24448c9 Rebuild
• 7c51060 Update changelog and version after v4.35.0
• b8bb9f2 Merge pull request #3776 from github/update-v4.35.0-0078ad667
• Additional commits viewable in compare view

Updates github/gh-aw from 0.62.5 to 0.65.0

Release notes

Sourced from github/gh-aw's releases.

v0.64.4

🌟 Release Highlights

This release delivers safe-output tooling improvements, sibling import resolution, and enhanced runner flexibility — driven largely by community feedback from @j-srodka.

✨ What's New

• runs-on-slim for compile-stable jobs — Override the runner for compile-stable framework jobs using the new runs-on-slim key, giving you precise control over job execution environments (#23490)
• Compile-time validation of safe-output job ordering — The compiler now validates needs: ordering on custom safe-output jobs at compile time, catching dependency misconfigurations before they reach runtime (#23486)
• DIFC proxy feature flag — The new difc-proxy feature flag gates DIFC proxy emission, enabling opt-in integrity enforcement for supported environments (#23471)

🐛 Bug Fixes & Improvements

• Sibling nested imports resolved correctly — ./file.md imports now resolve relative to the parent file's directory, fixing broken modular workflow imports (#23475)
• Custom tools included in <safe-output-tools> prompt — Custom jobs, scripts, and actions are now surfaced in the <safe-output-tools> prompt block so agents are aware of all available safe-output mechanisms (#23487)
• Repo-memory concurrency scope tightened — Push concurrency keys are now scoped to the actual branch target, eliminating unnecessary serialization across unrelated branches (#23489)
• MCP error message clarity — Docker-unavailable error messages now use correct parameter syntax for MCP compatibility (#23515)

📚 Documentation

• MemoryOps guide streamlined for better readability (#23506)
• Broken anchor link in safe-outputs specification fixed (#23474)

🌍 Community Contributions

@j-srodka

• Generated jobs lack a compile-stable runner override/inheritance mechanism (direct issue)
• Compiled (safe-output-tools) can omit custom safe-output tools/jobs (direct issue)
• Custom safe-output jobs cannot declare needs / ordering relative to generated jobs (direct issue)
• Compiler-generated repo-memory push concurrency is broader than the actual write surface (direct issue)

---

For complete details, see CHANGELOG.

Generated by Release

---

What's Changed

• [docs] Self-healing documentation fixes from issue analysis - 2026-03-29 by @​github-actions[bot] in github/gh-aw#23460
• fix: add Node.js 24 runtime to daily-multi-device-docs-tester by @​Copilot in github/gh-aw#23464
• feat: guard DIFC proxy emission with difc-proxy feature flag by @​Copilot in github/gh-aw#23471

... (truncated)

Changelog

Sourced from github/gh-aw's changelog.

Changelog

All notable changes to this project will be documented in this file.

v0.40.1 - 2026-02-03

Move from githubnext/gh-aw to github/gh-aw

If you were a former user of the githubnext Agentic Workflows you might have to re-register the extension to reflect the new location. As the gh-aw project moved from githubnext to github please delete the old channel and register the new one.

Example:

gh extension list
NAME   REPO              VERSION
gh aw  githubnext/gh-aw  v0.36.0
gh extension upgrade --all
[aw]: already up to date
gh extension remove gh-aw
gh extension install github/gh-aw
✓ Installed extension github/gh-aw
gh extension list
NAME   REPO          VERSION
gh aw  github/gh-aw  v0.40.1

Bug Fixes

Handle 502 Bad Gateway errors in assign_to_agent handler by treating them as success. The cloud gateway may return 502 errors during agent assignment, but the assignment typically succeeds despite the error. The handler now logs 502 errors for troubleshooting but does not fail the workflow.

Add discussion interaction to smoke workflows and serialize the discussion

flag in safe-outputs handler config.

Smoke workflows now select a random discussion and post thematic comments to validate discussion comment functionality. The compiler now emits the "discussion": true flag in GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG when a workflow requests discussion output, and lock files include discussions: write permission where applicable.

Add discussion interaction to smoke workflows; compiler now serializes the discussion flag into the safe-outputs handler config so workflows can post comments to discussions. Lock files include discussions: write where applicable.

Smoke workflows pick a random discussion and post a thematic comment (copilot: playful, claude: comic-book, codex: mystical oracle, opencode: space mission). This is a non-breaking tooling/workflow change.

Add discussion interaction to smoke workflows; deprecate the discussion flag and

... (truncated)

Commits

• 89ae1c2 Fix argument injection in npm/pip/docker package validators (#23374)
• eefc97d Bump MCP gateway default version to v0.2.8 (#23372)
• 4549e7b Fix DIFC proxy GH_HOST mismatch for user-defined setup steps (#23367)
• 531594a Security: exclude all secret-bearing env vars from agent container via AWF --...
• 8f8f67b Apply DIFC integrity filtering to the main agent job (post-activation only) (...
• 0962ba0 fix: propagate assign-to-agent failure to status comment (#23362)
• 89bb63b Add item_type, item_number, and comment_id to aw_context for current item res...
• 4abbaff refactor: semantic function clustering — consolidate, move, rename, and split...
• 06e7339 Apply progressive disclosure to agent failure issues (#23361)
• 21e679c Fix update-discussion API error logging for explicit discussion_number (#23340)
• Additional commits viewable in compare view

Updates sigstore/cosign-installer from 4.1.0 to 4.1.1

Release notes

Sourced from sigstore/cosign-installer's releases.

v4.1.1

What's Changed

• chore: update default cosign-release to v3.0.5 in sigstore/cosign-installer#223

Full Changelog: sigstore/cosign-installer@v4.1.0...v4.1.1

Commits

• cad07c2 chore: update default cosign-release to v3.0.5 (#223)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Labels

The following labels could not be found: dependencies, github-actions. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[github-actions]

Benchmark Results

No benchmarks configured. Add benchmarks to benches/ directory.

Full results available in CI artifacts.