Skip to content

ci: mcpp 2026.11.21.1 - #873

Open
Sunrisepeak wants to merge 2 commits into
mainfrom
chore/ci-mcpp-2026.11.21.1
Open

Sunrisepeak wants to merge 2 commits into
mainfrom
chore/ci-mcpp-2026.11.21.1

Conversation

@Sunrisepeak

Copy link
Copy Markdown
Member

The CI pins mcpp 2026.11.21.1, the newest release, in validate.yml, xpkgindex-update.yml, openkal-compat.yml and tests/openkal/pins.toml (openkal-compat checks that the last two agree). Its default platform is openkal-platform 0.31.2; a first run installs gcc 16.2.0, ninja 1.13.2-mcpp.1 and patchelf 0.19.3; it bundles xlings 2026.11.21.1; a cached dependency is served only against the module interfaces it was compiled with. The index's client floor (min_mcpp) is unchanged.

Checked locally with 2026.11.21.1: mcpp xpkg parse of all 343 descriptors; tools/platform_rows.py check (20 rows, each with one platform); the python tests under tests/ and tests/autoupdate; the lua lints; 14 members through tests/run_members.sh (8 mwrap, fmt, zlib, cjson, magic_enum, fmtlib.fmt, cmdline). A full sweep of every member runs on this branch (workflow_dispatch).

The root's [indices] stays as it is. Moving it to [workspace.indices] (mcpp removes the position reading in 2027.1) was measured: the mwrap members pass, but each of the 67 members that names this checkout under another namespace (neargye = { path = "../../.." }) then receives compat at the same directory as well, and xlings refuses the install as ambiguous (package 'mcpplibs:cmdline@0.0.5' is ambiguous, candidates ... from project repo 'compat' ... from project repo 'mcpplibs'). Two names for one checkout are two repositories to the resolver; that is decided in mcpp before the position reading is removed.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant