Skip to content

Oxiland 0.10.0 release checklist

Status: tip preflight

Tag target: v0.10.0

Release scope

0.10.0 ships the frozen storage contracts, expanded Redland-shaped C preview, and qualification-scaffold tooling described in the 0.10 report. It does not claim full Redland behavioral, source, or binary parity, native faster-than-Redland results, or release-duration fuzzing. Those candidate-bound proofs remain the active 0.11 milestone.

Preflight

  • Tip CI green on the exact release commit
  • Package and lockfile versions match v0.10.0
  • python scripts/check-0.10-release.py
  • Rust format, clippy, workspace tests, no-default-feature tests, and docs
  • Rust API semver comparison against 0.9.0 (196 checks passed)
  • Qualification-tool unit tests, inventories, docs links, and API snapshots
  • cargo publish -p oxiland --locked --dry-run
  • Clean CLI install, version execution, and uninstall from the workspace
  • CPython 3.13 wheel build, clean install, import, typing-file, and version smoke on macOS Apple Silicon

The checked boxes record the local preflight on 2026-07-31. The reusable CI workflow repeats and expands these checks on Linux, macOS, and Windows, builds and install-smokes all 15 Python wheels, runs security and C ABI jobs, and is the final gate before tagging.

Publish

After the exact release commit is green on main:

git tag -a v0.10.0 -m "Oxiland 0.10.0"
git push origin v0.10.0

The tag-triggered release workflow verifies the tag/version match, reuses the full CI gate, publishes oxiland and oxiland-cli to crates.io, publishes the install-smoked wheels to PyPI, and creates checksummed GitHub release assets.

After publish

  • Confirm crates.io, PyPI, docs.rs, and the GitHub release show 0.10.0.
  • Verify SHA256SUMS against the uploaded wheels, crates, and source archive.
  • Update tip banners and install examples from 0.9.0 to the next development line in a post-release commit.