build(deps): bump the github-actions group across 1 directory with 3 updates

[dependabot]

Bumps the github-actions group with 3 updates in the / directory: actions/cache, lukka/get-cmake and github/codeql-action.

Updates actions/cache from 5.0.2 to 5.0.3

Release notes

Sourced from actions/cache's releases.

v5.0.3

What's Changed

• Bump @actions/cache to v5.0.5 (Resolves: https://github.com/actions/cache/security/dependabot/33)
• Bump @actions/core to v2.0.3

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

Changelog

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

5.0.3

• Bump @actions/cache to v5.0.5 (Resolves: https://github.com/actions/cache/security/dependabot/33)
• Bump @actions/core to v2.0.3

5.0.2

• Bump @actions/cache to v5.0.3 #1692

5.0.1

• Update @azure/storage-blob to ^12.29.1 via @actions/cache@5.0.1 #1685

5.0.0

[!IMPORTANT] actions/cache@v5 runs on the Node.js 24 runtime and requires a minimum Actions Runner version of 2.327.1. If you are using self-hosted runners, ensure they are updated before upgrading.

4.3.0

• Bump @actions/cache to v4.1.0

... (truncated)

Commits

• cdf6c1f Merge pull request #1695 from actions/Link-/prepare-5.0.3
• a1bee22 Add review for the @​actions/http-client license
• 4695763 Add licensed output
• dc73bb9 Upgrade dependencies and address security warnings
• 345d5c2 Add 5.0.3 builds
• See full diff in compare view

Updates lukka/get-cmake from 4.2.2 to 4.2.3

Release notes

Sourced from lukka/get-cmake's releases.

CMake v4.2.3

The get-cmake action downloads and caches CMake and Ninja on your workflows. Versions can be specified using semantic versioning ranges using cmakeVersion and ninjaVersion inputs.

Changes:

• latest is now using CMake version v4.2.3, use this one-liner e.g.: uses: lukka/get-cmake@latest

Enjoy!

Changelog

Sourced from lukka/get-cmake's changelog.

Release Process for get-cmake

This document describes the release process for the get-cmake action after a new CMake or Ninja version has been merged to the main branch.

Overview

The get-cmake action uses two key reference points for users:

1. latest branch - Points to the most recent stable release
2. Version tags (e.g., vX.Y.Z) - Allow users to pin to specific versions

When a new CMake version is detected and merged to main via automated PR, a release is performed automatically (or can be done manually) to make it available to users.

Release Steps

Option 1: Automatic Release (Recommended)

The auto-release.yml workflow automatically handles releases when automated CMake version PRs are merged:

1. When a PR with title matching [Automated] Adding cmake-vX.Y.Z is merged to main
2. The workflow automatically:
   • Reads the version from .latest_cmake_version
   • Updates the latest branch to match main
   • Creates and pushes the version tag (if it doesn't exist)

No manual action needed - the release happens automatically!

Option 2: Manual Release (Override/Fallback)

If you need to manually trigger a release or override the automatic process:

1. Go to the Actions tab in GitHub
2. Select "Sync latest branch and create release tag" workflow
3. Click "Run workflow"
4. Enter the tag name (e.g., v4.2.3)
5. Click "Run workflow" button

The workflow will:

• Validate the tag name format
• Update the latest branch to match main
• Create and push the specified version tag

Option 3: Manual Command-Line Process (Advanced)

If you prefer to do this manually via command line:

# 1. Ensure you're on the main branch and up to date
git checkout main
git pull origin main
</tr></table>

... (truncated)

Commits

• f176ccd Add automated release workflows for latest branch sync and version tagging (#...
• e754285 New CMake version(s): cmake-v4.2.3 (#232)
• 822400b Bump jws from 3.2.2 to 3.2.3 (#222)
• 1bfad7b Bump lodash from 4.17.21 to 4.17.23 (#231)
• See full diff in compare view

Updates github/codeql-action from 4.31.11 to 4.32.0

Release notes

Sourced from github/codeql-action's releases.

v4.32.0

• Update default CodeQL bundle version to 2.24.0. #3425

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.32.0 - 26 Jan 2026

• Update default CodeQL bundle version to 2.24.0. #3425

4.31.11 - 23 Jan 2026

• When running a Default Setup workflow with Actions debugging enabled, the CodeQL Action will now use more unique names when uploading logs from the Dependabot authentication proxy as workflow artifacts. This ensures that the artifact names do not clash between multiple jobs in a build matrix. #3409
• Improved error handling throughout the CodeQL Action. #3415
• Added experimental support for automatically excluding generated files from the analysis. This feature is not currently enabled for any analysis. In the future, it may be enabled by default for some GitHub-managed analyses. #3318
• The changelog extracts that are included with releases of the CodeQL Action are now shorter to avoid duplicated information from appearing in Dependabot PRs. #3403

4.31.10 - 12 Jan 2026

• Update default CodeQL bundle version to 2.23.9. #3393

4.31.9 - 16 Dec 2025

No user facing changes.

4.31.8 - 11 Dec 2025

• Update default CodeQL bundle version to 2.23.8. #3354

4.31.7 - 05 Dec 2025

• Update default CodeQL bundle version to 2.23.7. #3343

4.31.6 - 01 Dec 2025

No user facing changes.

4.31.5 - 24 Nov 2025

• Update default CodeQL bundle version to 2.23.6. #3321

4.31.4 - 18 Nov 2025

No user facing changes.

4.31.3 - 13 Nov 2025

• CodeQL Action v3 will be deprecated in December 2026. The Action now logs a warning for customers who are running v3 but could be running v4. For more information, see Upcoming deprecation of CodeQL Action v3.

... (truncated)

Commits

• b20883b Merge pull request #3428 from github/update-v4.32.0-e3b8227a2
• c9aa45d Update changelog for v4.32.0
• e3b8227 Merge pull request #3427 from github/henrymercer/bump-for-new-minor-series
• 8a01181 Compare minor version number
• 80e1425 Bump minor version for CLI v2.24.0
• b748848 Bump the Action minor version number on new CodeQL minor version series
• 5e767ef Merge pull request #3425 from github/update-bundle/codeql-bundle-v2.24.0
• 9752869 Add changelog note
• c62c214 Update default bundle to codeql-bundle-v2.24.0
• 25a224b Merge pull request #3423 from github/mbg/ci/yq-windows
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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