⬆️ Bump lukka/get-cmake from 4.2.2 to 4.2.3

[dependabot]

Bumps 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

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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[YongDo-Hyun]

@dependabot recreate

[YongDo-Hyun]

@dependabot recreate

[coveralls]

Pull Request Test Coverage Report for Build 21779092421

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 97.871%

---

Totals
Change from base Build 21778922713:	0.0%
Covered Lines:	6393
Relevant Lines:	6445

---

💛 - Coveralls