Merge pull request #303544 from ggailey777/patch-4

[Functions] Remove the supported bundles table section

Author: prmerger-automator[bot]

articles/azure-functions/extension-bundles.md

@@ -25,7 +25,7 @@ You define an extension bundle reference in the `host.json` project file by addi
 
 [!INCLUDE [functions-extension-bundles-json](../../includes/functions-extension-bundles-json.md)]
 
-## Supported extension bundles
+<!---## Supported extension bundles
 
 This table lists all `Microsoft.Azure.Functions.ExtensionBundle` bundle versions and the current [support state](#support-policy):
 
@@ -36,7 +36,7 @@ This table lists all `Microsoft.Azure.Functions.ExtensionBundle` bundle versions
 | [2.x](https://github.com/Azure/azure-functions-extension-bundles/blob/main-v2/src/Microsoft.Azure.Functions.ExtensionBundle/extensions.json) | `[2.*, 3.0.0)` | Deprecated | May 30, 2026 |
 | [1.x](https://github.com/Azure/azure-functions-extension-bundles/blob/v1.x/src/Microsoft.Azure.Functions.ExtensionBundle/extensions.json) | `[1.*, 2.0.0)` | Deprecated | May 30, 2026 |
 
-The default extension bundles are defined via version ranges. To see the `extensions.json` definition file that generates the current bundle version for a major extension, select the link in the table.
+The default extension bundles are defined via version ranges. To see the `extensions.json` definition file that generates the current bundle version for a major extension, select the link in the table.-->
 
 ## Considerations for extension bundles
 
@@ -50,12 +50,12 @@ Keep these considerations in mind when you work with extension bundles:
 
 It's important to keep your bundle version up-to-date so that your apps can continue to be eligible for new features, security patches, and performance optimizations. 
 
-To upgrade your app to the most recent bundle, edit the host.json file in the root of your app project. Replace the value of `extensionBundle.version` with the most recent [supported extension bundles version](#supported-extension-bundles).
+To upgrade your app to the most recent bundle, edit the host.json file in the root of your app project. Replace the value of `extensionBundle.version` with the most recent supported extension bundles version.
 
 Keep these considerations in mind when upgrading the extension bundle version used by your app:
 
 + The contents of the latest 4.x bundle can always be found at [this release page in the repo](https://github.com/Azure/azure-functions-extension-bundles/releases/latest).
-+ Review the reference documentation for any extensions used by your app to look for any breaking changes between versions. For the list of extension versions included in the default bundle, see the `extension.json` project file linked [from this table](#supported-extension-bundles). You can also review the [bundle releases page](https://github.com/Azure/azure-functions-extension-bundles/releases) in the bundles repo for a specific bundle version tags.
++ Review the reference documentation for any extensions used by your app to look for any breaking changes between versions. <!---For the list of extension versions included in the default bundle, see the `extension.json` project file linked [from this table](#supported-extension-bundles).--> You can review the [bundle releases page](https://github.com/Azure/azure-functions-extension-bundles/releases) in the bundles repo for specific bundle version tags.
 + Always verify your app locally after upgrading the bundle version to ensure compatibility with the updated extensions. You can use the [func start](functions-core-tools-reference.md#func-start) command in Azure Functions Core Tools or F5 in Visual Studio or Visual Studio Code to run your function app locally.
 + The way that you trigger extensions to be updated based on changes to the bundle version in the host.json file depends on your app environment:
   + Local project: extensions are updated locally when Core Tools starts, either from the `func start` command or when debugging in your development tools.