Publishing HyBIT

Public repository: https://github.com/michioga/hybit

User-facing Rust crate: https://crates.io/crates/hybit

HyBIT 0.8.0 release procedure

HyBIT 0.8.0 publishes the same six Rust crates as 0.7.0. hybit-ffi remains repository-only but its C ABI, C++ wrapper, Fortran module, and OpenMP/Rayon thread-interoperability path are release-qualified.

The 0.8 release candidate must pass:

source integrity;
exact 0.8.0 workspace/dependency metadata;
formatting and Clippy;
workspace release tests and all targets;
Rust 1.73 MSRV;
C/C++/Fortran ABI/runtime;
OpenMP/Rayon environment/API interoperability;
crates.io package checks and dependency-ordered dry-runs;
the physical L-angle structural regression and prepared reuse;
mdBook build.

After qualifying the exact source commit on develop/0.8.0, move that exact source to main and rerun the complete gate there. Publish crates in dependency order, create immutable tag v0.8.0, and create the GitHub Release from RELEASE_NOTES_0.8.0.md.

GitHub Pages deploys the frozen 0.8 documentation from main.

Threading integration and oversubscription requirements are documented in THREADING.md.

HyBIT 0.7.0 publication record

HyBIT 0.7.0 was published on 2026-09-27 from the exact validated source commit:

1fdcd6a1b8127c84306c38c3fdbad42563538ad8

The immutable release tag is v0.7.0, and the GitHub Release uses RELEASE_NOTES_0.7.0.md.

The published Rust crates are:

hybit-core
hybit-matrix
hybit-krylov
hybit-precond
hybit-auto
hybit

hybit-ffi remains repository-only and is not published to crates.io. Its C ABI, C++ wrapper, and Fortran ISO_C_BINDING consumer path are built and runtime-tested by the repository release gate.

0.7.0 qualification record

The r32 numerical production line was frozen before release. Later watchdog, local-energy-gate, and filtered spectral-enrichment experiments were excluded from 0.7.0.

The exact release commit passed the complete release-candidate-gate.ps1 on develop/0.7.0, was fast-forwarded to main, and passed the complete gate again on main before publication. In the immutable v0.7.0 tree that script is at repository root; the post-release 0.8 development tree retains the 0.7 qualification scripts under tools/release/0.7/.

The qualifying gate covered:

source-integrity verification, including tracked-file/MANIFEST.txt agreement;
workspace metadata and version checks;
formatting and Clippy with warnings denied;
workspace release tests and all release targets;
Rust 1.73 MSRV;
Rust/C ABI plus C, C++, and Fortran build/runtime checks;
package inspection and crates.io dry-run validation;
the real L-angle structural regression;
independently verified residual, iteration guard, and prepared solve-many reuse.

The release-reference L-angle solve converged in 220 iterations with independently verified relative residual 9.378557e-9. Prepared reuse also passed.

Immutable release rule

Published crate versions and release tags are immutable.

Do not move v0.7.0 to a later documentation or development commit. A serious defect in 0.7.0 must be corrected with a new version such as 0.7.1 or a later release, not by rewriting the existing tag or crates.io artifacts.

Post-release documentation commits may advance main; they do not alter the 0.7.0 release source.

crates.io authentication

Authenticate locally with a crates.io API token using cargo login. Treat the token as a secret; never commit Cargo credentials or paste tokens into logs.

For GitHub Release automation, GitHub CLI may be authenticated with gh auth login. Authentication tokens and device codes must not be committed or included in release logs.

Dependency order for future workspace releases

HyBIT is a Cargo workspace. Higher-level crates depend on lower-level crates, so publication must preserve this dependency order:

hybit-core
    |
    +--> hybit-matrix
    +--> hybit-krylov
              |
              v
         hybit-precond
              |
              v
          hybit-auto
              |
              v
            hybit

hybit-matrix and hybit-krylov may be published at the same dependency level after hybit-core is visible in the crates.io index.

For each future release:

Freeze the exact numerical source set and exclude unintended experimental/generated artifacts.
Regenerate MANIFEST.txt and SOURCE_SHA256.txt.
Run the complete release-candidate gate without release-qualifying skip switches.
Merge the exact validated commit to main.
Rerun the complete gate on main.
Publish crates in dependency order, confirming each dependency level is visible in crates.io before publishing dependents.
Create an immutable annotated version tag on the exact published source commit.
Create the GitHub Release from the matching release notes.
Perform any post-release documentation synchronization in a later docs-only commit without moving the release tag.

The release gate records performance measurements for regression context, but correctness, residual verification, compatibility, and prepared reuse remain the publication criteria.

Keyboard shortcuts