Repository navigation
0.23.3: propagate the corrected Linux confinement graph - #16
Merged
Merged
Conversation
Co-authored-by: speak-agent <248744407+speak-agent@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Platform 0.23.3 selects the corrected Linux read-only confinement graph for both ok images and the hosted arrangement. Linux 0.24.1 requires Landlock ABI 3 before reporting confinement support, so truncation is constrained for a read-only grant. Its ABI probe cache uses atomic accesses. All four image packages are 0.4.3 so the native runner includes the corrected backend too. Compiler and image behavior otherwise follow platform 0.23.2.
The group pins Linux 0.24.1, musl 0.27.3, llvm-runtime 0.18.4 and image 0.4.3. All prerequisites have completed producer CI, immutable source releases, byte-verified GitCode mirrors and public-index publication. The runtime passes all ten producer jobs. The platform's package manifest, image/hosted layers, carrier, tools and version table all agree on these exact releases. mcpp remains required at 2026.11.3.1 for std-module compile flags.
Bootstrap order follows the existing exception in mcpp-community/mcpp#885:
CI uses the existing temporary MCPP_SOURCE_REF=release/2026.11.2.3, whose product version is 2026.11.3.1, until that engine is installable. Earlier tags, archives and index entries remain unchanged. Full final consumer qualification and native tool binary publication remain separate gates.
The prerequisite runtime index is now verified at public commit
24b40f77443511401916368eac0a07aa903af317: both archive downloads have SHA2569c63d881e48860a46ffb2df2cfdeebe871bd6b8c8e0bf4b009c40409ba89ebc6(664,148 bytes), and all three runtime 0.18.4 source entries have the expected digest. After a real index refresh, localmcpp test -vpasses with this platform source and the public released dependencies: one x86_64 image executes, one aarch64 image builds and is explicitly not run on the x86_64 host. No working-tree substitution is used for the dependencies.