Repository navigation
Conversation
Pins every diffIn* call as an explicit absolute or signed integer so results read the same on Carbon 2 and 3. Carbon 2 values are unchanged; tests pin direction and type at the priority sites.
…tion List tables and indexes through the schema builder, which Laravel 10.37+ and 12 both provide. Replace the removed Schema::getAllTables() fallbacks and alias the DataPurger catalog query, whose lower-case column name fails on MySQL 8. Sanctum 4 stops loading its migrations, so add a create migration that sorts after Sanctum 3's and before fix_personal_access_tokens. It is a no-op where the table exists and on the sandbox database, which has never had it.
Laravel 11+ ships a native Request::array(), and native methods win over macros, so on Laravel 12 this macro silently stops running. `?sort=a,b` and `?without=a,b` become a single value, and a sorted index returns a 500 for an unknown column. Renaming it now is safe on Laravel 10 and keeps the comma splitting after the upgrade. Callers and test harnesses follow the new name, with no behaviour change.
Released extensions still call the old name, and removing it breaks them against a core-api with this change. Storefront's suite hit that through released fleetops.
Requires illuminate ^12.69|^13.0, PHP ^8.2, Sanctum 4, Pest 3 and the matching majors of the notification channels, barcode, msgraph-mail and fast-paginate, plus the new majors of the spatial, countries and twilio forks. Source fixes: - PushNotification passes the config repository kreait/laravel-firebase 6 requires. Every FCM push would have failed on the old one-argument call. - QueryOptimizer no longer constructs a Grammar with no connection, and catches Throwable so an Error here can't take the query down. - ReportQueryErrorHandler ignores the host, port and database Laravel 11+ adds to QueryException messages, so an install's names can't decide the error category. Test fixes: Encrypter and Filesystem fakes implement the new contract methods, the money config path is set in the harness, and a guard test fails if a native method ever shadows an expansion again.
The native Request::array() wins over it here, so it does nothing.
…tion List tables and indexes through the schema builder, which Laravel 10.37+ and 12 both provide. Replace the removed Schema::getAllTables() fallbacks and alias the DataPurger catalog query, whose lower-case column name fails on MySQL 8. Sanctum 4 stops loading its migrations, so add a create migration that sorts after Sanctum 3's and before fix_personal_access_tokens. It is a no-op where the table exists and on the sandbox database, which has never had it. Set reports.average_execution_time to DOUBLE(8,2) in SQL, since Blueprint::float() stops defaulting to total and places on Laravel 11+.
chore(l12): drop Doctrine schema calls and add a guarded tokens migration
fix(request): rename the array macro to inputArray
…s/fast-paginate The same 2.0.0 release under its new name. composer audit now reports nothing, not even an abandoned package. Also raises phpspreadsheet to the patched 1.30.7.
feat!: move to Laravel 12 and Sanctum 4
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #334 +/- ##
===========================================
Coverage 100.00% 100.00%
- Complexity 9600 9691 +91
===========================================
Files 519 519
Lines 29841 29812 -29
===========================================
- Hits 29841 29812 -29
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
…0.0 ships Revert to fleetbase's api-contract.yml@main with no stack after the release.
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
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.
Summary
The v2.0.0 release branch: core-api on Laravel 12. It bumps
composer.jsonto2.0.0and replacesRELEASE.md, whose first line is> v2.0.0 ~ "Laravel 12", asrelease.ymlrequires.Not ready to merge. These PRs must merge into
release/v2.0.0first:Request::array()macro renamed toinputArray()getAllTablesremoved, guardedpersonal_access_tokensmigrationdiffIn*prep (a8fa020, merged in), which has no PR of its own#333 merges into this branch cleanly. Checked locally on
ec7f08e+4cb58a1: no conflicts, and afterwards the branch differs from #333 only byRELEASE.md.Release notes
RELEASE.mdcovers the breaking changes (Laravel 12 and PHP 8.2, Sanctum 4, Carbon 3, theinputArray()rename, Doctrine removal, fork majors), the FCM,QueryOptimizerand report-error fixes, dependency changes and upgrade steps.Testing
On #333's head
4cb58a1, resolved from Packagist with no path or VCS repositories: 2,410 Pest tests pass and the 100% coverage gate is met.composer auditexits 0 with no advisories and no abandoned packages, and nothing is ignored.The Postman contract can't pass here until the extensions and fleetbase/fleetbase#749 are on Laravel 12 (see #333). A local contract run against all the Laravel 12 branches assembled together is in progress, and its result will be reported before merge.
After merge
release.ymltagsv2.0.0. Then tag the extension releases built on^2.0, regenerate fleetbase/fleetbase#749's lock, and mark it ready.