-
Notifications
You must be signed in to change notification settings - Fork 447
Function Runtime Versioning
The Functions runtime runs as a site extension in your Function App. In your app settings, you'll find a version specifier FUNCTIONS_EXTENSION_VERSION which is set to a major version specifier, e.g.:
That value ~0.4 indicates that your Function App will stay on the 0.4 major version train. It won't be moved forward to any new major versions (which contain breaking changes). You will however be moved forward to new minor versions containing bug fixes, new features, etc. This allows you to manage when you take breaking changes. For release notes (including breaking changes) for each release, see here.
When we deploy a new major version, the Functions Portal will give you the option to move yourself forward:
All this update button does is set the FUNCTIONS_EXTENSION_VERSION app setting to a new value (the next major version specifier).
- Configuration Settings
- function.json
- host.json
- host.json (v2)
- Http Functions
- Function Runtime Versioning
- Official Functions developers guide
- Host Health Monitor
- Managing Connections
- Renaming a Function
- Retrieving information about the currently running function
- Site Extension Resolution
- Linux Consumption Regions
- Using LinuxFxVersion for Linux Function apps
- Out-of-proc Cancellation Tokens
- Assembly Resolution in Azure Functions
- ILogger
- Precompiled functions
- Official Functions C# developer reference
- Contributor Onboarding
- Development Process
- Deploying the Functions runtime as a private site extension
- Authoring & Testing Language Extensions
- Bindings in out-of-proc
- Language Extensibility
- Worker Capabilities
- Investigating and reporting issues with timer triggered functions not firing
- Sharing Your Function App name privately
- Azure Functions CLI release notes [moved here]
- Function App Zipped Deployment [deprecated]