Releases

Release track

• 0.x for beta and pre-stable iterations
• 1.0 for the first stable contract release

Beta release process

1. Run package checks.
2. Verify docs and changelog.
3. Validate the host-app example.
4. Confirm schema version expectations.
5. Publish the tagged release.

Release diagnostics

During release prep verify:

• provider-based panel config resolves before route and runtime boot
• flashboard:make-provider generates a working host provider
• inline Flashboard::configure() still works as a compatibility layer
• route registration still resolves
• JSON payload contains schema_version
• login flow and protected panel routes still behave correctly