Skip to content

Bump the github-actions group across 1 directory with 8 updates - #48842

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/github-actions-f0eee7b69d
Closed

Bump the github-actions group across 1 directory with 8 updates#48842
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/github-actions-f0eee7b69d

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 1, 2026

Copy link
Copy Markdown
Contributor

Bumps the github-actions group with 8 updates in the / directory:

Package From To
actions/checkout 6.0.2 7.0.1
github/gh-aw-actions/setup 0.80.9 0.87.5
actions/github-script 7.1.0 9.0.0
github/gh-aw-actions/setup-cli 0.80.9 0.87.5
actions/cache/restore 5.0.5 6.1.0
actions/cache/save 5.0.5 6.1.0
actions/setup-python 5.6.0 7.0.0
actions/setup-node 6.4.0 7.0.0

Updates actions/checkout from 6.0.2 to 7.0.1

Release notes

Sourced from actions/checkout's releases.

v7.0.1

What's Changed

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

v7.0.0

What's Changed

New Contributors

Full Changelog: actions/checkout@v6.0.3...v7.0.0

v6.1.0

What's Changed

https://github.blog/changelog/2026-06-18-safer-pull_request_target-defaults-for-github-actions-checkout/ for more details about this breaking change

Full Changelog: actions/checkout@v6.0.3...v6.1.0

v6.0.3

What's Changed

New Contributors

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

Changelog

Sourced from actions/checkout's changelog.

Changelog

v7.0.1

v7.0.0

v6.0.3

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

... (truncated)

Commits

Updates github/gh-aw-actions/setup from 0.80.9 to 0.87.5

Release notes

Sourced from github/gh-aw-actions/setup's releases.

v0.87.5

Sync of actions from gh-aw at v0.87.5.

v0.87.4

Sync of actions from gh-aw at v0.87.4.

v0.87.2

Sync of actions from gh-aw at v0.87.2.

v0.87.1

Sync of actions from gh-aw at v0.87.1.

v0.87.0

Sync of actions from gh-aw at v0.87.0.

v0.86.3

Sync of actions from gh-aw at v0.86.3.

v0.86.2

Sync of actions from gh-aw at v0.86.2.

v0.86.1

Sync of actions from gh-aw at v0.86.1.

v0.86.0

Sync of actions from gh-aw at v0.86.0.

v0.85.4

Sync of actions from gh-aw at v0.85.4.

v0.83.2

Sync of actions from gh-aw at v0.83.2.

v0.83.1

Sync of actions from gh-aw at v0.83.1.

v0.83.0

Sync of actions from gh-aw at v0.83.0.

v0.82.15

Sync of actions from gh-aw at v0.82.15.

v0.82.14

Sync of actions from gh-aw at v0.82.14.

v0.82.13

Sync of actions from gh-aw at v0.82.13.

v0.82.12

Sync of actions from gh-aw at v0.82.12.

... (truncated)

Commits

Updates actions/github-script from 7.1.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

v8.0.0

What's Changed

⚠️ Minimum Compatible Runner Version

v2.327.1
Release Notes

Make sure your runner is updated to this version or newer to use this release.

New Contributors

Full Changelog: actions/github-script@v7.1.0...v8.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 github/gh-aw-actions/setup-cli from 0.80.9 to 0.87.5

Release notes

Sourced from github/gh-aw-actions/setup-cli's releases.

v0.87.5

Sync of actions from gh-aw at v0.87.5.

v0.87.4

Sync of actions from gh-aw at v0.87.4.

v0.87.2

Sync of actions from gh-aw at v0.87.2.

v0.87.1

Sync of actions from gh-aw at v0.87.1.

v0.87.0

Sync of actions from gh-aw at v0.87.0.

v0.86.3

Sync of actions from gh-aw at v0.86.3.

v0.86.2

Sync of actions from gh-aw at v0.86.2.

v0.86.1

Sync of actions from gh-aw at v0.86.1.

v0.86.0

Sync of actions from gh-aw at v0.86.0.

v0.85.4

Sync of actions from gh-aw at v0.85.4.

v0.83.2

Sync of actions from gh-aw at v0.83.2.

v0.83.1

Sync of actions from gh-aw at v0.83.1.

v0.83.0

Sync of actions from gh-aw at v0.83.0.

v0.82.15

Sync of actions from gh-aw at v0.82.15.

v0.82.14

Sync of actions from gh-aw at v0.82.14.

v0.82.13

Sync of actions from gh-aw at v0.82.13.

v0.82.12

Sync of actions from gh-aw at v0.82.12.

... (truncated)

Commits

Updates actions/cache/restore from 5.0.5 to 6.1.0

Release notes

Sourced from actions/cache/restore's releases.

v6.1.0

What's Changed

Full Changelog: actions/cache@v6...v6.1.0

v6.0.0

What's Changed

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

v5.1.0

What's Changed

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

Changelog

Sourced from actions/cache/restore'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

6.1.0

6.0.0

  • Updated @actions/cache to ^6.0.1, @actions/core to ^3.0.1, @actions/exec to ^3.0.0, @actions/io to ^3.0.2
  • Migrated to ESM module system
  • Upgraded Jest to v30 and test infrastructure to be ESM compatible

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

... (truncated)

Commits
  • 55cc834 Merge pull request #1768 from jasongin/readonly-cache
  • d8cd72f Bump @​actions/cache to v6.1.0 - handle cache write error due to RO token
  • 2c8a9bd Merge pull request #1760 from actions/samirat/esm_migration_and_package_update
  • e9b91fd Prettier fixes
  • e4884b8 Rebuild dist
  • 10baf01 Fixed licenses
  • e39b386 Fix test mock return order
  • b692820 PR feedback
  • 6074912 Rebuild dist bundles as ESM to match type:module
  • 5a912e8 Fix lint and jest issues
  • Additional commits viewable in compare view

Updates actions/cache/save from 5.0.5 to 6.1.0

Release notes

Sourced from actions/cache/save's releases.

v6.1.0

What's Changed

Full Changelog: actions/cache@v6...v6.1.0

v6.0.0

What's Changed

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

v5.1.0

What's Changed

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

Changelog

Sourced from actions/cache/save'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

6.1.0

6.0.0

  • Updated @actions/cache to ^6.0.1, @actions/core to ^3.0.1, @actions/exec to ^3.0.0, @actions/io to ^3.0.2
  • Migrated to ESM module system
  • Upgraded Jest to v30 and test infrastructure to be ESM compatible

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

... (truncated)

Commits
  • 55cc834 Merge pull request #1768 from jasongin/readonly-cache
  • d8cd72f Bump @​actions/cache to v6.1.0 - handle cache write error due to RO token
  • 2c8a9bd Merge pull request #1760 from actions/samirat/esm_migration_and_package_update
  • e9b91fd Prettier fixes
  • e4884b8 Rebuild dist
  • 10baf01 Fixed licenses
  • e39b386 Fix test mock return order
  • b692820 PR feedback
  • 6074912 Rebuild dist bundles as ESM to match type:module
  • 5a912e8 Fix lint and jest issues
  • Additional commits viewable in compare view

Updates actions/setup-python from 5.6.0 to 7.0.0

Release notes

Sourced from actions/setup-python's releases.

v7.0.0

What's Changed

Enhancements

Bug Fix

Dependency Upgrade

New Contributors

Full Changelog: actions/setup-python@v6...v7.0.0

v6.3.0

What's Changed

Enhancement

Dependency update

Documentation

New Contributors

Full Changelog: actions/setup-python@v6.2.0...v6.3.0

v6.2.0

What's Changed

Dependency Upgrades

... (truncated)

Commits

Updates actions/setup-node from 6.4.0 to 7.0.0

Release notes

Sourced from actions/setup-node's releases.

v7.0.0

What's Changed

Enhancements:

Bug fixes:

Documentation updates:

Dependency update:

New Contributors

Full Changelog: actions/setup-node@v6...v7.0.0

v6.5.0

What's Changed

Full Changelog: actions/setup-node@v6.4.0...v6.5.0

Commits
  • 8207627 Migrate to ESM and upgrade dependencies (#1574)
  • 04be95c Add cache-primary-key and cache-matched-key as outputs (#1577)
  • 7c2c68d docs: Update caching recommendations to mitigate cache poisoning risks (#1567)
  • 6a61c03 Merge pull request #1569 from jasongin/update-actions-cache-5.1.0
  • 30eb73b Resolve high-severity audit issues
  • 4e1a87a Update dist
  • 360237f Strict equality
  • 4f8aac5 Bump @​actions/cache to 5.1.0, log cache write denied
  • f4a67bb Only use mirrorToken in getManifest if it's provided (#1548)
  • 0355742 Remove dummy NODE_AUTH_TOKEN export (#1558)
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Sep 1, 2026
Copilot AI balanced review requested due to automatic review settings September 1, 2026 23:54
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Sep 1, 2026
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 1 pipeline(s).
9 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🟡 Changes recommended

Generated lock-file manifests remain inconsistent with their updated executable action pins.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Updates pinned GitHub Actions across CI and agentic workflows.

Changes:

  • Upgrades checkout, runtime setup, cache, and GitHub Script actions.
  • Updates gh-aw setup actions in maintenance and generated workflows.
  • Retains SHA-pinned dependencies.
File summaries
File Description
.github/workflows/verify-links.yml Updates checkout.
.github/workflows/typespec-python-regenerate.yml Updates checkout, Node, Python, and GitHub Script actions.
.github/workflows/post-apiview.yml Updates checkout.
.github/workflows/pipeline-analysis-next-steps.lock.yml Updates generated agentic workflow dependencies.
.github/workflows/pipeline-analysis-auto-fix.lock.yml Updates generated auto-fix dependencies.
.github/workflows/mgmt-sdk-pr-review.lock.yml Updates gh-aw setup.
.github/workflows/issue-triage.lock.yml Updates generated triage dependencies.
.github/workflows/doc-consistency-check.lock.yml Updates generated documentation-check dependencies.
.github/workflows/dependency-checker.yml Updates checkout and Python setup.
.github/workflows/copilot-setup-steps.yml Updates Copilot environment actions.
.github/workflows/azure-sdk-tools.yml Updates tool-test actions.
.github/workflows/agentics-maintenance.yml Updates agentic maintenance dependencies.
.github/workflows/actionlint.yml Updates checkout.
Review details

Suppressed comments (1)

.github/workflows/typespec-python-regenerate.yml:102

  • This second checkout annotation also still says v6 while the updated SHA is v7.0.1. Update it to match the actual action major.
        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
  • Files reviewed: 13/13 changed files
  • Comments generated: 9
  • Review effort level: Balanced

- name: Setup Scripts
id: setup
uses: github/gh-aw-actions/setup@8c7d04ebf1ece56cd381446125da3e0f6896294a # v0.80.9
uses: github/gh-aw-actions/setup@2a78d04403fdc6907d0f05327cffac9dbad5312d # v0.87.5
- name: Setup Scripts
id: setup
uses: github/gh-aw-actions/setup@8c7d04ebf1ece56cd381446125da3e0f6896294a # v0.80.9
uses: github/gh-aw-actions/setup@2a78d04403fdc6907d0f05327cffac9dbad5312d # v0.87.5
- name: Setup Scripts
id: setup
uses: github/gh-aw-actions/setup@423b3dc04bbf1b1797194a4a75aa5cf5d0d4f5b3 # v0.87.1
uses: github/gh-aw-actions/setup@2a78d04403fdc6907d0f05327cffac9dbad5312d # v0.87.5
- name: Setup Scripts
id: setup
uses: github/gh-aw-actions/setup@8c7d04ebf1ece56cd381446125da3e0f6896294a # v0.80.9
uses: github/gh-aw-actions/setup@2a78d04403fdc6907d0f05327cffac9dbad5312d # v0.87.5
- name: Setup Scripts
id: setup
uses: github/gh-aw-actions/setup@8c7d04ebf1ece56cd381446125da3e0f6896294a # v0.80.9
uses: github/gh-aw-actions/setup@2a78d04403fdc6907d0f05327cffac9dbad5312d # v0.87.5
- name: Checkout azure-sdk-for-python
# SHA corresponds to actions/checkout@v6
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
- name: Setup Node.js
# SHA corresponds to actions/setup-node@v6
uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
- name: Setup Python
# SHA corresponds to actions/setup-python@v5
uses: actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065 # v5.6.0
uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0
- name: Send failure notification
# SHA corresponds to actions/github-script@v7
uses: actions/github-script@f28e40c7f34bde8b3046d885e986cb6290c5673b # v7.1.0
uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
@dependabot dependabot Bot changed the title Bump the github-actions group with 8 updates Bump the github-actions group across 1 directory with 8 updates Sep 2, 2026
Copilot AI review requested due to automatic review settings September 2, 2026 04:01
@dependabot
dependabot Bot force-pushed the dependabot/github_actions/github-actions-f0eee7b69d branch from 6f2ad77 to 43b5861 Compare September 2, 2026 04:01

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🟡 Changes recommended

Moderate version-alignment, generated-lock consistency, and annotation issues remain unresolved.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Review details

Suppressed comments (10)

.github/workflows/doc-consistency-check.lock.yml:99

  • This lock file is generated by gh-aw v0.80.9, but its executable references now differ from the old action SHAs retained in gh-aw-manifest. Besides making dependency metadata inaccurate, gh aw compile will restore the compiler-generated pins. Upgrade gh-aw and regenerate this file rather than patching generated uses lines.
        uses: github/gh-aw-actions/setup@2a78d04403fdc6907d0f05327cffac9dbad5312d # v0.87.5

.github/workflows/issue-triage.lock.yml:108

  • This lock file is generated by gh-aw v0.80.9, but only its executable action references were bumped; the gh-aw-manifest still records the v0.80.9 setup action and prior cache/checkout/setup-node pins. The metadata is therefore stale and recompilation will discard these edits. Upgrade the compiler and regenerate the lock file instead.
        uses: github/gh-aw-actions/setup@2a78d04403fdc6907d0f05327cffac9dbad5312d # v0.87.5

.github/workflows/mgmt-sdk-pr-review.lock.yml:96

  • This generated lock's metadata says compiler v0.87.1 and its manifest still pins the v0.87.1 setup SHA, while the executable jobs now use v0.87.5. That makes the lock internally inconsistent and recompilation will overwrite the manual pin. Upgrade gh-aw to v0.87.5 and regenerate this lock file so metadata and generated jobs remain synchronized.
        uses: github/gh-aw-actions/setup@2a78d04403fdc6907d0f05327cffac9dbad5312d # v0.87.5

.github/workflows/pipeline-analysis-auto-fix.lock.yml:164

  • This lock file is generated by gh-aw v0.80.9, and its gh-aw-manifest still records setup v0.80.9 plus the old cache/setup-node pins. Updating only executable uses lines leaves the lock metadata inconsistent and the next gh aw compile will regenerate these references. Upgrade the gh-aw compiler and regenerate the lock file instead.
        uses: github/gh-aw-actions/setup@2a78d04403fdc6907d0f05327cffac9dbad5312d # v0.87.5

.github/workflows/pipeline-analysis-next-steps.lock.yml:156

  • This lock file is generated by gh-aw v0.80.9, and its gh-aw-manifest still records setup v0.80.9 plus the old cache/checkout/setup-node SHAs. Updating only executable uses lines leaves the lock metadata inconsistent and the next gh aw compile will regenerate these pins. Upgrade the gh-aw compiler and regenerate the lock file instead of editing generated action references directly.
        uses: github/gh-aw-actions/setup@2a78d04403fdc6907d0f05327cffac9dbad5312d # v0.87.5

.github/workflows/typespec-python-regenerate.yml:40

  • The preceding annotation still says this SHA is for checkout v6, but the pin is now v7.0.1. Update the annotation so future SHA audits do not rely on incorrect version information.
        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1

.github/workflows/typespec-python-regenerate.yml:102

  • The checkout pin was upgraded to v7.0.1, but its SHA annotation still identifies v6. Keep the annotation synchronized with the pinned major version.
        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1

.github/workflows/typespec-python-regenerate.yml:431

  • The SHA annotation says github-script v7, but the changed pin is v9.0.0. Synchronize the annotation with the action version.
        uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0

.github/workflows/typespec-python-regenerate.yml:142

  • The SHA annotation still identifies setup-python v5 even though this line now pins v7.0.0. Update it to avoid misleading future maintenance.
        uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0

.github/workflows/typespec-python-regenerate.yml:136

  • The SHA annotation is stale after this upgrade: it identifies setup-node v6 while the pinned action is v7.0.0.
        uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
  • Files reviewed: 13/13 changed files
  • Comments generated: 2
  • Review effort level: Balanced

uses: github/gh-aw-actions/setup-cli@8c7d04ebf1ece56cd381446125da3e0f6896294a # v0.80.9
uses: github/gh-aw-actions/setup-cli@2a78d04403fdc6907d0f05327cffac9dbad5312d # v0.87.5
with:
version: v0.80.9
uses: github/gh-aw-actions/setup-cli@8c7d04ebf1ece56cd381446125da3e0f6896294a # v0.80.9
uses: github/gh-aw-actions/setup-cli@2a78d04403fdc6907d0f05327cffac9dbad5312d # v0.87.5
with:
version: v0.80.9
Bumps the github-actions group with 8 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [actions/checkout](https://github.com/actions/checkout) | `6.0.2` | `7.0.1` |
| [github/gh-aw-actions/setup](https://github.com/github/gh-aw-actions) | `0.80.9` | `0.87.5` |
| [actions/github-script](https://github.com/actions/github-script) | `7.1.0` | `9.0.0` |
| [github/gh-aw-actions/setup-cli](https://github.com/github/gh-aw-actions) | `0.80.9` | `0.87.5` |
| [actions/cache/restore](https://github.com/actions/cache) | `5.0.5` | `6.1.0` |
| [actions/cache/save](https://github.com/actions/cache) | `5.0.5` | `6.1.0` |
| [actions/setup-python](https://github.com/actions/setup-python) | `5.6.0` | `7.0.0` |
| [actions/setup-node](https://github.com/actions/setup-node) | `6.4.0` | `7.0.0` |



Updates `actions/checkout` from 6.0.2 to 7.0.1
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@v6.0.2...3d3c42e)

Updates `github/gh-aw-actions/setup` from 0.80.9 to 0.87.5
- [Release notes](https://github.com/github/gh-aw-actions/releases)
- [Changelog](https://github.com/github/gh-aw-actions/blob/main/CHANGELOG.md)
- [Commits](github/gh-aw-actions@v0.80.9...2a78d04)

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

Updates `github/gh-aw-actions/setup-cli` from 0.80.9 to 0.87.5
- [Release notes](https://github.com/github/gh-aw-actions/releases)
- [Changelog](https://github.com/github/gh-aw-actions/blob/main/CHANGELOG.md)
- [Commits](github/gh-aw-actions@8c7d04e...2a78d04)

Updates `actions/cache/restore` from 5.0.5 to 6.1.0
- [Release notes](https://github.com/actions/cache/releases)
- [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md)
- [Commits](actions/cache@v5.0.5...55cc834)

Updates `actions/cache/save` from 5.0.5 to 6.1.0
- [Release notes](https://github.com/actions/cache/releases)
- [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md)
- [Commits](actions/cache@v5.0.5...55cc834)

Updates `actions/setup-python` from 5.6.0 to 7.0.0
- [Release notes](https://github.com/actions/setup-python/releases)
- [Commits](actions/setup-python@v5.6.0...5fda3b9)

Updates `actions/setup-node` from 6.4.0 to 7.0.0
- [Release notes](https://github.com/actions/setup-node/releases)
- [Commits](actions/setup-node@v6.4.0...8207627)

---
updated-dependencies:
- dependency-name: actions/cache/restore
  dependency-version: 6.1.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: github-actions
- dependency-name: actions/cache/save
  dependency-version: 6.1.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: github-actions
- dependency-name: actions/checkout
  dependency-version: 7.0.1
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: github-actions
- dependency-name: actions/github-script
  dependency-version: 9.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: github-actions
- dependency-name: actions/setup-node
  dependency-version: 7.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: github-actions
- dependency-name: actions/setup-python
  dependency-version: 7.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: github-actions
- dependency-name: github/gh-aw-actions/setup
  dependency-version: 0.87.5
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: github-actions
- dependency-name: github/gh-aw-actions/setup-cli
  dependency-version: 0.87.5
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: github-actions
...

Signed-off-by: dependabot[bot] <support@github.com>
Copilot AI review requested due to automatic review settings September 2, 2026 22:48
@dependabot
dependabot Bot force-pushed the dependabot/github_actions/github-actions-f0eee7b69d branch from 43b5861 to fec2079 Compare September 2, 2026 22:48

Copilot AI commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

One or more custom setup steps configured for this repository failed during this Copilot code review run:

Install azsdk mcp server

Setup steps run before each review. If the review above is missing context, or no review was posted at all, the failing step above may be the cause. See the workflow run for failure details, fix your setup steps configuration, and re-request a review.

Note

You can configure setup steps for Copilot code review separately from Copilot cloud agent with a copilot-code-review.yml file. Read the docs for details.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🟡 Changes recommended

Regenerate generated workflows and manifests, upgrade the gh-aw CLI, and correct stale SHA annotations.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Review details

Suppressed comments (10)

.github/workflows/agentics-maintenance.yml:99

  • This file is marked as generated by gh-aw v0.80.9, and its setup-cli steps still explicitly install v0.80.9, so manually changing the generated action pins leaves the maintenance workflow on the old generator/CLI and the next regeneration can restore the old pins. Upgrade gh-aw and regenerate this workflow instead.
        uses: github/gh-aw-actions/setup@2a78d04403fdc6907d0f05327cffac9dbad5312d # v0.87.5

.github/workflows/doc-consistency-check.lock.yml:99

  • Regenerate this lock file after changing the pins. Its machine-readable gh-aw-manifest still declares the old cache, checkout, setup-node, and gh-aw setup SHAs, while the workflow steps now execute the new SHAs, so tooling consuming the manifest receives an inaccurate dependency set. The file header explicitly marks this file as generated and directs updates through gh aw compile.
        uses: github/gh-aw-actions/setup@2a78d04403fdc6907d0f05327cffac9dbad5312d # v0.87.5

.github/workflows/issue-triage.lock.yml:108

  • Regenerate this lock file after changing the pins. Its machine-readable gh-aw-manifest still declares the old cache, checkout, setup-node, and gh-aw setup SHAs, while the workflow steps now execute the new SHAs, so tooling consuming the manifest receives an inaccurate dependency set. The file header explicitly marks this file as generated and directs updates through gh aw compile.
        uses: github/gh-aw-actions/setup@2a78d04403fdc6907d0f05327cffac9dbad5312d # v0.87.5

.github/workflows/mgmt-sdk-pr-review.lock.yml:96

  • Regenerate this lock file after changing the pin. Its machine-readable gh-aw-manifest still declares the previous gh-aw setup SHA while every setup step now executes the new SHA, so tooling consuming the manifest receives an inaccurate dependency set. The file header explicitly marks this file as generated and directs updates through gh aw compile.
        uses: github/gh-aw-actions/setup@2a78d04403fdc6907d0f05327cffac9dbad5312d # v0.87.5

.github/workflows/pipeline-analysis-auto-fix.lock.yml:164

  • Regenerate this lock file after changing the pins. Its machine-readable gh-aw-manifest still declares the old cache, setup-node, and gh-aw setup SHAs, while the workflow steps now execute the new SHAs, so tooling consuming the manifest receives an inaccurate dependency set. The file header explicitly marks this file as generated and directs updates through gh aw compile.
        uses: github/gh-aw-actions/setup@2a78d04403fdc6907d0f05327cffac9dbad5312d # v0.87.5

.github/workflows/pipeline-analysis-next-steps.lock.yml:156

  • Regenerate this lock file after changing the pins. Its machine-readable gh-aw-manifest still declares the old cache, checkout, setup-node, and gh-aw setup SHAs, while the workflow steps now execute the new SHAs, so tooling consuming the manifest receives an inaccurate dependency set. The file header explicitly marks this file as generated and directs updates through gh aw compile.
        uses: github/gh-aw-actions/setup@2a78d04403fdc6907d0f05327cffac9dbad5312d # v0.87.5

.github/workflows/typespec-python-regenerate.yml:136

  • The SHA annotation still identifies setup-node v6, but this step now pins v7.0.0. Update the annotation with the dependency so it remains trustworthy.
        uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0

.github/workflows/typespec-python-regenerate.yml:142

  • The SHA annotation still identifies setup-python v5, but this step now pins v7.0.0. Update the annotation with the dependency so it remains trustworthy.
        uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0

.github/workflows/typespec-python-regenerate.yml:431

  • The SHA annotation still identifies github-script v7, but this step now pins v9.0.0. Update the annotation with the dependency so it remains trustworthy.
        uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0

.github/workflows/typespec-python-regenerate.yml:40

  • The SHA annotation still identifies checkout v6, but this step now pins v7.0.1. Update the annotation with the dependency so it remains trustworthy.
        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
  • Files reviewed: 13/13 changed files
  • Comments generated: 1
  • Review effort level: Balanced

# "azure-sdk-for-python" causing spec.includes("azure") to match all specs
# in regenerate.ts, which breaks unbranded package name detection
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
@dependabot @github

dependabot Bot commented on behalf of github Sep 3, 2026

Copy link
Copy Markdown
Contributor Author

Looks like these dependencies are updatable in another way, so this is no longer needed.

@dependabot dependabot Bot closed this Sep 3, 2026
@dependabot
dependabot Bot deleted the dependabot/github_actions/github-actions-f0eee7b69d branch September 3, 2026 02:46
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 github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant