-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
Laravel 9.x Compatibility #16
Conversation
|
⚗️ 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": [
{
"type": "vcs",
"url": "https://github.com/laravel-shift/laravel-http-client-logger.git"
}
]
} Then update your dependency constraint to reference this branch: {
"require": {
"bilfeldt/laravel-http-client-logger": "dev-l9-compatibility",
}
} Finally, run: |
Currently awaiting approval of timacdonald/log-fake#32 |
Change repo to https://github.com/bilfeldt/log-fake.git
Did you just run a normal laravel shift 8-9 to produce this? Didn't know shift works on packages. |
No actually Shift made it automatically without my request: https://twitter.com/laravelshift/status/1490709249491714050?s=21 I assume they made them for packages used in projects that have used a paid shift. |
@lionslair, @bilfeldt, they are collected from our Can I Upgrade Laravel tool. It is offered to help community packages prepare for new releases of Laravel. |
That Did a pr though. Hmm interesting. If you have code incompatibility will it fix that or just the composer file |
@lionslair, its focus is mostly on compatibility. Future runs may try to analyze the code too. |
This is an automated pull request from Shift to update your package code and dependencies to be compatible with Laravel 9.x.
Before merging, you need to:
l9-compatibility
branchIf you do find an issue, please report it by commenting on this PR to help improve future automation.