Skip to content

Oxiland 0.3.0 release checklist

Preflight for tagging v0.3.0 (same pattern as 0.2.0-release.md).

Includes post-preflight durability and docs fixes (canonical Fjall keys, serialize flush, SECURITY/evidence alignment) that must ship in 0.3.0 because v0.3.0 has not been tagged yet.

Preflight

  • Cargo.toml version is 0.3.0
  • CHANGELOG.md has a dated 0.3.0 section (2026-07-30) including the durability and docs fixes listed under Fixed
  • docs/reports/0.3.md describes the compatibility claim
  • PARITY.md marks 0.3 complete and points at the 0.3 inventory
  • docs/ROADMAP.md / docs/milestones/0.3.md are complete
  • ADR-009–ADR-012 are accepted
  • Public API snapshot includes owned QueryResults variants and serialize_graph_results_to_writer
  • Examples construct and update run in CI
  • README / getting-started / positioning list 0.3 SPARQL as available
  • SECURITY.md supports 0.3.x
  • LICENSE-APACHE and LICENSE-MIT are present
  • repository / homepage point at eddiethedean/oxiland
  • Working tree clean on the release candidate commit (ed6d9e7)
  • CI on main green for ed6d9e7 (Check + Fjall + MSRV + RDF I/O conformance)
  • cargo publish --dry-run succeeded on 4e21cc9 (included in ed6d9e7)
  • Pushed to main (ed6d9e7)

Tag the current main tip once its CI is green (release workflow re-runs CI on the tag). Do not retag an older preflight commit: it lacks the Fjall canonical-key fix.

Publish

  • Annotated tag v0.3.0 pushed (git tag -a v0.3.0 -m "oxiland 0.3.0")
  • Release workflow completed successfully on the tag

After publish

  • Confirm https://crates.io/crates/oxiland (0.3.0 via Release workflow)
  • Confirm https://docs.rs/oxiland builds for the published crate
  • Create a GitHub Release from the v0.3.0 tag using CHANGELOG.md (optional product packaging; tag + crates.io publish already land via workflow)