chore(deps): bump the everything group with 3 updates

[dependabot]

Bumps the everything group with 3 updates: github/codeql-action, KineticCafe/actions-dco and cloudflare/wrangler-action.

Updates github/codeql-action from 4.35.3 to 4.35.4

Release notes

Sourced from github/codeql-action's releases.

v4.35.4

• Update default CodeQL bundle version to 2.25.4. #3881

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]

• 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

4.35.4 - 07 May 2026

• Update default CodeQL bundle version to 2.25.4. #3881

4.35.3 - 01 May 2026

• 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

4.35.2 - 15 Apr 2026

• 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

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

... (truncated)

Commits

• 68bde55 Merge pull request #3885 from github/update-v4.35.4-803d9e8c3
• 9739ad2 Update changelog for v4.35.4
• 803d9e8 Merge pull request #3883 from github/mbg/test/macro-wrapper
• 0fd9c7d Merge pull request #3882 from github/dependabot/github_actions/dot-github/wor...
• 922d6fb Use makeMacro instead of test.macro
• df77e87 Update test macro snippet
• 6e3f985 Add wrapper for test.macro
• e7a347d Merge pull request #3881 from github/update-bundle/codeql-bundle-v2.25.4
• 17eabb2 Rebuild
• aaef09c Bump ruby/setup-ruby
• Additional commits viewable in compare view

Updates KineticCafe/actions-dco from 2.1.1 to 3.0.0

Release notes

Sourced from KineticCafe/actions-dco's releases.

v3.0.0

3.0.0 / 2026-05-09

Version 3 is a full rewrite in Gleam, targeting JavaScript. It should be mostly compatible with previous versions. Malformed commits or sign-off trailers are no longer treated as partial matches, which will result in those commits being rejected where earlier versions may have produced a subtly incorrect validation.

For security purposes, actions-dco is released with immutable releases and tags with no floating version tags. You muse use @v3.0.0 instead of @v3. Pinning to the specific tag reference is strongly recommended.

Deprecations and Stricter Validation

• The exempt-authors input is deprecated, and its use will emit a deprecation warning. Configuration is now provided via an embedded TOML configuration (config).

• Commit identity parsing has been made more strict. The previous version of actions-dco would compose a user and email combination from both the author and the committer if either was missing its name or email fields. Given a case where the commit author only had jane@example.org in her email, and the committer only had John Committer, the action would synthesize an identity John Committer <jane@example.org>.

  This no longer happens.

• Git trailers are strictly parsed. Previous versions would read the signed-off-by trailer from anywhere in the commit message. Now, they must be properly positioned as Git trailers with some flexibility by using trailer-parsing = "lenient".

• Sign-off trailers MUST have both name and email fields.

New Features

• TOML configuration. For the initial version, actions-dco supports inline configuration with the config input. Future versions will support config file references. Eventually, inline config will be deprecated and removed as external configuration is safer.

• Bot policies: Bot committers have been ignored by default since the first version of actions-dco, but this need not be the case any further. Bots may be configured to require explicit signed-off-by trailers (none), only well-known bots (which can be restricted further by bot.categories), or only specific bots are exempted (allowlist with bot.allow).

• Sign-off aliasing. When using the web interface for committing, you may be prompted to use your private Git commit alias, but you might still set signed-off-by to your habitual signature. This allows commit identities to be mapped to a different value for sign-off validation.

• Pull request comments: With comment = true in the configuration (off by default) and pull-requests: write job permission, actions-dco will now maintain a comment on the DCO validation within the PR, increasing the visibility of the sign-off check.

---

What's Changed

• feat: Rewrite from JavaScript to Gleam by @​halostatue in KineticCafe/actions-dco#210
• deps: bump the actions group across 1 directory with 2 updates by @​dependabot[bot] in KineticCafe/actions-dco#211
• chore: Update action.yml for new requirements by @​halostatue in KineticCafe/actions-dco#212

Full Changelog: KineticCafe/actions-dco@v2.1.1...v3.0.0

Changelog

Sourced from KineticCafe/actions-dco's changelog.

KineticCafe/actions-dco Changelog

3.0.0 / 2026-05-09

Version 3 is a full rewrite in Gleam, targeting JavaScript. It should be mostly compatible with previous versions. Malformed commits or sign-off trailers are no longer treated as partial matches, which will result in those commits being rejected where earlier versions may have produced a subtly incorrect validation.

For security purposes, actions-dco is released with immutable releases and tags with no floating version tags. You muse use @v3.0.0 instead of @v3. Pinning to the specific tag reference is strongly recommended.

Deprecations and Stricter Validation

• The exempt-authors input is deprecated, and its use will emit a deprecation warning. Configuration is now provided via an embedded TOML configuration (config).

• Commit identity parsing has been made more strict. The previous version of actions-dco would compose a user and email combination from both the author and the committer if either was missing its name or email fields. Given a case where the commit author only had jane@example.org in her email, and the committer only had John Committer, the action would synthesize an identity John Committer <jane@example.org>.

  This no longer happens.

• Git trailers are strictly parsed. Previous versions would read the signed-off-by trailer from anywhere in the commit message. Now, they must be properly positioned as Git trailers with some flexibility by using trailer-parsing = "lenient".

• Sign-off trailers MUST have both name and email fields.

New Features

• TOML configuration. For the initial version, actions-dco supports inline configuration with the config input. Future versions will support config file references. Eventually, inline config will be deprecated and removed as external configuration is safer.

• Bot policies: Bot committers have been ignored by default since the first version of actions-dco, but this need not be the case any further. Bots may be configured to require explicit signed-off-by trailers (none), only well-known bots (which can be restricted further by bot.categories), or only specific bots are exempted (allowlist with bot.allow).

• Sign-off aliasing. When using the web interface for committing, you may be

... (truncated)

Commits

• f7fe2fd chore: Update action.yml for new requirements
• f947d62 deps: bump the actions group across 1 directory with 2 updates
• 651af3d feat: Rewrite from JavaScript to Gleam
• f398be8 fix: Fix an error in check-dist workflow
• See full diff in compare view

Updates cloudflare/wrangler-action from 3.15.0 to 4.0.0

Release notes

Sourced from cloudflare/wrangler-action's releases.

v4.0.0

Major Changes

• #412 1029e90 Thanks @​ericclemmons! - Update default Wrangler version to v4 (latest). The action now installs Wrangler v4 by default when no wranglerVersion input is specified. Users can still pin to v3 by setting wranglerVersion: "3.90.0" explicitly.

Changelog

Sourced from cloudflare/wrangler-action's changelog.

Changelog

4.0.0

Major Changes

• #412 1029e90 Thanks @​ericclemmons! - Update default Wrangler version to v4 (latest). The action now installs Wrangler v4 by default when no wranglerVersion input is specified. Users can still pin to v3 by setting wranglerVersion: "3.90.0" explicitly.

3.15.0

Minor Changes

• #426 febbda6 Thanks @​WillTaylorDev! - Support version ranges and tags in wranglerVersion input. You can now set wranglerVersion to values like 4, ^4.0.0, 4.x, or latest instead of only exact versions like 4.81.0.

3.14.1

Patch Changes

• #358 cd6314a Thanks @​penalosa! - Use secret bulk instead of deprecated secret:bulk command

3.14.0

Minor Changes

• #351 4ff07f4 Thanks @​Maximo-Guk! - Use wrangler outputs for version upload and wrangler deploy

Patch Changes

• #350 e209094 Thanks @​Maximo-Guk! - Handle failures in createGitHubDeployment and createGitHubJobSummary

3.13.1

Patch Changes

• #345 e819570 Thanks @​Maximo-Guk! - fix: Pages GitHub Deployment not triggering

3.13.0

Minor Changes

• #325 cada7a6 Thanks @​Maximo-Guk! - Add GitHub deployments and job summaries for parity with pages-action

• #334 9fed19a Thanks @​Maximo-Guk! - Bump default wrangler version to 3.90.0

3.12.1

Patch Changes

• #319 59c04629408d58978884fadd18755f1a15f96157 Thanks @​Maximo-Guk! - Fixes #317: Generate a new output directory with a randomUUID in the tmpDir, so that when the action is executed multiple times, we use the artifacts from that run, opposed to the artifacts from a previous run.

... (truncated)

Commits

• ebbaa15 Automatic compilation
• a61fbea Merge pull request #429 from cloudflare/changeset-release/main
• e804ea3 Version Packages
• 8d0324a fix: update release workflow to v5 actions and regenerate lockfile
• 2f18b18 Merge pull request #431 from cloudflare/fix/semgrep-blocking-findings
• 622ff0d fix: upgrade checkout and setup-node to v5 for Node 24 runtime
• f501f05 fix: force GitHub actions to run on Node 24 via env var
• f990691 fix: resolve npm audit vulnerabilities via undici override and vitest v3
• 652762d fix: migrate action runtime from node20 to node24
• bd3f4f0 fix: add retry support to worker health check using better-result
• Additional commits viewable 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