Release guide

Release only with recovery and workflow evidence.

A package is ready when installation, upgrades, critical assessment journeys, security boundaries, private files, screenshots, and documentation have all been verified.

Release ownerMaintainer

Update and recovery flow. A release is verified and backed up before migration; database recovery uses a tested backup rather than reverse migrations.

Package and environment

Verify artifact signature/checksum, version, compatibility, license notices, and public-webroot layout.
Test a fresh protected install and an upgrade from the oldest supported version.
Verify queues, scheduler, mail, storage, PDF generation, canonical URL, proxy policy, and HTTPS.

Assessment smoke

Approve a question, build/publish/assign an exam, and complete a student attempt with autosave/recovery.
Review integrity evidence, mark manual work, moderate, approve, publish, and verify portals.
Generate a document, report, and controlled result export.

Security and recovery

Test tenant, permission, ownership, state, file, URL, webhook, SSO, and update-signature boundaries.
Create and restore the backup in an isolated environment.
Verify failed-migration and failed-provider recovery behavior.

Required commands

php artisan test
php artisan route:list --no-ansi
php artisan view:cache --no-ansi
npm run build
npm run docs:build
npm run docs:verify

Documentation evidence

Every public page, link, anchor, image, caption, diagram, and search entry passes verification.
Screenshots match the current seeded demo and manifest, with no secrets or real personal data.
Feature claims stay within the documented product boundary.