-
Notifications
You must be signed in to change notification settings - Fork 11.4k
Replace swiftmailer/swiftmailer package with symfony/mailer #39766
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
Comments
Sorry for creating a duplicate, Google Search came up empty for this issue. On the other hand, Release Notes say that Laravel 8 will be actively supported until July 26th, 2022. I think that replacing abandoned projects should be a part of active support. How can I explain to my clients that Laravel is the best framework, with the best support, if it uses abandoned packages? |
Replacing Swift Mailer with Symfony Mailer introduces breaking changes to Laravel, the list of which can be seen in the PR for Symfony Mailer -> #38481 Breaking changes can't be done on minor versions (those are allowed only on major versions) so there's nothing the Laravel team can do here about that. Besides it's not like Swift Mailer magically stopped working all of a sudden just because Symfony Mailer was released. Swift Mailer had little development going on for years as it's an old and stable/mature library. And Laravel 9 is gonna be released on January 25th which is just two months away. |
Description:
When I try to
run composer update
, I get the following message:Steps To Reproduce:
Type
composer update
into the consoleThe text was updated successfully, but these errors were encountered: