Skip to content

0.4.0 --- follow openkal 0.10 - #10

Merged
Sunrisepeak merged 2 commits into
mainfrom
declarations-0.10
Aug 30, 2026
Merged

0.4.0 --- follow openkal 0.10#10
Sunrisepeak merged 2 commits into
mainfrom
declarations-0.10

Conversation

@Sunrisepeak

Copy link
Copy Markdown
Member

Part of the openkal 0.10 move: mcpplibs/openkal#25.

⚠️ A specification revision moves the whole graph or none of it. openkal is
the shared dependency of every package here and a version requirement is exact —
an implementation left at 0.9.0 while a consumer moves to 0.10.0 does not get its
own older contract; the two are irreconcilable and nothing resolves at all.

Branch declarations-0.10 exists in every implementation so the specification's
own cross-repository job builds against this one.

The commit message states what this package does with each of the five new
declarations and why.

⚠️ A REPIN AND NOTHING ELSE, AND IT IS NOT OPTIONAL.

openkal 0.10 adds five declarations, all of them to interfaces this
implementation does not provide --- so nothing here has anything to implement.

What is not optional is the version. A version requirement in this ecosystem is
EXACT and does not float up, and `openkal' is the shared dependency of every
package in the graph. An implementation left at 0.9.0 while a consumer moves to
0.10.0 does not get its own older contract: the two are irreconcilable and
nothing resolves at all. So a specification revision moves the whole graph or
none of it, and this package is part of the graph.
Same defect as openkal-opensbi and found the same way: the commit is titled
0.4.0, moves the openkal requirement to 0.10.0, and left `version' at 0.3.0.
A release tagged 0.4.0 whose manifest says 0.3.0 is a package that does not
answer to its own name.

Checked every self-version in the chain against what its consumers require.
These two were the only ones that disagreed.
@Sunrisepeak
Sunrisepeak merged commit b89bd56 into main Aug 30, 2026
3 checks passed
@Sunrisepeak
Sunrisepeak deleted the declarations-0.10 branch August 30, 2026 11:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant