Skip to content

Commit 10fd2e4

Browse files
Merge pull request #303385 from ggailey777/patch-4
[Functions][Bundles] Added Madhura's content for updating bundles
2 parents cd40fa2 + a9ad25d commit 10fd2e4

File tree

2 files changed

+19
-4
lines changed

2 files changed

+19
-4
lines changed

articles/azure-functions/extension-bundles.md

Lines changed: 18 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Azure Functions Extension Bundles
33
description: Learn how to use extension bundles to make the correct set of Azure Functions trigger and binding extensions available in your non-.NET function code.
44
ms.topic: concept-article
5-
ms.date: 05/30/2025
5+
ms.date: 07/25/2025
66

77
#Customer intent: I want to understand how to correctly install extension bundles so that the functionality implemented in the extensions is available to my functions in my preferred development language.
88
---
@@ -19,7 +19,7 @@ Extension bundles add a predefined set of compatible binding extensions to your
1919

2020
When you create an Azure Functions project from a non-.NET template, extension bundles are already enabled in the app's `host.json` file.
2121

22-
## Defining an extension bundle reference
22+
## Define an extension bundle reference
2323

2424
You define an extension bundle reference in the `host.json` project file by adding an `extensionBundle` section, as in this example:
2525

@@ -46,7 +46,22 @@ Keep these considerations in mind when you work with extension bundles:
4646
- Use the latest version range to obtain optimal app performance and access to the latest features.
4747
- In the unlikely event that you can't use an extension bundle, you must instead [explicitly install extensions](./functions-bindings-register.md#explicitly-install-extensions).
4848

49-
## Previewing extension bundles
49+
## Upgrade extension bundles
50+
51+
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.
52+
53+
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).
54+
55+
Keep these considerations in mind when upgrading the extension bundle version used by your app:
56+
57+
+ 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).
58+
+ 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.
59+
+ 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.
60+
+ 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:
61+
+ Local project: extensions are updated locally when Core Tools starts, either from the `func start` command or when debugging in your development tools.
62+
+ Function app: extensions are updated when you deploy the updated host.json file to your function app in Azure.
63+
64+
## Preview extension bundles
5065

5166
Prerelease versions of specific binding extensions are maintained in a preview extension bundle: `Microsoft.Azure.Functions.ExtensionBundle.Preview`. You can use this preview extension bundle to take advantage of preview extensions and new behaviors in existing extensions before they reach general availability (GA).
5267

articles/azure-functions/functions-bindings-register.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ To manually install binding extensions:
6060

6161
1. Validate your app functionality locally and then redeploy your project, including `extensions.csproj`, to your function app in Azure.
6262

63-
As soon as possible, you should [switch your app back to using the latest supported extension bundle](./extension-bundles.md#defining-an-extension-bundle-reference).
63+
As soon as possible, you should [switch your app back to using the latest supported extension bundle](./extension-bundles.md#define-an-extension-bundle-reference).
6464
::: zone-end
6565

6666
## Related content

0 commit comments

Comments
 (0)