Skip to content

Latest commit

 

History

History
17 lines (14 loc) · 848 Bytes

RELEASE.md

File metadata and controls

17 lines (14 loc) · 848 Bytes

Releases

Pushing a vX.Y.Z tag runs .github/workflows/release.yml, which runs the tests, verifies the tag matches pyproject.toml, publishes to PyPI via trusted publishing, then packs, signs, and attaches the .mcpb bundle to the GitHub release alongside the wheel and sdist.

scripts/publish.sh <tag> --dry-run reproduces the build locally without publishing anything.

Bundles are signed with mcpb sign --self-signed. This proves the archive was not modified after signing, but the certificate is generated fresh on each release, so it carries no publisher identity and no continuity between versions. Hosts will warn accordingly. Note also that mcpb verify reports signed bundles as unsigned in CLI 2.1.2 — node-forge does not implement PKCS#7 verification — so the release does not gate on it.