Skip to content

Laravel 11.x Compatibility #91

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

Merged
merged 1 commit into from
Apr 22, 2024

Conversation

laravel-shift
Copy link
Contributor

This is an automated pull request from Shift to update your package code and dependencies to be compatible with Laravel 11.x.

Before merging, you need to:

  • Checkout the l11-compatibility branch
  • Review all comments for additional changes
  • Thoroughly test your package

If you do find an issue, please report it by commenting on this PR to help improve future automation.

@laravel-shift
Copy link
Contributor Author

⚠️ The latest version of Laravel has a dependency for phpunit/phpunit of ^10.5. If you would like to also upgrade your tests, you may run the PHPUnit 10 Shift for free.

@laravel-shift
Copy link
Contributor Author

ℹ️ Shift detected you do not have a CI workflow using GitHub Actions. If you would like, Shift can help you get started with the CI Generator. Although the Shift is paid, GitHub Actions is free and having a CI workflow will improve the stability and review process for your package.

@laravel-shift
Copy link
Contributor Author

⚗️ Using this package? If you would like to help test these changes or believe them to be compatible, you may update your project to reference this branch.

To do so, temporarily add Shift's fork to the repositories property of your composer.json:

{
    "repositories": [
        {
            "type": "vcs",
            "url": "https://github.com/laravel-shift/laravel-dump-server.git"
        }
    ]
}

Then update your dependency constraint to reference this branch:

{
    "require": {
        "beyondcode/laravel-dump-server": "dev-l11-compatibility",
    }
}

Finally, run: composer update

This was referenced Mar 7, 2024
@reppair
Copy link

reppair commented Mar 24, 2024

We could make use of L11 support ❤️

@nik-418
Copy link

nik-418 commented Mar 27, 2024

t'would be great 👍

@Redtama
Copy link

Redtama commented Mar 29, 2024

Yes please L11 support would be wonderful! ❤️

@jleonardolemos
Copy link

To merge this PR will be necessary to fix the phpunit.xml attibutes due to the phpunit update.

Screenshot from 2024-04-01 11-33-51

After upgrading my own packages i will do a PR here.

@tanerkay
Copy link

tanerkay commented Apr 3, 2024

To merge this PR will be necessary to fix the phpunit.xml attibutes due to the phpunit update.

it's not so much an upgrade, but rather added support for a newer phpunit version, in addition to the current ones

note that this package currently supports packages down to laravel 5.? and phpunit 7

@TSchuermans
Copy link

@mpociot would it be possible to have a look at this PR?
Sorry for bothering you.

@devnicolas1
Copy link

Also expecting this PR to merged. Would be great to have an update about it! :)

@renky
Copy link

renky commented Apr 18, 2024

To merge this PR will be necessary to fix the phpunit.xml attibutes due to the phpunit update.

it's not so much an upgrade, but rather added support for a newer phpunit version, in addition to the current ones

note that this package currently supports packages down to laravel 5.? and phpunit 7

Since this package doesn't really have big changes over time, I think it sould be fine for all the people out there using Laravel5 and phpunit 7 to stick with an old version. Finally it could get a new major number and drop support for older versions, but anyway, it should go forward

@flexchar
Copy link

Maybe someone could shot a kind email to them regarding this at [email protected] ✌️

@renky
Copy link

renky commented Apr 22, 2024

I already contacted them right before the weekend. So let's wait...

@mechelon mechelon merged commit d0a1ae1 into beyondcode:master Apr 22, 2024
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.