Repository navigation
chore: prepare 1.0.1 release - #596
Merged
Merged
Conversation
Sets every published crate, the daemon, the Python package and the npm package to 1.0.1, moves the workspace path requirements with them, and regenerates Cargo.lock, crates/agentd/fuzz/Cargo.lock, docs/schema.json, docs/manifest.json and microvms.pyi. mise run release:prepare 1.0.1 wrote changelog.d/ into CHANGELOG.md as 1.0.1: the one entry is #592, so this release's agentd asset reports 1.0.1 where v1.0.0's reported 0.1.0. ./tools/check-publishable.py --tag=v1.0.1 passes.
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.
What and why
Prepare the 1.0.1 release, so the daemon release asset reports the release number. v1.0.0's
agentdreports0.1.0, and its tag and assets are immutable; SDK 1.0.0 always provisions v1.0.0's asset, so the fix from #593 reaches users as 1.0.1.agentd,bindings/microvms-py/pyproject.tomlandbindings/microvms-js/package.json(withpackage-lock.json) are 1.0.1, and the workspace path requirements move with them.agentd-modeland the other private crates keep their versions.Cargo.lock,crates/agentd/fuzz/Cargo.lock,docs/schema.json(daemon_version1.0.1),docs/manifest.jsonandmicrovms.pyi(__version__).mise run release:prepare 1.0.1wrotechangelog.d/into CHANGELOG.md as[1.0.1] - 2026-10-12. Its one entry is agentd reports version 0.1.0 in the 1.0.0 release #592's fix.Follows #593, which fixed #592.
Evidence
./tools/check-publishable.py --tag=v1.0.1: exit 0, "every published manifest and the daemon's agree with tag v1.0.1".mise run release:prepare 1.0.1: "CHANGELOG.md has 1.0.1 and 1 fragments are removed"; we read the section it wrote.mise run schema,mise run manifestandmise run stubs: each generated file changes only its version value.mise run check: exit 0 in 450 s at fffbc1d (2026-10-12).mise run publish:dry-run: exit 0;cargo publish --workspace --dry-runpackaged and verified all six crates at 1.0.1 and aborted each upload as a dry run.Parity
microvms.pyi,index.d.ts).Guards
None: this adds no guard.
tag_version_skewintools/check-publishable.py, whichrelease:tagruns, holds every version here to the tag.Follow-ups
None.
Platform claims
Scope
(see
docs/STRATEGY.md).