4.0.1 Remove remaining mentions to Azure Functions v3

Remove remaining mentions to Azure Functions v3

4.0.0 Drop support for .NET Core 3.1/.NET 6 and Azure Functions v3

Drop support for:

• .NET Core 3.1
• .NET 6
• Azure Functions v3

You can use the previous version is you still need support.

3.1.0 Add support for .NET 8

3.1.0 Support .NET 8

3.0.1-alpha.0.49

Fix func permissions

3.0.0 Use .NET Standard 2.0 instead of 2.1

I shouldn't have used .NET Standard 2.1 to start with. See The future of .NET Standard and .NET Standard.

I don't expect this to be a breaking change but I decided to bump the major to give consumers a heads-up.

2.0.2 Document in-process model requirement

• Update Functions libraries and SDK to latest

2.0.1 Make applicationName optional

applicationName is now optional. When applicationName is not provided, neither the 'Cloud role name', nor the 'Application version' will be set.

2.0.1-alpha.0.10

Merge b38bb3bfafa112799fecaa5205e765563b850a2c into 98c6ca7005d21b71d…

2.0.1-alpha.0.9

applicationName is now optional. When applicationName is not provided, neither the 'Cloud role name', nor the 'Application version' will be set.

2.0.0 Use IOptions to make configuration more flexible

🚨 This is a breaking change 🚨

Discarding Service Bus trigger traces, Function execution traces, and Health Function requests is now configured using application settings.

The customisation can be completely disabled by setting an application setting as an escape hatch.

See https://github.com/gabrielweyer/azure-functions-telemetry/blob/main/docs/Migrate-from-v1-to-v2.md for a migration guide.