Use this checklist before tagging and releasing a new stable package.
- Run
php scripts/check-release.php - Confirm all PHP files pass syntax lint
- Confirm route targets resolve to existing controller methods
- Confirm controller views and layouts exist
- Confirm App class imports resolve to real files
- Verify
database/schema.sqlreflects the latest code - Verify
database/seed.sqlstill creates a working admin account - Verify the newest
database/upgrade-v*.sqlfile exists - Confirm upgrade notes mention whether the release changes schema
- Review
MANUAL-TEST-CHECKLIST.md - Test the critical pages after importing current schema + seed
- Check the inquiry list, inquiry detail, sites, tools, logs, reports, follow-up reminders
- Review
API-TEST-EXAMPLES.md - Test
/api/v1/health - Test one valid submission
- Test one invalid token request
- Test one spam-rule-triggered request
- Confirm data and API request logs are written as expected
- Update
VERSION.txt - Update
CHANGELOG.md - Update
README.mdif release or upgrade steps changed - Create the release ZIP
- Tag the release in GitHub
- Record any remaining known issues in the release notes
- Do not claim untested areas are verified