Azure Functions Runtime 2.0.1262

In this release:

• Ensuring an app level middleware pipeline is registered

Azure Functions Runtime 2.0.12555

In this release:

• Block for environmentreload request to complete
• Reduce debounce time when app_offline.htm is created

Azure Functions Runtime 2.0.12549

In this release:

• allow -1 for in host.json to indicate unbounded timeout in Dedicated
• Fix for DurableTask SyncTriggers config parsing/Scaling
• Support for configuring HSTS (#4069)
• Add support for VFS API relative pathing
• Increase ANCM startup time limit. Fixes #4393
• Fix for Python worker HTTP raw body issue (Azure/azure-functions-python-worker#380)
• Processing ActionResult properly. Fixes #4369
• Other fixes/optimizations

Azure Functions Runtime 2.0.12507

Deployment completed

Release Notes

• Application Insights telemetry customDimensions dictionary now contains HostInstanceId. This is a unique id given to each Functions host. (#4501)
• [Bug Fix] Application Insights telemetry could have the incorrect operation id when running on consumption plan. This affected TimerTrigger, EventHubTrigger. (#4461)

Visual Studio Availability

Visual Studio updates will be released soon.

Azure Functions Runtime 2.0.12493

Release Notes

• [Linux] Enable mounting of user code package (#4373)
• [Java] Azure Functions Java Worker 1.4.1 (Release Notes)
• [PowerShell] Azure Functions PowerShell Worker 0.1.102-preview (Release Notes)
• [Node.js] Azure Functions Node.js Worker 1.0.3 (Release Notes)
• Sync function triggers on slot swap (#4402) and improve monitoring/diagnostic logs (#4401)
• Multiple language worker support (#4161)
  • Process count is configurable by AppSetting: FUNCTIONS_WORKER_PROCESS_COUNT
• [Bug Fix] Process management improvements around node.exe, python.exe, and java.exe
  • Fixes #3939, #4026, #4326, #4392, #4328
• [Bug Fix] Accept functionTimeout: null as a valid host.json configuration (#4373)
• [Bug Fix] Stop infinite recursion in extensions metadata generation on publish (#4055)
• [Bug Fix] Do not fail function when HTTP header 'request-context' is explicitly set (#4358)
• [Bug Fix] Fix for function apps encountering container disposed error when accessing master key (#4406)

Visual Studio Availability

This release has been made available to Visual Studio users. When running a V2 Function App project locally, you can verify if you are running this version by checking for the following in the console output:

Azure Functions Core Tools (XXX Commit hash: XXX)
Function Runtime Version: 2.0.12493.0

Appveyor build

https://ci.appveyor.com/project/appsvc/azure-webjobs-sdk-script-y8o14/builds/24792252/job/029p0flm1rmy88vs/artifacts

Azure Functions Runtime 1.0.12529

[Release in progress]

Release Notes

• Enable SyncTriggers cache; Support Disable Config #4496

Appveyor build

https://ci.appveyor.com/project/appsvc/azure-webjobs-sdk-script-y8o14/builds/25295063/artifacts

Azure Functions Runtime 1.0.12491

Release Notes

• [SyncTriggers] Improve SyncTriggers Logging and Monitoring (#4401), and add internal auth for SyncTriggers call (#4467)
• Add logic to register DELETE endpoints from extension webhooks (#4308)
• Fix WEBSITE_HOSTNAME going out of sync in slot swap (#4162)
• [SyncTriggers] Add SyncTriggers support to the v1 runtime, including background sync triggers (#4325)
• [AppInsights] Bump MaxTelemetryItemsPerSecond default to 20 (#3806)
• Fix size of keys growing during snapshot/refresh if they fail to decrpyt (#3034)

Appveyor build

https://ci.appveyor.com/project/appsvc/azure-webjobs-sdk-script-y8o14/builds/24640055

Azure Functions Runtime 2.0.12438

Release Notes

• Check for invalid services in Dependency Injection (prevent core services from being overridden)
• SyncTrigger improvements (#4145)
• [Bugfix] Fix for WEBSITE_HOSTNAME issue (#4162)
• PowerShell worker version 0.1.97-preview

PowerShell worker changes

• Support the dependency download to happen on a background thread spawned by the FunctionLoad request and if the dependency download is still in progress and the function execution is invoked from the azure portal then the user will get the message on the azure portal log window that the dependency download is in progress and the function execution will continue when the download is done
• Support json as a dataType for queueTrigger
• Adding InvocationId', 'FunctionDirectory' and 'FunctionName' to HttpTriggerWithMetadata
• Improvement in PowerShell unction execution throughput improvement depending upon the PowerShell
  thread pool

Appveyor build

https://ci.appveyor.com/project/appsvc/azure-webjobs-sdk-script-y8o14/builds/24110971/job/8uhio0f949a661bs/artifacts

Azure Functions Runtime v2.0.12427

Release Notes

• Identifying derived startup attributes
• Updated ASP.NET Core deps to 2.2.202
• Sync triggers for dedicated linux
• log execution event timestamp added
• Accepting DELETE in extension webhook route
• Adding Indexing errors to the error collection
• Updates to functions cold start
• RID catalog updated
• Diagnostics for linux consumption
• Fixes to extension bundle range resolution
• Revert: change to fallback load handling

Appveyor build

https://ci.appveyor.com/project/appsvc/azure-webjobs-sdk-script-y8o14/builds/24028849

Azure Functions Runtime 2.0.12408

Release Notes

• Cold start improvements.
• [Application Insights] HTTP Trigger now logs RequestTelemetry with richer request details

  • Properties resultCode, url, client_City, client_StateOrProvince, client_CountryOrRegion are now populated.

  • Method and path are logged to customDimensions.HttpMethod and customDimensions.HttpPath, respecively.

  • Auto-tracking of these properties is enabled by default. To disable and return to previous behavior, you can set the disable this by setting applicationInsights.httpAutoCollectionOptions.enableHttpTriggerExtendedInfoCollection to false in host.json. For example:

    {
      "version": "2.0",
      "logging": {
        "applicationInsights": {
          "httpAutoCollectionOptions": {
            "enableHttpTriggerExtendedInfoCollection" : false
          }
        }
      }
    }
    

Visual Studio Availability

This release has been made available to Visual Studio users. When running a V2 Function App project locally, you can verify if you are running this version by checking for the following in the console output:

Azure Functions Core Tools (2.6.666 Commit hash: 2ea98ed)
Function Runtime Version: 2.0.12408.0

Appveyor build

https://ci.appveyor.com/project/appsvc/azure-webjobs-sdk-script-y8o14/builds/23728189/job/04jqeye65364eq4g/artifacts