-
Notifications
You must be signed in to change notification settings - Fork 452
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
Add support for .NET 8.0.10 and 8.0.11 #10625
Comments
This is a platform issue rather than a functions issue, we'll get this routed to the correct team. |
Hello @skisy Thank you for reporting we will check and get back with proper documentation |
Same issue here on linux Function App host, we were advised to create custom base image, which requires much effort form our side. Thats a lot of CVEs not fixed: .NET 8.0.10 release carries the security fixes: |
We've also been advised to use containers. |
Can we get an update on this please. Thanks |
Dear Microsoft, Could you please update the base images for Linux to include .NET version 8.0.11 as a minimum? |
Could you provide an update on this? Additionally, is there a confirmed release date? Thanks |
We have been actively working with the appropriate teams and the deployment is currently rolling out. We'll keep this updated as progress is made. Thank you all for the patience. |
Thank you for your response. We will follow the updates and wait for news. creates a new image, and will soon push it as a base image to Azure, so we can start using it in production already? I hope it will happen today or on Monday? :) |
What problem would the feature you're requesting solve? Please describe.
High severity security vulnerabilities exist in .NET 8.0.8, but the Windows Function App host does not contain 8.0.10 or 8.0.11 runtime. A month after 8.0.10 release, it is still not supported.
Describe the solution you'd like
.NET 8.0.10 runtime (as a minimum) is added to Function App host.
Describe alternatives you've considered
Using docker, dotnet-docker has support for 8.0.10. Should not be necessary as PaaS resources should be maintained correctly.
Additional context
The text was updated successfully, but these errors were encountered: