Repository navigation
chore(release): prepare v0.6.0 - #433
Merged
Merged
Conversation
The Docker image no longer built: image templates compile in rootfs-init, which the Dockerfile did not copy. Only a tag runs that build, so nothing had noticed. The release binary, built on ubuntu-latest, needed glibc 2.38 and would not start on Ubuntu 22.04 or Debian 12. Build the binary on ubuntu-22.04, and add ci-release so both are tried on a pull request rather than on a tag. Track Cargo.lock, which was ignored, so a release builds what was tested, and build with --locked. Bump the core and SDKs to 0.6.0 and the MCP server to 0.3.0, and turn Unreleased into v0.6.0 with the note that v0.5 does not upgrade in place. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: WaylandYang <145302500+WaylandYang@users.noreply.github.com>
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
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.
Prepares v0.6.0. Nothing here tags or publishes.
Fixed: would have broken the release
node/images.rscompiles inrootfs-init/, and the Dockerfile did not copy it. Reproduced with exactly the files the Dockerfile copies: twocouldn't readerrors, and withrootfs-initadded the check passes.ubuntu-latestit binds__isoc23_sscanf@GLIBC_2.38, so Ubuntu 22.04 and Debian 12 could not run it, and a node runs the master's binary. The 2.39 symbols are weak and do not bind.binariesnow runs onubuntu-22.04.Cargo.lockwas ignored, so a release resolved its dependencies on the day. It is now tracked, and the release and the image build with--locked. This is the lockfile from the build tested below.New
ci-releasebuilds the Docker image and checks the glibc floor on pull requests, becauserelease.ymlotherwise only runs on a tag. This PR is its first run, and that is the real proof of the two fixes above: Docker Hub cannot be reached from the test host, sodocker builditself was not run there.Versions
sandstorm-core,sandstorm-sdk,@deeplethe/sandstormsandstorm-mcpUnreleasedbecomesv0.6.0 - 2026-11-01, with a summary and the note that v0.5 does not upgrade in place. The README Status says v0.6 is current. The date needs changing if the tag lands on another day.Closes #317
#317 on KVM
Bare metal,
--backend firecrackeron XFS,devatce5beff, one tag forked into 4 children at once. 0 failed.layers/<id>/disk/rootfs.ext4, and nothing holds the template's or the tag's image.e2fsck -fnis clean on all 4 disks, checked while no process held them, and on the tag's image.rootfs.ext4hashes the same before and after, and the parent was untouched.🤖 Generated with Claude Code