Skip to content

M10-05: Establish release artifact verification #64

@DrunkOnJava

Description

@DrunkOnJava

Created from the roadmap audit in TODO.md.

Source: https://github.com/DrunkOnJava/rvt-rs/blob/main/TODO.md#L1144
Tracking commit: 1ec8105

Scope

Labels: priority:P1, type:release, area:ci

  • For each release, verify:
    • crate installs
    • Python wheel installs/imports on Linux/macOS/Windows
    • CLIs run on a sample
    • viewer build artifact loads
    • docs.rs builds
  • Record output in release notes.

Acceptance criteria:

  • Release checklist has exact commands.
  • Failed verification blocks release publication or triggers hotfix.

Definition of done

  • The TODO acceptance criteria for this section are implemented or explicitly superseded by a linked decision.
  • Tests, fixtures, or documentation are added at the level appropriate to the change risk.
  • User-facing behavior and limitations remain honest in README/docs/viewer messaging.
  • Relevant CI checks pass before the issue is closed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:ciWork in the ci area.priority:P1High-impact work needed for the MVP or beta path.type:releaseRelease packaging, provenance, and artifact verification.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions