Laravel 11.x Compatibility#117
Conversation
|
|
|
ℹ️ 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 11 has removed its dependency on Shift detected potential uses of these within the following files. You should review these instances and, if they are still needed, reference the Upgrade Guide for native alternatives.
|
|
⚗️ 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/eloquent-model-generator.git"
}
]
}Then update your dependency constraint to reference this branch: {
"require": {
"krlove/eloquent-model-generator": "dev-l11-compatibility",
}
}Finally, run: |
|
This one doesn't seem to work for me FWIW, at least for postgres: I removed this package from my project for now to continue with my Laravel 11 upgrade until this can be fixed, assuming that it's an issue with eloquent-model-generator. |
|
Can we get an update on this? It would be so handy to have this on L11. |
|
@Jonyorker You can use it temporarily fwiw, and see if that works, the instructions for that are here: #117 (comment) I think this repo is no longer maintained. |
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:
l11-compatibilitybranchIf you do find an issue, please report it by commenting on this PR to help improve future automation.