Use this checklist before publishing a RePERS release or handing the package to another repository.
python3 .repers/scripts\repers.py package --output dist --verify-roundtrip --json
python3 .repers/scripts\repers.py release-pack --json
python3 .repers/scripts\repers.py release-pack-verify --archive dist\repers-release-pack.zip --jsonRequired local assets:
dist/repers-0.1.0.zipdist/repers-0.1.0-readiness.jsondist/repers-release-pack.zipdist/repers-release-pack.jsondist/repers-release-pack.mddist/repers-state.jsondist/repers-state.md
python3 .repers/scripts\repers.py verify-all --json
python3 .repers/scripts\repers.py receiver-fixture --json
python3 .repers/scripts\repers.py source-install-fixture --json
python3 .repers/scripts\repers.py publish-clone-fixture --jsonMinimum evidence:
- package readiness reports
ok=true; - release pack verification reports
ok=true; - receiver fixture proves install, doctor, bundle status, capabilities, and deterministic fixture from a fresh target;
- source install fixture proves one-command bootstrap from a checkout;
- publish clone fixture proves clone-side verification from a bare remote.
GitHub Release assets:
repers-0.1.0.ziprepers-release-pack.ziprepers-release-pack.jsonrepers-release-pack.md
Release notes should include:
- one-line value statement;
- install command;
- verification command;
- known limits;
- checksums or a pointer to the release-pack manifest.
Run:
python3 .repers/scripts/repers.py state --jsonThen confirm:
- the public repository has description, topics, and license visible;
- README first screen has install and demo links;
- the release asset can be downloaded and verified;
dist/repers-state.mdreflects current Git remote and branch state.