release-checklist.md

Release checklist

Use this checklist for MinerU-ROCm releases. Checked items are required before publishing a release tag; GPU inference is reused only when its formal bundle already passes integrity and provenance validation.

Source and metadata

• Package, import, citation, and changelog versions agree.
• Release branch starts from a clean, synchronized main.
• User-facing claims distinguish community from verified.
• Known gaps retain all intentionally deferred work.

Evidence

• Dataset revision and GT SHA-256 are committed.
• Model cards point to self-contained committed bundles.
• Prediction counts, failures, and fallback policy are recorded.
• Windows DirectML activity and the explicit CPU override are auditable.
• Platform bundle validation and repository conformance pass.

Quality and packaging

• Full CPU test suite passes.
• Ruff, REUSE, repository gates, and pip check pass.
• Wheel and source archive build in an isolated build environment.
• Built wheel metadata reports version 1.0.0 and the expected Python range.
• SHA256SUMS is generated from the final release assets.

Publication

• Changes are reviewed through a green GitHub pull request.
• An annotated v1.0.0 tag targets the merged release commit.
• GitHub Release contains wheel, source archive, checksum file, and release manifest.
• Independent maintainer reproduction completed; badges promoted to verified.