# Release candidate checks
These checks apply to each candidate release.
1. Confirm the intended source commit, version, and a clean working tree.
2. Run unit, integration, doctest, documentation, formatting, Clippy, package,
coverage, and independent interoperability checks. In particular, verify
injected second-install failures and destination races for both CLI overwrite
and library no-clobber pairs. Review the recovery files and support-contract
wording before release.
3. Confirm the supported-platform CI matrix and coverage workflow pass for the
exact source commit. Publish the crate, then verify its recorded source
commit before tagging and creating the matching GitHub release.
For 0.1.1, verify the MSC Nastran plate fixture provenance, upstream BSD
terms, and the pyNastran comparison of IDs, topology, and displacement values.
Run the malformed Exodus header regression and check that measured line coverage
remains above the 90% floor. Review the draft release notes before publishing.