ci(deps): bump the actions-minor-patch group with 2 updates

[dependabot]

Bumps the actions-minor-patch group with 2 updates: github/codeql-action and vig-os/commit-action.

Updates github/codeql-action from 4.32.6 to 4.33.0

Release notes

Sourced from github/codeql-action's releases.

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

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

4.32.4 - 20 Feb 2026

• 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

4.32.3 - 13 Feb 2026

• 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

4.32.2 - 05 Feb 2026

... (truncated)

Commits

• b1bff81 Merge pull request #3574 from github/update-v4.32.7-7dd76e6bf
• e682234 Add changelog entry for #3570
• 95be291 Bump minor version
• 59bcb60 Update changelog for v4.32.7
• 7dd76e6 Merge pull request #3572 from github/mbg/pr-checks/eslint
• e3200e3 Merge pull request #3563 from github/mbg/private-registry/oidc
• 4c356c7 Merge pull request #3570 from github/mbg/repo-props/warn-on-unexpected-props
• b4937c1 Only emit one message with accumulated property names
• 136b8ab Remove cache-dependency-path options as well
• a5aba59 Remove package-lock.json that's no longer needed
• Additional commits viewable in compare view

Updates vig-os/commit-action from 0.1.3 to 0.1.5

Release notes

Sourced from vig-os/commit-action's releases.

v0.1.5

Fixed

• Excluded .git metadata paths during FILE_PATHS directory expansion to prevent malformed Git tree paths (issue #15).

v0.1.4

Added

• Added ALLOW_EMPTY environment variable support to allow creating signed empty commits when no file changes are detected
• Added unit test coverage for empty commit behavior in commitViaAPI() and commit-runner flow handling

Changed

• Updated npm dependency overrides to force patched minimatch versions across transitive dependency trees.
• Updated commitViaAPI() to support empty commits by reusing the parent tree SHA when ALLOW_EMPTY=true
• Updated runner behavior to preserve default no-op behavior when no files are detected, unless ALLOW_EMPTY=true
• Updated README usage examples and environment variable documentation for ALLOW_EMPTY
• Replaced process.exit(0) with early return in runner for improved testability

Fixed

• Fixed missing ALLOW_EMPTY in commit-runner environment variable documentation

Security

• Fixed minimatch ReDoS vulnerabilities (CVE-2026-27903 / GHSA-7r86-cg39-jmmj) by pinning safe transitive versions via npm overrides.

Changelog

Sourced from vig-os/commit-action's changelog.

Changelog

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

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

v0.1.5 - 2026-03-13

Fixed

• Excluded .git metadata paths during FILE_PATHS directory expansion to prevent malformed Git tree paths (issue #15).

v0.1.4 - 2026-03-11

Added

• Added ALLOW_EMPTY environment variable support to allow creating signed empty commits when no file changes are detected
• Added unit test coverage for empty commit behavior in commitViaAPI() and commit-runner flow handling

Changed

• Updated npm dependency overrides to force patched minimatch versions across transitive dependency trees.
• Updated commitViaAPI() to support empty commits by reusing the parent tree SHA when ALLOW_EMPTY=true
• Updated runner behavior to preserve default no-op behavior when no files are detected, unless ALLOW_EMPTY=true
• Updated README usage examples and environment variable documentation for ALLOW_EMPTY
• Replaced process.exit(0) with early return in runner for improved testability

Fixed

• Fixed missing ALLOW_EMPTY in commit-runner environment variable documentation

Security

• Fixed minimatch ReDoS vulnerabilities (CVE-2026-27903 / GHSA-7r86-cg39-jmmj) by pinning safe transitive versions via npm overrides.

v0.1.3 - 2026-01-28

Added

• Added TARGET_BRANCH environment variable support to avoid conflicts with GitHub's built-in GITHUB_REF
• Added normalizeBranch() and resolveBranch() exported functions for branch resolution logic
• Added comprehensive test suite for branch normalization and resolution (commit-runner.test.ts)

Changed

• Improved branch resolution logic with explicit priority: TARGET_BRANCH > GITHUB_REF (if different from context) > workflow context
• Refactored branch resolution into testable exported functions

Fixed

... (truncated)

Commits

• c0024cb release: Release 0.1.5
• 3d6eb3a chore: bump action version to 0.1.5
• 0e52494 chore: prepare CHANGELOG for release 0.1.5
• ef2addf fix: exclude .git paths when expanding FILE_PATHS directories
• 873cb5f build(dist): refresh compiled commit-runner test artifacts
• f2baddf docs(readme): clarify direct .git FILE_PATHS entries are ignored
• a93945c test(commit-runner): cover direct .git FILE_PATHS and remove require usage
• 0cc2e65 build(dist): re-bundle artifacts for issue 15 fix
• 7974cb6 docs(changelog): document issue 15 .git exclusion behavior
• 74d2d5f fix(commit-runner): skip .git metadata during FILE_PATHS expansion
• 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

[c-vigo]

Will be implemented by #6