Skip to content

release.verify

Verify a member's latest released wheel against its own tests.

The member's verify phase: the pairing a consumer gets, the wheel the registry serves installed into a plain environment beside the tests at the release tag, imported from site-packages. The nightly point schedules it through [[ci.schedule]]; by hand it answers the same. A red verification fails, and inside CI (or with --report) files or extends the marker issue through the forge first.

fm release.verify <member> [--python=VALUE] [--extras=VALUE] [--report]
Parameter Type Default Description
<member> required the member's directory under packages/
--python=VALUE "" the interpreter version for the plain environment
--extras=VALUE "" extras to install with the wheel, comma-joined
--report flag false file or extend the marker issue on red; the default inside CI

Example

$ fm release.verify <member> --report