sonarcloud[bot]
commented
5 days ago 
Quality Gate passed
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
This PR contains the following updates:
1.23.0->2.0.0Release Notes
Azure/azure-functions-dotnet-worker (Microsoft.Azure.Functions.Worker)
### [`v2.0.0`](https://redirect.github.com/Azure/azure-functions-dotnet-worker/releases/tag/2.0.0): Microsoft.Azure.Functions.Worker 2.0.0 [Compare Source](https://redirect.github.com/Azure/azure-functions-dotnet-worker/compare/1.23.0...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](https://redirect.github.com/Azure/azure-functions-dotnet-worker/issues/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](https://redirect.github.com/Azure/azure-functions-dotnet-worker/issues/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](https://redirect.github.com/Azure/azure-functions-dotnet-worker/issues/2716)) - Removed the default value for HttpStatusCode in WriteAsJsonAsync ([#2720](https://redirect.github.com/Azure/azure-functions-dotnet-worker/issues/2720)) - Removed fallback command line argument reading code for grpc worker startup options. ([#1908](https://redirect.github.com/Azure/azure-functions-dotnet-worker/issues/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: ```csharp var host = new HostBuilder() .ConfigureFunctionsWorkerDefaults(options => { options.EnableUserCodeException = false; options.IncludeEmptyEntriesInMessagePayload = false; }) ``` ##### Microsoft.Azure.Functions.Worker.Grpc 2.0.0 - Refer to metapackageConfiguration
📅 Schedule: Branch creation - "before 07:00 on Thursday" in timezone Europe/Oslo, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.