0.18.0 — follow openkal-macos 0.12.0, so the macOS question has an answer - #40
Merged
Merged
Conversation
…answer openkal-macos 0.12.0 is the first release of that implementation to declare which interfaces of the layer it provides. Until this pin moves, a consumer's `[kernel-abi] requires-interfaces` had no answer at all on macOS --- not a refusal and not a confirmation --- while the same consumer was answered on Linux and Windows, whose implementations have carried the array since openkal-linux 0.15.0 and openkal-windows 0.10.0. That asymmetry is worse than the check not existing: a consumer declaring a requirement reads a green macOS build as the graph having confirmed it. A pin move and nothing else. openkal-macos 0.12.0 changed no source; its array is regenerated from its own objects by its CI and diffed against the manifest, so what this pin brings in is a declaration that has already been checked against the artefact it describes.
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
1 participant
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.
Why this pin moves
openkal-macos 0.12.0 is the first release of that implementation to declare which interfaces of the layer it provides (
[kernel-abi] provides-interfaces, derived from its own objects and diffed against the manifest by its CI).Until this pin moves, a consumer's
requires-interfaceshad no answer at all on macOS — not a refusal, not a confirmation — while the same consumer was answered on Linux and Windows, whose implementations have carried the array since openkal-linux 0.15.0 and openkal-windows 0.10.0.That asymmetry is worse than the check not existing: a consumer that declares a requirement reads a green macOS build as the graph having confirmed it, when nothing looked.
Scope
A pin move and nothing else. openkal-macos 0.12.0 changed no source — the array it adds is regenerated from its own objects and diffed against its manifest on every run, so what this pin brings in is a declaration already checked against the artefact it describes.
CI substitutes the implementation for the host as a working tree (
tools/working-trees.sh), so the macOS job here tests openkal-macosmain.