Upgrade to Laravel 13 - #181
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps
illuminate/*andlaravel-zero/frameworkto ^13.0, and swapsshipfastlabs/agent-detectorforlaravel/agent-detector^2.0 now that the package has moved to the Laravel org. The new package renamed its namespace toLaravel\AgentDetector, so the two imports inapp/Supportwere updated to match, along with the package name in the build script's runtime list.Laravel 13 requires PHP 8.3, so the floor moves from 8.2 to 8.3 in composer.json and the README. This is not really a new break:
illuminate/supportcallsjson_validate(), which is 8.3 only, so an 8.2 user was going to fatal either way. Declaring it means composer says so up front instead. PHP 8.2 also reached end of security support at the end of last year.One test cleanup along the way:
SensitiveJsonOutputTestCommandwas declared inline in the test file, in the global namespace under a Tests\ PSR-4 root. It now lives in tests/Fixtures.