openkal-kit 0.1.1, and 0.1.0 withdrawn - #265
Merged
Merged
Conversation
0.1.0 named the specification by path. That was true inside the tarball it was published from and false for a consumer: a project naming openkal-kit alongside any implementation reached openkal two ways --- by path from the kit, by version from the implementation --- and the build refused, correctly, because two routes to one package are two copies of it.⚠️ 0.1.0 IS REMOVED RATHER THAN SUPERSEDED. A range requirement would take the larger version and never see it, but `= 0.1.0` would, and there is no graph in which that version does anything but fail. A version that cannot be used is not a version a consumer should be able to select. 0.1.1 is published from the tag `kit-0.1.1`, not from a version of the specification. The specification did not change, and releasing it to repair a package beside it would have required five implementations to move so that an in-step check could be satisfied about a contract that had not moved. The precedent for a version key that differs from its tag is already here: grpc-plugin 1.83.0 comes from grpc-m's v1.83.0-4. The publisher asserted the archive's own `*/kit/mcpp.toml` before uploading --- that it declares 0.1.1 and names the specification by version --- because a tag placed on the wrong commit produces an archive that downloads, verifies against its hash, and still carries the defect the release exists to remove.
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.
0.1.0 named the specification by path — true inside its tarball, false for a consumer. Any project naming openkal-kit alongside an implementation reached openkal two ways and the build refused, correctly.
= 0.1.0would, and there is no graph in which it does anything but fail.0.1.1 is published from the tag
kit-0.1.1rather than from a version of the specification. The specification did not change; releasing it to repair a package beside it would have required five implementations to move so an in-step check could be satisfied about a contract that had not moved. Precedent for a version key differing from its tag is already here: grpc-plugin 1.83.0 ← grpc-m v1.83.0-4.The publisher asserted the archive's own
*/kit/mcpp.tomlbefore uploading — a tag on the wrong commit yields an archive that downloads, verifies, and still carries the defect.