openkal 0.8.0, and openkal-kit published from its tarball - #261
Merged
Conversation
openkal 0.8 adds five optional interfaces --- terminal, net, datagram, space and timeout --- each admitted against the criterion clause 3 states rather than because it was wanted. The version crosses a minor boundary, so under the leftmost-nonzero caret rule every already-published consumer of `"0.7.0"` resolves `>=0.7.0, <0.8.0` and is unaffected by this entry. openkal-kit is new here. It is the composed half of the specification: facilities that can be written in terms of openkal's atoms, which the specification therefore declines to admit, and which every caller would otherwise write again. It is published out of the specification's own tarball through `mcpp = "*/kit/mcpp.toml"`, as grpc-plugin and grpcgen are published out of grpc-m's, so its version key need not equal the tag: 0.1.0 comes from openkal's 0.8.0 archive and the two entries carry the same hash because they are the same bytes.⚠️ Its manifest reaches the specification by `path = ".."` and its headers by `include_dirs = ["../include"]`. Both escape the package's own directory and hold only if the whole archive is extracted and the manifest then located within it. Measured before publishing rather than after: a consumer naming the kit's directory builds and runs against it, parsing an endpoint and refusing a malformed one. Both assets were fetched back from the CN mirror and compared by hash rather than trusted to the uploader's report, which has said `uploaded` for an object that then answered 404.
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.
openkal 0.8 adds five optional interfaces, each admitted against the criterion clause 3 states. The version crosses a minor boundary, so under the leftmost-nonzero caret rule every already-published consumer of
"0.7.0"resolves>=0.7.0, <0.8.0and is unaffected.openkal-kitis new: the composed half of the specification, published out of the same tarball throughmcpp = "*/kit/mcpp.toml"— the arrangementgrpc-pluginandgrpcgenalready use. Its version key (0.1.0) deliberately differs from the tag (0.8.0); the two entries share one hash because they are the same bytes.Measured before publishing: a consumer naming the kit's directory builds and runs against it, so the
path = ".."andinclude_dirs = ["../include"]that escape the package's own directory do resolve. Both mirrors were fetched back and compared by hash.