Skip to content

Oxiland 0.11.0 release checklist

Status: tip preflight

Tag target: v0.11.0

Release scope

0.11.0 ships demonstrated Redland parity on the frozen matrix: checksummed baseline and obligations, six-cell native two-sided C-oracle differentials, fail-closed release checker, C source corpus, librdf-compat packaging, and revision-bound soak/performance evidence described in the 0.11 report.

Preflight

  • Tip CI and 0.11 Qualification green on main before this readiness commit (CI 30789988269, Qualification 30789988184)
  • Package and lockfile versions match v0.11.0 (python scripts/check-release-version.py v0.11.0)
  • python scripts/check-0.11-release.py (6 profiles, 102 results, 1532 obligations)
  • Rust format, clippy, workspace tests, MSRV, C ABI allowlist, and docs (covered by tip CI)
  • Rust API semver comparison against 0.9.0 as a minor release (covered by tip CI)
  • cargo publish -p oxiland --locked --dry-run
  • Release workflow enforces scripts/check-0.11-release.py for v0.11.* tags

The checked boxes record the tip preflight on 2026-08-03. Confirm CI is green on the commit you tag; the tag-triggered release workflow re-runs full CI and the 0.11 checker before publishing. The reusable CI workflow expands these checks on Linux, macOS, and Windows, builds and install-smokes all Python wheels, and runs security and C ABI jobs.

Publish

After the exact release commit is green on main:

git tag -a v0.11.0 -m "Oxiland 0.11.0"
git push origin v0.11.0

The tag-triggered release workflow verifies the tag/version match, enforces scripts/check-0.11-release.py, 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.11.0.
  • Verify SHA256SUMS against the uploaded wheels, crates, and source archive.
  • Keep tip banners on 0.11.0 until the next development line opens.