mcpp.plugins 0.19.0 - #505
Merged
Merged
Conversation
This was referenced Oct 1, 2026
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
2 participants
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.
Registers mcpp-plugins 0.19.0 in the three platform tables, moves
latest, and records what the release changes.v0.19.0cmp)2dd13d81cffd77babdb1070d24659348d2f699c634981f66e3e97206389c5c7ePackage floor: mcpp 2026.10.1.3, which is released and already in xim-pkgindex (openxlings/xim-pkgindex#917).
Every member now answers where the tool it runs comes from in one order, and a choice made in
build.mcppnever asks for the payload: five entries (xim:vcpkg,xim:cmaketwice,xim:appimagetool,xim:bundletool) are installed only when a member asks for them. mcpp-community/mcpp-plugins#41.