Microsoft.Azure.Functions.Worker.Extensions.EventGrid 3.4.3

Microsoft.Azure.Functions.Worker.Extensions.EventGrid 3.4.3

• Updated Microsoft.Azure.WebJobs.Extensions.EventGrid reference to 3.4.3

Microsoft.Azure.Functions.Worker 1.24.0

What's Changed

Microsoft.Azure.Functions.Worker (metapackage) 1.24.0

• Updating Microsoft.Azure.Functions.Worker.Core to 1.20.0
• Updating Microsoft.Azure.Functions.Worker.Grpc to 1.18.0

Microsoft.Azure.Functions.Worker.Core 1.20.0

• Updated service registrations for bootstrapping methods to ensure idempotency. (#2820)

Microsoft.Azure.Functions.Worker.Grpc 1.18.0

• Changed exception handling in function invocation path to ensure fatal exceptions bubble up. (#2789)
• Updated service registrations for bootstrapping methods to ensure idempotency. (#2820)

Microsoft.Azure.Functions.Worker 2.0.0

Microsoft.Azure.Functions.Worker (metapackage) 2.0.0

• Updating Microsoft.Azure.Functions.Worker.Core to 2.0.0
• Updating Microsoft.Azure.Functions.Worker.Grpc to 2.0.0
• Changed exception handling in function invocation path to ensure fatal exceptions bubble up.

Breaking Changes

• Dropping .NET 5 TFM support
• Capability IncludeEmptyEntriesInMessagePayload is now enabled by default (#2701)
  • This means that empty entries will be included in the function trigger message payload by default.
  • To disable this capability and return to the old behaviour, set IncludeEmptyEntriesInMessagePayload to false in the worker options.
• ValidateScopes is enabled for development environments by default.

Microsoft.Azure.Functions.Worker.Core 2.0.0

• Updating Azure.Core to 1.41.0
• New APIs supporting IHostApplicationBuilder
• Updated service registrations for bootstrapping methods to ensure idempotency.

Breaking Changes

• Capability EnableUserCodeException is now enabled by default (#2702)
  • This means that exceptions thrown by user code will be surfaced to the Host as their original exception type, instead of being wrapped in an RpcException.
  • To disable this capability and return to the old behaviour, set EnableUserCodeException to false in the worker options.
  • The EnableUserCodeException property in WorkerOptions has been marked as obsolete and may be removed in a future release.
• Rename ILoggerExtensions to FunctionsLoggerExtensions to avoid naming conflict issues (#2716)
• Removed the default value for HttpStatusCode in WriteAsJsonAsync (#2720)
• Removed fallback command line argument reading code for grpc worker startup options. (#1908)

Setting Worker Options Example

If you need to disable these capabilities and return to the old behaviour, you can set the worker options as follows:

var host = new HostBuilder()
.ConfigureFunctionsWorkerDefaults(options =>
{
    options.EnableUserCodeException = false;
    options.IncludeEmptyEntriesInMessagePayload = false;
})

Microsoft.Azure.Functions.Worker.Grpc 2.0.0

• Refer to metapackage

Microsoft.Azure.Functions.Worker.Sdk 2.0.0

What's Changed

Microsoft.Azure.Functions.Worker.Sdk 2.0.0

• Updated Microsoft.Azure.Functions.Worker.Sdk.Generators reference to 1.3.4.
• Setting _ToolingSuffix for TargetFrameworkVersion v9.0
• Adding support for SDK container builds with Functions base images
• Support for dotnet run

Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore 2.0.0

What's Changed

Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore 2.0.0

• Addressing fix for AspNetCoreResponseCookies cookie defaults (#2811)
• Support for IHostApplicationBuilder

Microsoft.Azure.Functions.Worker.ApplicationInsights 2.0.0

What's Changed

Microsoft.Azure.Functions.Worker.ApplicationInsights 2.0.0

• Updated Microsoft.Azure.Functions.Worker.Core dependency to 2.0.0

Microsoft.Azure.Functions.Worker.Extensions.SignalRService 1.15.0

Important: due to a common issue #2776 in dotnet isolated worker, this version can't use managed identity to connect to Azure SignalR Service until #2776 is fixed.

What's Changed

• Support SignalR trigger return value by @Y-Sindo in #2771

Full Changelog: signalr-extension-1.14.1...signalr-extension-1.15.0

Microsoft.Azure.Functions.Worker.Sdk 1.18.1

What's Changed

Microsoft.Azure.Functions.Worker.Sdk 1.18.1

• Updated Microsoft.Azure.Functions.Worker.Sdk.Generators reference to 1.3.4.

Microsoft.Azure.Functions.Worker.Sdk.Generators 1.3.4

• Changed FunctionExecutorGenerator to avoid generation of long if/else chains for apps with a large number of functions.

Microsoft.Azure.Functions.Worker.Sdk 1.18.0

What's Changed

Microsoft.Azure.Functions.Worker.Sdk 1.18.0

• Fix incorrect function version in build message (#2606)
• Fix inner build failures when central package management is enabled (#2689)
• Add support to publish a Function App (Flex Consumption) with ZipDeploy (#2712)
  • Add 'UseBlobContainerDeploy' property to identify when to use OneDeploy publish API endpoint ("<publish_url>/api/publish")
  • Enhance ZipDeploy deployment status logging by appending the 'status_message' (when defined) to the output messages

Microsoft.Azure.Functions.Worker.Sdk.Generators

Microsoft.Azure.Functions.Worker.Extensions.Tables 1.4.2

What's Changed

Microsoft.Azure.Functions.Worker.Extensions.Tables 1.4.2

• Updated Microsoft.Extensions.Azure dependency to 1.7.5