Repository navigation
13.0.0 — Laravel 13
Themosis 13 runs on Laravel 13 (illuminate/* ^13.35). Laravel 12 stays on the 12.x branch (^12.0) for fixes.
Requirements
- PHP 8.3+ (was 8.2). On PHP 8.4+ Composer installs the Symfony 8 components; PHP 8.3 gets Symfony 7.4.
- WordPress 6.8+ (tested on WordPress 7.1, PHP 8.5).
Dependencies
illuminate/*^12.69→^13.35laravel/tinker^3.0only (2.x doesn't support Laravel 13)guzzlehttp/guzzle^7.8.2|^8.0(Laravel 13 allows Guzzle 8)- Floors raised to Laravel 13's:
dragonmantank/cron-expression ^3.4,vlucas/phpdotenv ^5.6.1,ramsey/uuid ^4.7 - Dev:
beyondcode/laravel-dump-serverremoved (no Laravel 13 release), PHPUnit^12.5.8|^13.0.3, paratest^7.20, PHPUnit configuration migrated to the current schema
Laravel 13 port
- CSRF: new
PreventRequestForgerymiddleware (Laravel 13). Same-origin requests (Sec-Fetch-Site) pass without a token;allowSameSite(),useOriginOnly(), staticexcept().VerifyCsrfTokenis now a deprecated subclass, so app middleware extending it keeps working. - Exception handler:
dontRetry(),dontRetryWhen(),shouldStopRetries()(used by the queue worker),isReporting(),contextForException(),buildContextForException()(used by the JSON log formatter).OriginMismatchExceptionrenders a 403 and isn't reported. - Console:
findCommand()on the console kernel. - Routing: domain routes match before routes without a domain.
- Caches:
route:cacherestores the facades and container instance after booting a fresh app;optimize --except=routes,view:cache. - Bus/events:
PendingChain(prepend(),append(),dispatchIf()/dispatchUnless()) and the eventDispatchabletrait synced with Laravel 13. - Logging: with
logging.deprecations.trace, deprecations are logged with theErrorExceptionin the context (Laravel 13 format, with a stack trace).
Fixes
- Terminating callbacks never ran:
dispatchAfterResponse()jobs and the components' terminating callbacks were silently dropped. Bus::chain()andAnonymousEventfailed with "class not found" (Illuminate\Foundation\Bus\PendingChain,Illuminate\Foundation\Events\Dispatchableare now aliased).- The encrypted
X-XSRF-TOKENheader was never read (X-CSRF-TOKENwas checked twice). unauthenticated()threw anArgumentCountError(redirectTo()without the request). Without a redirect target it now returns an empty 401 instead of redirecting toroute('login').- Routes sharing a URI and their last HTTP method (e.g.
POSTandPUT|POST) were dropped fromgetRoutes()and from the route cache. Twig\Environmentresolved a new environment instead of the sharedtwigbinding (the alias still used the Twig 1 class name).- Application: added
isProduction()andgetBootstrapProvidersPath()(called by Laravel components),isLocal(),runningConsoleCommand()andcurrentLocale().
Upgrade notes for sites
- In
composer.json, require"themosis/framework": "^13.0"(and"php": "^8.3"), then runcomposer update. Sites still ondev-laravel-12-upgradeor^4.0stay on Laravel 12: that branch is frozen at 12.0.0, so move them to^12.0or^13.0. - Packages requiring
illuminate/*must allow 13.laravel/tinker3,laravel/ui4.6 andpropaganistas/laravel-phone6 do. - After deploying, rebuild the caches with
composer deploy(optimize, thenopcache:clear). Route and config caches built with Laravel 12 must not be reused. - Check the Laravel 13 changes that depend on your configuration (upgrade guide):
- the new cache/Redis prefixes, session cookie name,
cache.serializable_classes => falseand sessionserialization => jsononly come with Laravel 13's skeleton config files. Existing Themosisconfig/*.phpfiles keep their values; don't copy the new skeleton values without reading the guide (changing the session serialization or cookie logs users out); - pagination view names (
pagination::default→pagination::bootstrap-3); upsert()with an emptyuniqueBynow throws.
- the new cache/Redis prefixes, session cookie name,
- CSRF: where the
csrfmiddleware is enabled, same-origin requests now pass without a token (Laravel 13 behaviour). - The
errors.phpmu-plugin, which maskedE_DEPRECATEDwhileWP_DEBUGwas on, can be removed. Deprecations, including compile-time ones, go to thedeprecationschannel (WP_DEBUGon) or are discarded (WP_DEBUGoff), and are never displayed.
Known issues
make:authstays disabled (its stubs reference traits that don't exist).- On a fatal error, Themosis'
handleShutdownand WordPress' fatal error handler can both render.
Full changelog: 12.0.0...13.0.0