Repository navigation
0.4.3: openkal 0.25 and the implementations of its family are admitted - #23
Merged
Merged
Conversation
The requirements are ranges over the 0.24 and 0.25 families, so the implementations' own tests, which reach this package through mtest while the package under test stands for itself, resolve. Nothing this library calls changed, and no newer mcpp is stated.
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.
Summary
Requirements become ranges over both families: openkal
>=0.24.0, <0.26.0, openkal-linux>=0.25.0, <0.27.0, openkal-macos>=0.22.0, <0.24.0, openkal-windows>=0.20.0, <0.22.0, openkal-emscripten>=0.13.0, <0.15.0.Why: an openkal implementation that tests itself with mtest reaches this package (mtest -> mcpplibs.os), and this package requires the implementation; with caret requirements on the released family the package under test (a newer minor) could not stand for itself. Ranges keep the 0.24 family building exactly as before.
Why not the capability form (
requires = ["mcpp:kernel-abi=openkal"]with[defaults]per system): it needs mcpp 2026.11.9.1, and a patch that raised the engine floor would stop every consumer on an older mcpp that resolves^0.4. It belongs in a minor release.Test plan
mcpp test(2026.11.9.1) with the released family: 10 passed.