Add upgrade logs for Laravel 11 to 12 migration across multiple projects
- Created detailed upgrade log for deversspecialist with phases including Composer updates, Filament upgrades, Tailwind migration, Pest updates, and final verification. - Added upgrade log for goos project, documenting version changes, encountered issues, and resolutions during the migration process. - Documented Composer dependency upgrades for qlshandling, highlighting significant changes and necessary code adjustments. - Introduced a template for future upgrade logs to standardize documentation for Laravel migrations.
This commit is contained in:
132
Work/Projects/Laravel-v12-Migration/TEMPLATE.md
Normal file
132
Work/Projects/Laravel-v12-Migration/TEMPLATE.md
Normal file
@@ -0,0 +1,132 @@
|
||||
# Update Log: [Project Name] — Laravel 11 → 12 + Ecosystem
|
||||
|
||||
> **Date:** YYYY-MM-DD
|
||||
> **Branch:** `upgrade/laravel-12-full`
|
||||
> **AI Tool:** (e.g., Claude Code, Cursor)
|
||||
|
||||
---
|
||||
|
||||
## Starting State
|
||||
|
||||
| Package | Before | Target |
|
||||
|---------|--------|--------|
|
||||
| PHP | | (no change expected) |
|
||||
| laravel/framework | | ^12.0 |
|
||||
| filament/filament | | ^5.0 |
|
||||
| livewire/livewire | | ^4.0 |
|
||||
| tailwindcss | | ^4.0 |
|
||||
| pestphp/pest | | ^4.0 |
|
||||
| | | |
|
||||
|
||||
**Baseline tests:** _X passed (Y assertions)_
|
||||
**Baseline build:** _Success / Fail_
|
||||
|
||||
---
|
||||
|
||||
## Upgrade Phases
|
||||
|
||||
### Phase 1: Pre-Flight
|
||||
|
||||
- [ ] Branch created
|
||||
- [ ] Baseline tests recorded
|
||||
- [ ] Baseline build verified
|
||||
- [ ] Reference document consulted (`Laravel-12-Migration-Problems-and-Solutions.md`)
|
||||
|
||||
### Phase 2: Composer — Laravel 12
|
||||
|
||||
- [ ] Blockers resolved (codezero, resend, laravel-lang, etc.)
|
||||
- [ ] Laravel framework ^12 installed
|
||||
- [ ] Bootstrap cache cleared
|
||||
- [ ] Tests pass, build succeeds
|
||||
|
||||
### Phase 3: Filament v3 → v4 → v5
|
||||
|
||||
- [ ] Rector v4 run for each directory: `app/`, `modules/`, `cms/`, etc.
|
||||
- [ ] Rector v5 run for each directory
|
||||
- [ ] Manual namespace fixes applied (grep scan)
|
||||
- [ ] Incompatible plugins replaced
|
||||
- [ ] Tests pass, build succeeds
|
||||
|
||||
### Phase 4: Tailwind v3 → v4
|
||||
|
||||
- [ ] Automated upgrade tool attempted
|
||||
- [ ] PostCSS config updated
|
||||
- [ ] CSS directives migrated (@theme, @utility, @import order)
|
||||
- [ ] Old TW plugins removed
|
||||
- [ ] Build succeeds
|
||||
- [ ] **Developer visual check completed** (pages inspected in browser)
|
||||
|
||||
### Phase 5: Pest / PHPUnit Upgrade
|
||||
|
||||
- [ ] Pest v4 / PHPUnit 12 installed
|
||||
- [ ] `setUp()` visibility fixed
|
||||
- [ ] `@test` annotations migrated to `#[Test]`
|
||||
- [ ] Test count matches baseline
|
||||
|
||||
### Phase 6: NPM Updates
|
||||
|
||||
- [ ] Major frontend packages upgraded
|
||||
- [ ] Breaking import changes fixed
|
||||
- [ ] Build succeeds
|
||||
|
||||
### Phase 7: Final Verification
|
||||
|
||||
- [ ] Tests pass (count matches baseline)
|
||||
- [ ] Build succeeds (client + SSR)
|
||||
- [ ] Pint passes
|
||||
- [ ] `composer outdated --direct` reviewed
|
||||
- [ ] `npm outdated` reviewed
|
||||
- [ ] `php artisan about` confirms Laravel 12
|
||||
|
||||
---
|
||||
|
||||
## Exceptions & Issues
|
||||
|
||||
Record every error, warning, or unexpected behavior here. Use this format:
|
||||
|
||||
### Issue 1: [Title]
|
||||
|
||||
**Symptom:** What you observed (error message, failing test, broken behavior).
|
||||
**Root Cause:** Why it happened (breaking change, deprecated API, version conflict).
|
||||
**Fix:** What resolved it.
|
||||
**Files affected:** List of files changed.
|
||||
|
||||
<!-- Repeat for each issue -->
|
||||
|
||||
---
|
||||
|
||||
## Packages Changed
|
||||
|
||||
| Package | From | To | Notes |
|
||||
|---------|------|----|-------|
|
||||
| | | | |
|
||||
|
||||
---
|
||||
|
||||
## What Worked Without Issues
|
||||
|
||||
List packages and steps that completed cleanly with no problems. This is useful for future reference so the AI does not over-research these.
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## Remaining / Unresolved
|
||||
|
||||
Items that were not fixed, intentionally skipped, or need follow-up.
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## Miscellaneous
|
||||
|
||||
Anything that does not fit the sections above. Observations, decisions, context, or notes for the next person.
|
||||
|
||||
-
|
||||
|
||||
---
|
||||
|
||||
## Recommendations for Next Session
|
||||
|
||||
-
|
||||
Reference in New Issue
Block a user