Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow Laravel 12 #2665

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Allow Laravel 12 #2665

wants to merge 1 commit into from

Conversation

stayallive
Copy link
Collaborator

@stayallive stayallive commented Mar 8, 2025

  • Added or updated tests
  • Documented user facing changes
  • Updated CHANGELOG.md

Changes

Allow Laravel 12 and adjust tests and dependencies where needed.

There are some interesting things.

  • dms/phpunit-arraysubset-asserts dependency is not yet out for the phpunit we need for L12 and thus I've included the fork with the compatible PR. Since it's a dev only dependency this might be fine for now but should be reverted in the future. It does allow us to move forward at least.
  • Removed laravel/scout versions since Scout doesn't update its version every time Laravel does, this was probably done in error in previous Laravel version updates.
  • unset.possiblyHookedProperty phpstan errors is a bug on their side, should be fixed soon-ish: Fix unsetting array item triggers unset.possiblyHookedProperty phpstan/phpstan-src#3855

Breaking changes

None. Laravel 12 is also a super simple release for us from what it seems (in the BC department at least).

@stayallive stayallive force-pushed the laravel-12 branch 2 times, most recently from 911d7e3 to ed42b1d Compare March 8, 2025 13:51
@stayallive
Copy link
Collaborator Author

This is shaking out some nasty phpstan stuff, a small part is probably a bug on their side (for php 8.4; phpstan/phpstan-src#3855) but others seems to be related to larastan maybe not correctly detecting the testing mixing. Not sure how to fix this. Tests are passing so it's all working but it looks like phpstan/larastan might not understand some stuff all of a sudden. Quick search on both repo's did not yield any red flags. It might be on their side since only the "highest" dependency phpstan runs are failing (and 8.4 runs because of linked bug).

Appreciate a quick look @spawnia since you might know what is going on here or maybe we should just have a little patience and this will resolve itself in a few days 🫣

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant