Skip to content

COMP: Bump lukka/get-cmake from 4.4.5 to 4.5.0 - #1301

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/github_actions/lukka/get-cmake-4.5.0
Open

dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/github_actions/lukka/get-cmake-4.5.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 19, 2026

Copy link
Copy Markdown
Contributor

Bumps lukka/get-cmake from 4.4.5 to 4.5.0.

Release notes

Sourced from lukka/get-cmake's releases.

CMake v4.5.0

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.5.0, use this one-liner e.g.: uses: lukka/get-cmake@latest

Enjoy!

CMake v4.5.0-rc3

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:

  • latestrc is now using CMake version v4.5.0-rc3, use e.g.:
- uses: lukka/get-cmake@latest
  with:
    cmakeVersion: latestrc

Enjoy!

CMake v4.5.0-rc2

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:

  • latestrc is now using CMake version v4.5.0-rc2, use e.g.:
- uses: lukka/get-cmake@latest
  with:
    cmakeVersion: latestrc

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 or ninja-vX.Y.Z) - Allow users to pin to specific catalog snapshots

When a new stable CMake, CMake release candidate, or Ninja version is merged to main via automated PR, a release is performed automatically (or can be done manually). Release detection and notes use fixed rules, without an LLM.

Release formats and tag policy

The shared publisher, .github/scripts/publish-release.js, compares these version markers:

Component Version marker Title entry Notes
Stable CMake .latest_cmake_version CMake vX.Y.Z New latest CMake version and one-line action usage
CMake RC .latestrc_cmake_version CMake vX.Y.Z-rcN New latestrc version and usage with cmakeVersion: latestrc
Ninja .latest_ninja_version Ninja vX.Y.Z New Ninja version available through @latest

Combined updates produce one release: title entries are joined with and, and the notes contain a separate entry for each changed component. For example, CMake v3.29.5 and CMake v3.30.0-rc1 follows the historical combined format. RC-only notes follow the historical RC format, rather than claiming the default CMake version changed.

Tag selection is deterministic:

  1. If stable CMake changed, use v<CMake version>.
  2. Otherwise, if Ninja changed, use ninja-v<Ninja version>. This also applies to combined Ninja + RC updates and avoids reusing an unchanged stable CMake tag.
  3. Otherwise, use v<CMake RC version> and mark the release as a GitHub prerelease.

Combined updates containing stable CMake or Ninja are not marked as prereleases. An RC marker that resolves to the stable CMake version is not announced as a separate RC update. Without changed markers or an explicit matching recovery tag, the publisher makes no release, tag, or latest branch changes.

Release titles and tagged catalog versions describe the release target. Usage notes for @latest and cmakeVersion: latestrc use the markers from current main, which is where the moving latest branch is synchronized. When recovering an older catalog, notes distinguish its versions from the versions currently selected by those aliases.

Release Steps

Option 1: Automatic Release (Recommended)

The auto-release.yml workflow automatically handles releases when version markers change on main, including merged automated tool version PRs:

  1. When a push to main changes any of the three version markers
  2. The workflow automatically:
    • Compares all three markers between the push's before and after commits
    • Generates the title, notes, tag, and prerelease status using the rules above
    • Updates the latest branch to match main
    • Creates an annotated version tag at the exact pushed commit (if it doesn't exist)
    • Publishes a GitHub release with the generated title and notes

Detection does not depend on PR titles and covers merge commits, squash merges, multi-commit rebase merges, and direct version updates on main. Using the push's exact commit range prevents a later merge from changing the versions announced by a queued release. The moving latest branch still tracks current main.

... (truncated)

Commits
  • 16e8153 New tool version(s): cmake-v4.5.0
  • 30aea71 New tool version(s): cmake-rc-v4.5.0-rc3
  • b95330f New tool version(s): cmake-rc-v4.5.0-rc2
  • 7d80f02 Bump browserslist from 4.22.1 to 4.28.8
  • 4a9b995 Bump actions/download-artifact from 8.0.1 to 8.0.2
  • See full diff in compare view

Dependabot compatibility score

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 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)

Bumps [lukka/get-cmake](https://github.com/lukka/get-cmake) from 4.4.5 to 4.5.0.
- [Release notes](https://github.com/lukka/get-cmake/releases)
- [Changelog](https://github.com/lukka/get-cmake/blob/main/RELEASE_PROCESS.md)
- [Commits](lukka/get-cmake@f86dd60...16e8153)

---
updated-dependencies:
- dependency-name: lukka/get-cmake
  dependency-version: 4.5.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Nov 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants