Skip to content

deps: Update dependencies for github (major) - #487

Open
renovate-bot wants to merge 1 commit into
GoogleCloudPlatform:mainfrom
renovate-bot:renovate/major-dependencies-for-github
Open

renovate-bot wants to merge 1 commit into
GoogleCloudPlatform:mainfrom
renovate-bot:renovate/major-dependencies-for-github

Conversation

@renovate-bot

@renovate-bot renovate-bot commented Aug 31, 2025 •

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change
actions/checkout action major v5.0.0 → v7.0.1
actions/github-script action major v8 → v9
actions/setup-node action major v4.4.0 → v7.1.0
actions/upload-artifact action major v4.6.2 → v7.0.2
github/codeql-action action major v3.29.9 → v4.39.0
google-github-actions/auth action major v2.1.12 → v3.0.0
google-github-actions/get-secretmanager-secrets action major v2.2.4 → v3.0.0
node uses-with major 22 → 24

Release Notes

actions/checkout

v7.0.1

Compare Source

v7.0.0

Compare Source

  • Block checking out fork PR for pull_request_target and workflow_run by @​aiqiaoy in #​2454
  • Various dependency updates

v6.1.0

Compare Source

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

Compare Source

v6.0.2

Compare Source

v6.0.1

Compare Source

v6.0.0

Compare Source

v5.1.0

Compare Source

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@v5.0.1...v5.1.0

v5.0.1

Compare Source

actions/github-script

v9.0.0

Compare Source

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

actions/setup-node

v7.1.0

Compare Source

What's Changed

Enhancements:
Bug fixes:
Documentation updates:
Dependency updates:

New Contributors

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

v7.0.0

Compare Source

What's Changed
Enhancements:
Bug fixes:
Documentation updates:
Dependency update:
New Contributors

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

v6.5.0

Compare Source

What's Changed

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

v6.4.0

Compare Source

What's Changed
Dependency updates:
New Contributors

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

v6.3.0

Compare Source

What's Changed
Enhancements:

When using node-version-file: package.json, setup-node now prefers devEngines.runtime over engines.node.

Dependency updates:
Bug fixes:
New Contributors

Full Changelog: actions/setup-node@v6...v6.3.0

v6.2.0

Compare Source

What's Changed

Documentation
Dependency updates:

New Contributors

Full Changelog: actions/setup-node@v6...v6.2.0

v6.1.0

Compare Source

What's Changed
Enhancement:
Dependency updates:
Documentation update:

Full Changelog: actions/setup-node@v6...v6.1.0

v6.0.0

Compare Source

What's Changed

Breaking Changes

Dependency Upgrades

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

v5.0.0

Compare Source

What's Changed
Breaking Changes

This update, introduces automatic caching when a valid packageManager field is present in your package.json. This aims to improve workflow performance and make dependency management more seamless.
To disable this automatic caching, set package-manager-cache: false

steps:
- uses: actions/checkout@v5
- uses: actions/setup-node@v5
  with:
    package-manager-cache: false

Make sure your runner is on version v2.327.1 or later to ensure compatibility with this release. See Release Notes

Dependency Upgrades
New Contributors

Full Changelog: actions/setup-node@v4...v5.0.0

actions/upload-artifact

v7.0.2

Compare Source

What's Changed
  • Improves artifact download retries when the service returns HTTP 429 (rate limiting), including honoring valid Retry-After headers.
  • Updates @​actions/artifact to v6.3.1.
New Contributors

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

v7.0.1

Compare Source

What's Changed

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

v7.0.0

Compare Source

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

Compare Source

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

Compare Source

What's Changed

BREAKING CHANGE: this update supports Node v24.x. This is not a breaking change per-se but we're treating it as such.

New Contributors

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

github/codeql-action

v4.39.0

Compare Source

  • Breaking change: Bump the minimum required CodeQL bundle version to 2.20.7. #​4205
  • The codeql-action/analyze step now validates that a correct argument for the checkout_path input has been provided. The checkout_path input must be set to the path where the repository that is being analyzed is checked out at on the runner, if that path is something other than the workspace root. If the path does not point to a repository checkout or is different from the path that was used by codeql-action/init, then the CodeQL Action now produces a warning. #​4148
  • Resolved an issue with third-party caching implementations that prevented caches from being restored correctly. #​4206
  • The codeql-action/start-proxy step that is used in Code Scanning Default Setup now finds CodeQL releases using the same logic as codeql-action/init. This primarily benefits customers who are using GitHub instances other than github.com where the codeql-action/start-proxy step may previously have been unable to locate recent releases and ended up using outdated versions of the private registry authentication proxy as a result. #​4198

v4.38.3

Compare Source

  • Upcoming breaking change: CodeQL version 2.21.2 and earlier were discontinued on 24 September 2026 alongside GitHub Enterprise Server 3.17, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #​4188
  • Update default CodeQL bundle version to 2.27.2. #​4203
  • Fixed a bug where the decision of whether to use a per-language bundle did not account for custom configurations that reference queries outside of compiled CodeQL packs. This issue was caught during internal testing and did not affect any customer repositories. We will resume the roll out of per-language bundles in the coming weeks. #​4184

v4.38.2

Compare Source

v4.38.1

Compare Source

  • The CodeQL Action now has experimental support for CodeQL releases for which per-language bundles are available. Per-language bundles support analysis for a single language and are therefore smaller than the combined bundles that allow analysis for all supported languages. As a result, per-language bundles take up less space on disk and are faster to download. We expect to roll this change out to everyone in the coming weeks. #​4146

v4.38.0

Compare Source

  • On GitHub-hosted runners, the CodeQL Action now deletes unused CodeQL bundles from the toolcache before downloading a different bundle, which frees up disk space for the analysis. We expect to roll this change out to everyone in September. #​4124
  • The CodeQL Action now supports CodeQL releases that are compatible with Linux Arm64 and downloads the native linux-arm64 CodeQL bundle when available. #​4072
  • Update default CodeQL bundle version to 2.27.0. #​4129

v4.37.9

Compare Source

v4.37.8

Compare Source

No user facing changes.

v4.37.7

Compare Source

v4.37.6

Compare Source

  • Changed the default filepath for the new remote file address format that was introduced in CodeQL Action 4.37.0 / 3.37.0 to .github/codeql-config.yml to align it with the suggested path that is used elsewhere. #​4070

v4.37.5

Compare Source

  • Fixed a bug where a network error while streaming the download of the CodeQL bundle could terminate the init Action instead of falling back to downloading the bundle before extracting it. #​4061

v4.37.4

Compare Source

  • This version of the CodeQL Action adds support for the tools input for the codeql-action/init step to be specified using a github-codeql-tools repository property. This feature will gradually be rolled out following the release of this version. Once rolled out, this allows for the CodeQL CLI version that is used in GitHub-managed workflows, such as Default Setup, to be set to a custom value. For example, customers who run into issues with rate limits when a new CodeQL CLI version is released can set the value to toolcache to always use the CodeQL CLI version that is available in the runner toolcache. For Advanced Setup workflows, the value provided for tools in the workflow definition always takes precedence unless the value of the repository property starts with !. #​4037
  • Update default CodeQL bundle version to 2.26.2. #​4051

v4.37.3

Compare Source

No user facing changes.

v4.37.2

Compare Source

  • The new address format for the config-file input that was introduced in CodeQL Action 4.37.0 is now enabled by default. In addition to the format described there, the remote= prefix can now be used to explicitly indicate that the input refers to a remote file. All previous input formats continue to be accepted as well. #​4023
  • The CodeQL Action can now make use of configured private registries in Default Setup to retrieve CodeQL configuration files from remote repositories that require authentication. This will allow customers to store their CodeQL configuration in a single repository that can then be referenced by Default Setup workflows in other repositories. We expect to roll this and other, related changes out to everyone in July. #​4007

v4.37.1

Compare Source

  • Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.20.6 and earlier. These versions of CodeQL were discontinued on 1 July 2026 alongside GitHub Enterprise Server 3.16, and will be unsupported by the next minor release of the CodeQL Action. #​3956
  • Update default CodeQL bundle version to 2.26.1. #​4019

v4.37.0

Compare Source

  • Update default CodeQL bundle version to 2.26.0. #​3995
  • In addition to the existing input format, the config-file input for the codeql-action/init step will soon support a new [owner/]repo[@ref][:path] format. All components except the repository name are optional. If omitted, owner defaults to the same owner as the repository the analysis is running for, ref to main, and path to .github/codeql-action.yaml. Support for this format ships in this version of the CodeQL Action, but will only be enabled over the coming weeks. #​3973

v4.36.3

Compare Source

No user facing changes.

v4.36.2

Compare Source

  • Cache CodeQL CLI version information across Actions steps. #​3943
  • Reduce requests while waiting for analysis processing by using exponential backoff when polling SARIF processing status. #​3937
  • Update default CodeQL bundle version to 2.25.6. #​3948

v4.36.1

Compare Source

No user facing changes.

v4.36.0

Compare Source

  • Breaking change: Bump the minimum required CodeQL bundle version to 2.19.4. #​3894
  • Add support for SHA-256 Git object IDs. #​3893
  • Update default CodeQL bundle version to 2.25.5. #​3926

v4.35.5

Compare Source

  • We have improved how the JavaScript bundles for the CodeQL Action are generated to avoid duplication across bundles and reduce the size of the repository by around 70%. This should have no effect on the runtime behaviour of the CodeQL Action. #​3899
  • For performance and accuracy reasons, improved incremental analysis will now only be enabled on a pull request when diff-informed analysis is also enabled for that run. If diff-informed analysis is unavailable (for example, because the PR diff ranges could not be computed), the action will fall back to a full analysis. #​3791
  • If multiple inputs are provided for the GitHub-internal analysis-kinds input, only code-scanning will be enabled. The analysis-kinds input is experimental, for GitHub-internal use only, and may change without notice at any time. #​3892
  • Added an experimental change which, when running a Code Scanning analysis for a PR with improved incremental analysis enabled, prefers CodeQL CLI versions that have a cached overlay-base database for the configured languages. This speeds up analysis for a repository when there is not yet a cached overlay-base database for the latest CLI version. We expect to roll this change out to everyone in May. #​3880

v4.35.4

Compare Source

v4.35.3

Compare Source

  • Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.19.3 and earlier. These versions of CodeQL were discontinued on 9 April 2026 alongside GitHub Enterprise Server 3.15, and will be unsupported by the next minor release of the CodeQL Action. #​3837
  • Configurations for private registries that use Cloudsmith or GCP OIDC are now accepted. #​3850
  • Best-effort connection tests for private registries now use GET requests instead of HEAD for better compatibility with various registry implementations. For NuGet feeds, the test is now always performed against the service index. #​3853
  • Fixed a bug where two diagnostics produced within the same millisecond could overwrite each other on disk, causing one of them to be lost. #​3852
  • Update default CodeQL bundle version to 2.25.3. #​3865

v4.35.2

Compare Source

  • 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
  • Update default CodeQL bundle version to 2.25.2. #​3823

v4.35.1

Compare Source

v4.35.0

Compare Source

v4.34.1

Compare Source

  • 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

Compare Source

  • 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

Compare Source

  • 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

[!IMPORTANT]
✂ PR body was truncated to here.


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 is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

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

@renovate-bot
renovate-bot requested a review from a team as a code owner August 31, 2025 12:03
@dpebot

dpebot commented Aug 31, 2025

Copy link
Copy Markdown
Collaborator

/gcbrun

@renovate-bot renovate-bot changed the title deps: Update google-github-actions/auth action to v3 deps: Update dependencies for github to v3 (major) Sep 3, 2025
@renovate-bot
renovate-bot force-pushed the renovate/major-dependencies-for-github branch from 5b2acd0 to 773474c Compare September 3, 2025 02:41
@dpebot

dpebot commented Sep 3, 2025

Copy link
Copy Markdown
Collaborator

/gcbrun

@renovate-bot renovate-bot changed the title deps: Update dependencies for github to v3 (major) deps: Update dependencies for github (major) Sep 4, 2025
@renovate-bot
renovate-bot force-pushed the renovate/major-dependencies-for-github branch from 773474c to 9017e24 Compare September 4, 2025 04:49
@dpebot

dpebot commented Sep 4, 2025

Copy link
Copy Markdown
Collaborator

/gcbrun

@renovate-bot
renovate-bot force-pushed the renovate/major-dependencies-for-github branch from 9017e24 to d789779 Compare September 18, 2025 22:04
@dpebot

dpebot commented Sep 18, 2025

Copy link
Copy Markdown
Collaborator

/gcbrun

@renovate-bot
renovate-bot force-pushed the renovate/major-dependencies-for-github branch from d789779 to 90ed24e Compare September 29, 2025 22:29
@dpebot

dpebot commented Sep 29, 2025

Copy link
Copy Markdown
Collaborator

/gcbrun

@renovate-bot
renovate-bot force-pushed the renovate/major-dependencies-for-github branch from 90ed24e to 0951217 Compare October 7, 2025 17:32
@dpebot

dpebot commented Oct 7, 2025

Copy link
Copy Markdown
Collaborator

/gcbrun

@renovate-bot
renovate-bot force-pushed the renovate/major-dependencies-for-github branch from 0951217 to f3449a8 Compare October 8, 2025 23:41
@dpebot

dpebot commented Oct 8, 2025

Copy link
Copy Markdown
Collaborator

/gcbrun

@renovate-bot
renovate-bot force-pushed the renovate/major-dependencies-for-github branch from f3449a8 to 4c90054 Compare October 9, 2025 17:19
@dpebot

dpebot commented Oct 9, 2025

Copy link
Copy Markdown
Collaborator

/gcbrun

@renovate-bot
renovate-bot force-pushed the renovate/major-dependencies-for-github branch from 4c90054 to f619647 Compare October 10, 2025 16:12
@dpebot

dpebot commented Oct 10, 2025

Copy link
Copy Markdown
Collaborator

/gcbrun

@renovate-bot
renovate-bot force-pushed the renovate/major-dependencies-for-github branch from f619647 to cc53736 Compare October 14, 2025 03:13
@dpebot

dpebot commented Oct 14, 2025

Copy link
Copy Markdown
Collaborator

/gcbrun

@renovate-bot
renovate-bot force-pushed the renovate/major-dependencies-for-github branch from cc53736 to 244e5d4 Compare October 17, 2025 15:50
@dpebot

dpebot commented Oct 17, 2025

Copy link
Copy Markdown
Collaborator

/gcbrun

@renovate-bot
renovate-bot force-pushed the renovate/major-dependencies-for-github branch from 244e5d4 to 70a632f Compare October 24, 2025 21:30
@dpebot

dpebot commented Oct 24, 2025

Copy link
Copy Markdown
Collaborator

/gcbrun

@renovate-bot
renovate-bot force-pushed the renovate/major-dependencies-for-github branch from 70a632f to 7d7f5b3 Compare October 28, 2025 04:04
@dpebot

dpebot commented Oct 28, 2025

Copy link
Copy Markdown
Collaborator

/gcbrun

@renovate-bot
renovate-bot force-pushed the renovate/major-dependencies-for-github branch from 7d7f5b3 to 7b340d7 Compare November 5, 2025 01:26
@dpebot

dpebot commented Jul 22, 2026

Copy link
Copy Markdown
Collaborator

/gcbrun

27 similar comments
@dpebot

dpebot commented Jul 24, 2026

Copy link
Copy Markdown
Collaborator

/gcbrun

@dpebot

dpebot commented Jul 30, 2026

Copy link
Copy Markdown
Collaborator

/gcbrun

@dpebot

dpebot commented Aug 3, 2026

Copy link
Copy Markdown
Collaborator

/gcbrun

@dpebot

dpebot commented Aug 4, 2026

Copy link
Copy Markdown
Collaborator

/gcbrun

@dpebot

dpebot commented Aug 11, 2026

Copy link
Copy Markdown
Collaborator

/gcbrun

@dpebot

dpebot commented Aug 12, 2026

Copy link
Copy Markdown
Collaborator

/gcbrun

@dpebot

dpebot commented Aug 13, 2026

Copy link
Copy Markdown
Collaborator

/gcbrun

@dpebot

dpebot commented Aug 13, 2026

Copy link
Copy Markdown
Collaborator

/gcbrun

@dpebot

dpebot commented Aug 18, 2026

Copy link
Copy Markdown
Collaborator

/gcbrun

@dpebot

dpebot commented Aug 21, 2026

Copy link
Copy Markdown
Collaborator

/gcbrun

@dpebot

dpebot commented Aug 26, 2026

Copy link
Copy Markdown
Collaborator

/gcbrun

@dpebot

dpebot commented Aug 31, 2026

Copy link
Copy Markdown
Collaborator

/gcbrun

@dpebot

dpebot commented Sep 2, 2026

Copy link
Copy Markdown
Collaborator

/gcbrun

@dpebot

dpebot commented Sep 2, 2026

Copy link
Copy Markdown
Collaborator

/gcbrun

@dpebot

dpebot commented Sep 2, 2026

Copy link
Copy Markdown
Collaborator

/gcbrun

@dpebot

dpebot commented Sep 2, 2026

Copy link
Copy Markdown
Collaborator

/gcbrun

@dpebot

dpebot commented Sep 9, 2026

Copy link
Copy Markdown
Collaborator

/gcbrun

@dpebot

dpebot commented Sep 18, 2026

Copy link
Copy Markdown
Collaborator

/gcbrun

@dpebot

dpebot commented Sep 24, 2026

Copy link
Copy Markdown
Collaborator

/gcbrun

@dpebot

dpebot commented Sep 25, 2026

Copy link
Copy Markdown
Collaborator

/gcbrun

@dpebot

dpebot commented Oct 2, 2026

Copy link
Copy Markdown
Collaborator

/gcbrun

@dpebot

dpebot commented Oct 7, 2026

Copy link
Copy Markdown
Collaborator

/gcbrun

@dpebot

dpebot commented Oct 8, 2026

Copy link
Copy Markdown
Collaborator

/gcbrun

@dpebot

dpebot commented Oct 8, 2026

Copy link
Copy Markdown
Collaborator

/gcbrun

@dpebot

dpebot commented Oct 8, 2026

Copy link
Copy Markdown
Collaborator

/gcbrun

@dpebot

dpebot commented Oct 8, 2026

Copy link
Copy Markdown
Collaborator

/gcbrun

@dpebot

dpebot commented Oct 12, 2026

Copy link
Copy Markdown
Collaborator

/gcbrun

@dpebot

dpebot commented Oct 15, 2026

Copy link
Copy Markdown
Collaborator

/gcbrun

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants