Skip to content

Commit 7191437

Browse files
Update extension-bundles-support-policy.md
Adding a section about preview bundles expectation.
1 parent bfaeab0 commit 7191437

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

articles/azure-functions/extension-bundles-support-policy.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,12 @@ Microsoft will provide advance notification before retiring a package/extension
2424

2525
After the retirement of a package/extension bundle version, function apps that use retired packages/extension bundle versions can still be created and deployed, and they continue to run on the platform. However, the retired packages/bundle version aren’t eligible for new features, security patches, and performance optimizations until you upgrade them to a supported extension bundle version. Additionally, functions apps using a retired extension bundle will need to be upgraded before receiving support.
2626

27-
## Bundle version state 
27+
# Preview Bundles
28+
29+
Preview bundles offer early access to Azure Functions extensions that are still in development. They are intended for evaluation and testing in non-production environments. These bundles may change without notice - functionality, bindings, or triggers can shift between versions, and performance or stability may vary. It's important to move to a Generally Available bundle version as soon as the needed features are available.
30+
To stay informed about what’s transitioning from preview to GA, monitor the [bundle release notes](https://github.com/Azure/azure-functions-extension-bundles/releases), extension documentation, and NuGet changelogs.
31+
32+
# Bundle version state 
2833

2934
This table shows the major bundle versions and their current lifecycle state: 
3035

0 commit comments

Comments
 (0)