Update azure-functions-dotnet-worker monorepo (major) #20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.10.0
->2.0.0
1.6.0
->2.0.0
5.0.1
->6.6.0
1.7.0
->2.0.0
1.3.0
->2.0.0
Release Notes
Azure/azure-functions-dotnet-worker (Microsoft.Azure.Functions.Worker)
v2.0.0
: Microsoft.Azure.Functions.Worker 2.0.0Compare Source
Microsoft.Azure.Functions.Worker (metapackage) 2.0.0
Microsoft.Azure.Functions.Worker.Core
to 2.0.0Microsoft.Azure.Functions.Worker.Grpc
to 2.0.0Breaking Changes
IncludeEmptyEntriesInMessagePayload
is now enabled by default (#2701)IncludeEmptyEntriesInMessagePayload
tofalse
in the worker options.ValidateScopes
is enabled for development environments by default.Microsoft.Azure.Functions.Worker.Core 2.0.0
Azure.Core
to 1.41.0IHostApplicationBuilder
Breaking Changes
EnableUserCodeException
is now enabled by default (#2702)EnableUserCodeException
tofalse
in the worker options.EnableUserCodeException
property in WorkerOptions has been marked as obsolete and may be removed in a future release.ILoggerExtensions
toFunctionsLoggerExtensions
to avoid naming conflict issues (#2716)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:
Microsoft.Azure.Functions.Worker.Grpc 2.0.0
v1.23.0
Compare Source
Microsoft.Azure.Functions.Worker.Core
to 1.19.0Microsoft.Azure.Functions.Worker.Grpc
to 1.17.0Azure.Core
to 1.41.0v1.22.0
: Microsoft.Azure.Functions.Worker 1.22.0Compare Source
What's Changed
Microsoft.Azure.Functions.Worker (metapackage) 1.22.0
Microsoft.Azure.Functions.Worker.Core
to 1.18.0Microsoft.Azure.Functions.Worker.Core 1.18.0
v1.21.0
Compare Source
Microsoft.Azure.Functions.Worker.Core
to 1.17.0Microsoft.Azure.Functions.Worker.Grpc
to 1.16.0Azure.Core
to 1.37.0v1.20.1
: Microsoft.Azure.Functions.Worker 1.20.1Compare Source
What's Changed
Microsoft.Azure.Functions.Worker (metapackage) 1.20.1
Microsoft.Azure.Functions.Worker.Core
1.16.1Microsoft.Azure.Functions.Worker.Core 1.16.1
v1.20.0
: Microsoft.Azure.Functions.Worker 1.20.0Compare Source
What's Changed
Microsoft.Azure.Functions.Worker (metapackage) 1.20.0
Microsoft.Azure.Functions.Worker.Core
1.16.0Microsoft.Azure.Functions.Worker.Grpc
1.15.0Microsoft.Azure.Functions.Worker.Core 1.16.0
Microsoft.Azure.Functions.Worker.Http.HttpHeadersCollection
HttpRequestDataExtensions.ReadAsStringAsync
updated to use enforce theUTF-8
default if the encoding is not specified. (#1987)Microsoft.Azure.Functions.Worker.Grpc 1.15.0
Thank you @endizhupani for your contributions to this release!
v1.19.0
Compare Source
Azure.Core
to 1.41.0v1.18.0
: Microsoft.Azure.Functions.Worker 1.18.0Compare Source
What's Changed
Microsoft.Azure.Functions.Worker (metapackage) 1.18.0
Microsoft.Azure.Functions.Worker.Core 1.14.0
InputConverterAttribute
. Implementers can now derive from this type to map attributes to custom converters. (#1712)Microsoft.Azure.Functions.Worker.Grpc 1.12.0
Full Changelog: Azure/azure-functions-dotnet-worker@1.17.0...1.18.0
v1.17.0
Compare Source
Azure.Core
to 1.41.0v1.16.0
Azure.Core
to 1.37.0Google.Protobuf
to 3.25.2Grpc.Net.Client
to 2.60.0Grpc.Net.ClientFactory
to 2.60.0Grpc.Core
to 2.46.6 (netstandard2.0 only)v1.14.1
: Microsoft.Azure.Functions.Worker 1.14.1Compare Source
What's Changed
Microsoft.Azure.Functions.Worker 1.14.1 (meta package)
Microsoft.Azure.Functions.Worker.Core 1.12.1
Microsoft.Azure.Functions.Worker.Grpc 1.10.1
v1.14.0
: Microsoft.Azure.Functions.Worker 1.14.0Compare Source
What's Changed
Microsoft.Azure.Functions.Worker 1.14.0 (meta package)
Microsoft.Azure.Functions.Worker.Core 1.12.0
ArgumentOutOfRangeException
when usingHttpDataRequestDataExtensions.ReadAsStringAsync
in .NET Framework (#1466)Microsoft.Azure.Functions.Worker.Grpc 1.10.0
null
reference exception when retry context is not set (#1476)v1.13.0
: Microsoft.Azure.Functions.Worker 1.13.0Compare Source
What's Changed
Microsoft.Azure.Functions.Worker 1.13.0 (meta package)
Microsoft.Azure.Functions.Worker.Core 1.11.0
Microsoft.Azure.Functions.Worker.Grpc 1.11.0
Microsoft.Azure.Functions.ApplicationInsights 1.0.0-preview4
Full Changelog: Azure/azure-functions-dotnet-worker@1.10.1...1.13.0
v1.10.1
: Microsoft.Azure.Functions.Worker 1.10.1Compare Source
WorkerOptions additions:
Full Changelog: Azure/azure-functions-dotnet-worker@1.10.0...1.10.1
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.