-
Notifications
You must be signed in to change notification settings - Fork 11.1k
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
[9.x] Deprecation Test Improvements #45317
Conversation
@crynobone I thought we already were treating deprecations as exceptions: https://github.com/laravel/framework/blob/9.x/phpunit.xml.dist#L6 This can definitely just go into the current test suite. No need for a separate workflow 👍 |
Full write-up regarding the changes: orchestral/testbench-core#97 |
@driesvints Not in application tests that actually need to boot the framework. As Laravel boots, and HandleExceptions actually proxy those deprecations to a specific log channel, if any. @crynobone Out of curiosity, can you point me to the exact code, on testbench, that modifies the behavior on |
Testbench would bootstrap |
Hey @crynobone. I'm gonna take this one over and see if I can solve all issues. I think the right way to tackle prefer-lowest is to bump minimum versions. For anything we cannot solve through Composer we can use the already provided step here: https://github.com/laravel/framework/blob/9.x/.github/workflows/tests.yml#L84 |
@crynobone I feel like we're still missing things here. For example, the first failing test I look at is:
But there's no |
Seems like it's the case in most tests: https://github.com/laravel/framework/actions/runs/3707093739/jobs/6283094947#step:9:159
|
fakerphp/faker
from^1.9.2
to^1.21
league/commonmark
from^2.2
to^2.2.1