You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We now would like to have the Azure Functions extension for VS Code to show warnings when a stack is selected and has an EOL date within 6 months (or if EOL already passed).
Verbiage for the warning can be based on the Important note on the Azure Functions runtime versions overview documentation:
"After the deadline, function apps can be created and deployed, and existing apps continue to run. However, your apps won't be eligible for new features, security patches, performance optimizations, and support until you upgrade them".
This extension already uses the Stacks API.
The text was updated successfully, but these errors were encountered:
Hi @nzthiago I noticed in the Azure Functions Stacks API that Powershell 7.0 and 7.2 do not have an associated End of Life date. Is that something that will be added?
Hi @nzthiago I noticed in the Azure Functions Stacks API that Powershell 7.0 and 7.2 do not have an associated End of Life date. Is that something that will be added?
It looks like the dates were added by @Francisco-Gamino with this PR five days ago to address this. They should start showing up when a future deployment includes this PR.
The Azure Functions Stacks API has been updated to include End of Life dates based on our Azure Functions language runtime support policy table.
We now would like to have the Azure Functions extension for VS Code to show warnings when a stack is selected and has an EOL date within 6 months (or if EOL already passed).
Verbiage for the warning can be based on the Important note on the Azure Functions runtime versions overview documentation:
"After the deadline, function apps can be created and deployed, and existing apps continue to run. However, your apps won't be eligible for new features, security patches, performance optimizations, and support until you upgrade them".
This extension already uses the Stacks API.
The text was updated successfully, but these errors were encountered: