Historical RC1 Readiness¶

Software Status¶

All software-controlled RC1 work is implemented and validated. No critical bug, TODO, FIXME, stub, or unresolved package vulnerability is known.

Historical External Publication Gates¶

1. Let the Windows/Linux/macOS GitHub Actions matrix pass in the hosted repository.
2. Configure protected GitHub release and npm publication credentials.
3. Approve package-manager submissions and public RC publication.

These gates were satisfied for the stable 1.x publication. Current releases use the signed-tag Automated Release workflow; this file is retained as historical release-candidate evidence.