majdghithan/agent-skills / skills/laravel-upgrade
laravel-upgrade
Verified| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.3 KB |
| references/10-to-11.md | markdown | 2.2 KB |
| references/11-to-12.md | markdown | 2.0 KB |
| references/12-to-13.md | markdown | 1.6 KB |
| references/8-to-9.md | markdown | 2.1 KB |
| references/9-to-10.md | markdown | 1.8 KB |
| references/legacy-5-to-7.md | markdown | 1.6 KB |
references/10-to-11.md
View on GitHub# Laravel 10 -> 11
**PHP floor: 8.2.** Bump PHP to 8.2 under Laravel 10 first.
## The myth to kill first
**The slim skeleton (streamlined structure) is OPTIONAL for existing apps.** Laravel 11 ships new installs with a leaner layout, no `app/Http/Kernel.php`, no `app/Console/Kernel.php`, no `app/Exceptions/Handler.php`, middleware and exceptions configured in `bootstrap/app.php`. Upgraded apps keep their existing structure and keep working. You do NOT have to migrate to the new skeleton to be on Laravel 11, and rushing that rewrite during the version bump is how people break things. Upgrade first, adopt the structure later (or never). Treat them as two separate projects.
## The actual runtime bites
- **`Kernel` middleware registration still works, but new features assume `bootstrap/app.php`.** If you stay on the old structure, some newer docs and packages will tell you to register things in `bootstrap/app.php` that your app registers in `Http/Kernel`. Pick one place per concern and know which you are on, mixing both silently double-registers or drops middleware.
- **Password rehashing on login.** Laravel 11 rehashes passwords automatically when the hashing work factor changes. Usually invisible, but if you have a custom auth path that bypasses the framework's hasher, it can fight this.
- **Default config was slimmed.** Many `config/*` files are no longer published by default in 11, the framework reads sensible defaults. Your app still has its published copies, which is fine, but new config keys added in 11 will not appear in your old files. Diff against the new stubs for keys you care about (e.g. per-second rate limiting).
- **SQLite is the new-install default DB**, and some SQLite-specific defaults tightened. This only bites if you actually run SQLite; MySQL/Postgres apps are unaffected.
## Checklist
- [ ] PHP 8.2 confirmed
- [ ] Decided explicitly: keep old skeleton (recommended for the upgrade) vs migrate to slim (separate task)
- [ ] Not mixing `Http/Kernel` and `bootstrap/app.php` for the same middleware
- [ ] Diffed `config/*` for new 11 keys you want
- [ ] Custom auth path checked against automatic rehashing
- [ ] Suite green on staging
Official rename list: `laravel.com/docs/11.x/upgrade`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |