Skip to content

Oxiland 0.5.0 release checklist

Preflight for tagging v0.5.0 (same pattern as 0.4.0-release.md).

Includes post-feature correctness and docs fixes (URI join/relativize, namespace delimiter, World log-level sharing, BOM probe I/O, Fjall create(false) marker heuristic, disk compensation, import I/O mapping, ADR-017 renumber, vocab module split) that must ship in 0.5.0 because v0.5.0 has not been tagged yet.

Preflight

  • Cargo.toml version is 0.5.0
  • CHANGELOG.md has a dated 0.5.0 section (2026-07-30) including the Fixed items for URI/namespace/logging/BOM/storage/docs
  • docs/reports/0.5.md describes the compatibility claim
  • PARITY.md marks 0.5 complete and points at the 0.5 inventory
  • docs/ROADMAP.md / docs/milestones/0.5.md are complete
  • ADR-013–ADR-016 are accepted; Python package ADR is ADR-017 (proposed)
  • Public API snapshot includes utility + logging + utility::vocab::*
  • Example std_replacements runs in CI
  • README / getting-started / utilities / streams docs cover 0.5 surface
  • Format v1 reopen promise covers 0.4.x and 0.5.x (ADR-006)
  • SECURITY.md supports 0.5.x
  • LICENSE-APACHE and LICENSE-MIT are present
  • repository / homepage point at eddiethedean/oxiland
  • Working tree clean on the release candidate tip after push
  • CI on main green (Check + Fjall + MSRV + RDF I/O conformance)
  • cargo publish --dry-run succeeded on e624059 (included in this tip)
  • Pushed to main

Tag the current main tip once its CI is green (release workflow re-runs CI on the tag). Do not tag 0d27c57: it lacks the post-feature deep-dive fixes.

Publish

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

After publish

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