Single source of truth for which Laraversine majors, PHP, Laravel and database versions are supported and until when. Read this before stating a version or end date, or deciding whether a fix belongs on a branch.
php artisan boost:add-skill freepeace13/laraversineSave this content to: .claude/skills/laraversine-support-policy/SKILL.md
# Laraversine support policy
Other skills and agents read this file instead of hardcoding versions. Update it when a major ships or a window changes, and keep the table in `SECURITY.md` in step.
## Policy
The previous major gets bug fixes for 6 months after the next major ships, then security fixes only for a further 6 to 12 months. This is sized for a solo maintainer; promise no more than can be sustained.
## Branches and versions
| Branch | Status | PHP | Laravel | Bug fixes until | Security fixes until |
|---|---|---|---|---|---|
| `main` | Mirrors `2.x` until 3.0 work starts | 8.3+ | 12, 13 | n/a | n/a |
| `2.x` | Current stable | 8.3+ | 12, 13 | 3.0 release + 6 months | 3.0 release + 12 to 18 months |
| `1.x` | Maintenance | 8.2+ | 11, 12 | 2027-04-22 | 2027-10-22 to 2028-04-22 |
2.0.0 shipped on 2026-10-22, which sets the `1.x` dates above. The `2.x` dates stay relative until 3.0 ships.
Supported databases on every branch: MySQL, MariaDB, PostgreSQL, SQLite. Exact database versions are an open question; read the CI matrix in `.github/workflows/tests.yml` for what is tested.
The PHP and Laravel columns mirror `composer.json` on each branch. If they disagree, `composer.json` wins; fix this table.
## Using it
- A bug fix goes on the oldest branch that is still in its bug-fix window and has the bug.
- A branch past its bug-fix window takes security fixes only.
- Dropping a PHP, Laravel or database version is a breaking change (`feat!:`) and belongs in a new major.
- Security reports go through GitHub private security advisories (see `SECURITY.md`).Other skills and agents read this file instead of hardcoding versions. Update it when a major ships or a window changes, and keep the table in SECURITY.md in step.
The previous major gets bug fixes for 6 months after the next major ships, then security fixes only for a further 6 to 12 months. This is sized for a solo maintainer; promise no more than can be sustained.
| Branch | Status | PHP | Laravel | Bug fixes until | Security fixes until |
|---|---|---|---|---|---|
main |
Mirrors 2.x until 3.0 work starts |
8.3+ | 12, 13 | n/a | n/a |
2.x |
Current stable | 8.3+ | 12, 13 | 3.0 release + 6 months | 3.0 release + 12 to 18 months |
1.x |
Maintenance | 8.2+ | 11, 12 | 2027-04-22 | 2027-10-22 to 2028-04-22 |
2.0.0 shipped on 2026-10-22, which sets the 1.x dates above. The 2.x dates stay relative until 3.0 ships.
Supported databases on every branch: MySQL, MariaDB, PostgreSQL, SQLite. Exact database versions are an open question; read the CI matrix in .github/workflows/tests.yml for what is tested.
The PHP and Laravel columns mirror composer.json on each branch. If they disagree, composer.json wins; fix this table.
feat!:) and belongs in a new major.SECURITY.md).How can I help you explore Laravel packages today?