We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Question from slack: "Is there like a mailing list I can subscribe to to get notifications of Symfony security issues?"
Page wise, you can see them at: https://symfony.com/blog/category/security-advisories. But there's no clear way of receiving updates regarding these CVEs. In order to receive updates regarding those security advisories, you have to register to the roadmap updates on: https://symfony.com/roadmap, where you have to manage your subscriptions. On the following page (https://symfony.com/account/notifications) you can specify what you want to receive.
My proposal is to add a link on the security advisories page, to that same page. This way it should be easier to register for those specific updates.
The text was updated successfully, but these errors were encountered:
/cc @javiereguiluz
Sorry, something went wrong.
@iltar thanks for proposing this improvement. We've added a new message to tell about the email notifications. Once deployed, it'd look like this:
Awesome, thanks!
Great!
No branches or pull requests
Question from slack: "Is there like a mailing list I can subscribe to to get notifications of Symfony security issues?"
Page wise, you can see them at: https://symfony.com/blog/category/security-advisories. But there's no clear way of receiving updates regarding these CVEs. In order to receive updates regarding those security advisories, you have to register to the roadmap updates on: https://symfony.com/roadmap, where you have to manage your subscriptions. On the following page (https://symfony.com/account/notifications) you can specify what you want to receive.
My proposal is to add a link on the security advisories page, to that same page. This way it should be easier to register for those specific updates.
The text was updated successfully, but these errors were encountered: