You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 4bd862d
Browse filesBrowse the repository at this point in the historyBrowse files
bump(mcpp.plugins): 0.6.0 adds the dist-* family and embed table()
0.6.0 introduces a third member family. The prefix states which of three
questions a member answers: `rules-*` how a translation unit is compiled,
`tools-*` what the build program does itself, `dist-*` what comes out of the
link and in what form a user installs it. A `dist-*` member compiles nothing
and does nothing while the build program runs; it consumes link outputs
through a `role = "artifact"` action, reached with `mcpp pack --format <name>`.
Three dist members ship: `dist-appimage` (Linux), `dist-wix` (Windows) and
`dist-apple` (macOS). `mcpp.tools.embed` gains `table()`: N inputs, one
header, one table, each row carrying its input's key alongside the contents.
The floor remains documentation rather than a gate, unchanged. Nothing here
records a per-package engine floor and index-level `min_mcpp` does not move.
What an older client gets is legible at the point of use, and for these three
members it is the best case of that rule: `mcpp::provides_pack_format` does
not exist in an older engine's bundled `mcpp` module, so a consumer that
activates a `dist-*` feature fails at the build.mcpp compile naming the
missing function rather than at a link or, worse, in an artifact.
The descriptor points at the source archive of the tag. The CN asset holds
the identical bytes, verified by download-back, so one sha256 names both
hosts. No package in this index pins `mcpp.plugins`, so moving `latest`
re-pins no consumer.
0 commit comments