From 0d36c0e3e3d5af19ea1e099358b0300ea0728416 Mon Sep 17 00:00:00 2001 From: Sunrisepeak Date: Sun, 15 Nov 2026 03:15:24 +0900 Subject: [PATCH] CI: mcpp 2026.11.14.1 in every workflow and the openkal pins --- .github/workflows/openkal-compat.yml | 2 +- .github/workflows/validate.yml | 5 ++++- .github/workflows/xpkgindex-update.yml | 2 +- tests/openkal/pins.toml | 2 +- 4 files changed, 7 insertions(+), 4 deletions(-) diff --git a/.github/workflows/openkal-compat.yml b/.github/workflows/openkal-compat.yml index c860ab6a..6caf5088 100644 --- a/.github/workflows/openkal-compat.yml +++ b/.github/workflows/openkal-compat.yml @@ -42,7 +42,7 @@ env: # run if this drifts from pins.toml. See the comment beside `mcpp` in # pins.toml for why this pin, not just validate.yml's, is gated by the # index floor. - MCPP_VERSION: "2026.11.10.1" + MCPP_VERSION: "2026.11.14.1" # CROSS-VALIDATION BEFORE A RELEASE, NOT AFTER IT. # # Empty in an ordinary run, so this measurement keeps using the RELEASED diff --git a/.github/workflows/validate.yml b/.github/workflows/validate.yml index ffab967d..9ad67391 100644 --- a/.github/workflows/validate.yml +++ b/.github/workflows/validate.yml @@ -450,7 +450,10 @@ env: # # 2026.11.7.2: the built-in platform as one release, and the floor # mcpplibs.mtest 0.1.0 states. - MCPP_VERSION: "2026.11.7.2" + # + # 2026.11.14.1: the newest release; the index validates with the engine its + # consumers install (openkal-run 0.6.3 states 2026.11.13.1). + MCPP_VERSION: "2026.11.14.1" jobs: lint: diff --git a/.github/workflows/xpkgindex-update.yml b/.github/workflows/xpkgindex-update.yml index 19868889..5688e4e6 100644 --- a/.github/workflows/xpkgindex-update.yml +++ b/.github/workflows/xpkgindex-update.yml @@ -25,7 +25,7 @@ concurrency: env: PYTHONUTF8: '1' - MCPP_VERSION: '2026.11.13.1' + MCPP_VERSION: '2026.11.14.1' # CROSS-VALIDATION BEFORE A RELEASE: a candidate that needs an mcpp newer # than the pin (its package states the floor) is built with mcpp built from # this branch of mcpp-community/mcpp, as openkal-compat.yml measures with it. diff --git a/tests/openkal/pins.toml b/tests/openkal/pins.toml index 59e2811f..1def820d 100644 --- a/tests/openkal/pins.toml +++ b/tests/openkal/pins.toml @@ -155,7 +155,7 @@ toolchain = "llvm@22.1.8" # openkal-musl 0.16.0 and openkal-llvm-runtime 0.12.0), because a pin that # moves onto an unreachable or divergent asset fails every member at once and # reports it as a compatibility result. -mcpp = "2026.11.10.1" +mcpp = "2026.11.14.1" # The Windows target is named for the C environment the graph presents there, # which is musl's (openkal-musl declares `[c-abi] presents = "posix"`), not