Skip to content

Release Operations

Release operations coordinate verification, compatibility review, tagging, and publishing across programs.

Visual Summary

flowchart LR
    verify[verify candidate commit] --> review[compatibility and docs review]
    review --> tag[tag approved release]
    tag --> publish[publish artifacts]
    publish --> monitor[post-release monitoring]

Release Workflow Rules

  • only tag commits with green required gates
  • include compatibility notes for CLI and DAG changes
  • ensure docs navigation and links are valid before publishing
  • verify post-release health and rollback readiness

Current Publication Policy

  • v0.3.4 publishes bijux-cli to crates.io and bijux-cli to PyPI.
  • bijux-dag-* crates remain internal and are intentionally not published in v0.3.4.
  • DAG publication is deferred to v0.4.0, when CLI and DAG are released together.
  • canonical repository for both programs is https://github.com/bijux/bijux-core.

Preflight Checklist

  • required tests and maintainer verification commands are green
  • compatibility notes are prepared for changed public behavior
  • documentation tree and MkDocs navigation are synchronized
  • release owner and rollback owner are explicitly assigned

Postflight Checklist

  • published artifacts match tagged commit identity
  • docs site builds and serves expected handbook routes
  • no new unresolved failures in release-monitoring workflows

Standard Commands

cargo run -q -p bijux-dev --bin bijux-dev-cli -- quickcheck --format json --no-pretty
cargo run -q -p bijux-dev --bin bijux-dev-cli -- release
make docs-check

Code Anchors

  • crates/bijux-dev/src/commands/cli_release_command.rs
  • crates/bijux-dev/src/suites/release.rs
  • .github/workflows/

Next Reads