Skip to content

chore(provider): release v0.1.5-nddev.102 for the rustup-capable controller - #319

Merged
rldyourmnd merged 1 commit into
mainfrom
chore/provider-102-stamp
Aug 31, 2026
Merged

chore(provider): release v0.1.5-nddev.102 for the rustup-capable controller#319
rldyourmnd merged 1 commit into
mainfrom
chore/provider-102-stamp

Conversation

@rldyourmnd

Copy link
Copy Markdown
Contributor

Controller-only release: #315..#318 changed the golden-image contract (channels, rustup ownership), so the hosts that build and re-smoke those images need a stamped binary that decodes it. Provider source_commit stays 103ef263; binary_sha256 is the reproducible rebuild of that tree with only the version stamp moved (built twice, cmp clean). Example configs follow the manifest.

https://claude.ai/code/session_01LsGid6U5RrQdFvJmvYdGCF

…roller

The controller gained the b19-era manifest fields in #315..#318; a host that
re-smokes or builds those images must run a binary that decodes them, and the
strict journal reader makes an unstamped rebuild indistinguishable from the
packaged .101 -- the exact divergence the derivative manifest exists to
prevent.

Provider bytes are otherwise unchanged: source_commit stays 103ef26, and the
new binary_sha256 is the reproducible build of that same tree with only the
version stamp moved, verified twice locally with cmp before pinning.

Claude-Session: https://claude.ai/code/session_01LsGid6U5RrQdFvJmvYdGCF
@rldyourmnd
rldyourmnd merged commit 218749a into main Aug 31, 2026
10 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