Skip to content

openkal ecosystem: seven releases that resolve through the index - #247

Merged
Sunrisepeak merged 1 commit into
mainfrom
feat/openkal-index-resolved
Aug 23, 2026
Merged

openkal ecosystem: seven releases that resolve through the index#247
Sunrisepeak merged 1 commit into
mainfrom
feat/openkal-index-resolved

Conversation

@Sunrisepeak

@Sunrisepeak Sunrisepeak commented Aug 23, 2026

Copy link
Copy Markdown
Member

Follow-up to #246. Those versions carry the right capabilities and the wrong references: their manifests name a development branch, which is not part of any release.

package version names
openkal-linux 0.5.3 openkal = "0.6.0"
openkal-macos 0.3.3 same
openkal-windows 0.1.3 same
openkal-opensbi 0.1.2 same
openkal-uefi 0.1.2 same
openkal-musl 0.3.3 openkal 0.6.0 + the four platform implementations
openkal-llvm-runtime 0.1.1 openkal-musl = "0.3.3"

Verified on the fetched tarballs before these entries were written: zero occurrences of the branch name in any published manifest, and every CN mirror object byte-identical to its GitHub archive.

The versions published an hour earlier carry the right capabilities and the
wrong references: their manifests name a development branch, which is not part
of any release and breaks the published tarball the moment that branch is
deleted. These seven replace every such reference with a version that exists
here, layer by layer -- the platform implementations name openkal 0.6.0, the C
library names them, and the C++ runtime names the C library.

Verified on the fetched tarballs before these entries were written: zero
occurrences of the branch name in any published manifest, and every CN mirror
object byte-identical to its GitHub archive.

Claude-Session: https://claude.ai/code/session_01Q4ucduLuSsETHYJ1RkGVVD
@Sunrisepeak
Sunrisepeak merged commit b1f7c0f into main Aug 23, 2026
8 checks passed
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