Skip to content

mcpp:plugins 0.12.0, and CI builds against mcpp 2026.9.16.1 - #433

Merged
Sunrisepeak merged 1 commit into
mainfrom
feat/plugins-0.12.0
Sep 16, 2026
Merged

Sunrisepeak merged 1 commit into
mainfrom
feat/plugins-0.12.0

Conversation

@Sunrisepeak

Copy link
Copy Markdown
Member

mcpp-community/mcpp-plugins v0.12.0 is published, and mcpp 2026.9.16.1 is the release its graph-reading members are written against.

The descriptor

Three platform blocks gain 0.12.0 and latest moves to it. The descriptor points at the source archive of the tag, and the CN asset is the same bytes: both were downloaded and compared with cmp, and 90a70689b090be7208c1f1f35487e148ed353a1bef0cec33d391bd46d67ba13f names each.

What 0.12.0 adds: a package states what it contributes to an application in its own manifest ([package.metadata.dist-apk], [package.metadata.dist-apple]), and the root build program reads those statements from the resolved graph, each package ranked above the packages it depends on and the application above all of them; dist-apk follows the engine's strip decision (MCPP_PACK_STRIP, MCPP_PACK_DEBUG_SYMBOLS_DIR); dist-apple gains options::omit_keys; dist-web gains options::page; rules-swift compiles a package's Swift sources on the Apple rows. Under an older engine there is no graph, the variable is absent, and a package builds without the contribution as before.

The pin

MCPP_VERSION moves 2026.9.15.2 to 2026.9.16.1, with the reason stated beside it. The descriptor is not what moves it -- 0.12.0 degrades on an older engine. What moves it is that 2026.9.16.1 changes how images and runtimes are decided: on ELF every C++ image a plan loads into one process shares one C++ runtime, a static package reached from several shared images is refused where the link or load cannot succeed, and a package whose targets are all programs no longer contributes its dependencies to a consumer's graph. Each decides what a real manifest links, and this index is where they meet five hundred of them.

index.toml min_mcpp does not move: no descriptor grammar changed.

0.12.0 is published (mcpp-community/mcpp-plugins v0.12.0). The descriptor
points at the source archive of the tag, and the GitCode asset is the same
bytes: both were downloaded and compared, and
90a70689b090be7208c1f1f35487e148ed353a1bef0cec33d391bd46d67ba13f names each.

The release: a package states what it contributes to an application in its own
manifest, and the root build program reads those statements from the resolved
graph mcpp 2026.9.16.1 hands it; `dist-apk` follows that engine's strip
decision; `dist-apple` gains `options::omit_keys`, `dist-web` gains
`options::page`, and `rules-swift` compiles a package's Swift sources on the
Apple rows. Under an older engine there is no graph and a package builds
without the contribution, as before.

The CI pin moves with it, for the reason stated beside it: 2026.9.16.1 changes
how images and runtimes are decided, and this index is where that meets five
hundred real manifests. `index.toml` min_mcpp does not move; no descriptor
grammar changed.
@Sunrisepeak
Sunrisepeak merged commit c176883 into main Sep 16, 2026
36 checks passed
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