Tags: devlooped/WhatsApp
Tags
Minor doc comment fix on options format for numbers
Normalize user's numbers automatically on every payload This makes it easier to just Reply to a message or Send without having to normalize anything.
Bump the azure group with 6 updates Bumps the azure group with 6 updates: | Package | From | To | | --- | --- | --- | | [Microsoft.Azure.Functions.Worker.Extensions.Storage.Queues](https://github.com/Azure/azure-functions-dotnet-worker) | `5.5.1` | `5.5.2` | | [Microsoft.Extensions.Configuration](https://github.com/dotnet/runtime) | `8.0.0` | `5.0.0` | | [Microsoft.Extensions.Configuration.EnvironmentVariables](https://github.com/dotnet/runtime) | `8.0.0` | `5.0.0` | | [Microsoft.Extensions.Configuration.UserSecrets](https://github.com/dotnet/runtime) | `8.0.1` | `5.0.0` | | [Microsoft.Extensions.DependencyInjection](https://github.com/dotnet/runtime) | `8.0.1` | `5.0.0` | | [Microsoft.Extensions.Options.ConfigurationExtensions](https://github.com/dotnet/runtime) | `8.0.0` | `5.0.0` | Updates `Microsoft.Azure.Functions.Worker.Extensions.Storage.Queues` from 5.5.1 to 5.5.2 - [Release notes](https://github.com/Azure/azure-functions-dotnet-worker/releases) - [Changelog](https://github.com/Azure/azure-functions-dotnet-worker/blob/main/release_notes.md) - [Commits](https://github.com/Azure/azure-functions-dotnet-worker/commits) Updates `Microsoft.Extensions.Configuration` from 8.0.0 to 5.0.0 - [Release notes](https://github.com/dotnet/runtime/releases) - [Commits](dotnet/runtime@v8.0.0...v5.0.0) Updates `Microsoft.Extensions.Configuration.EnvironmentVariables` from 8.0.0 to 5.0.0 - [Release notes](https://github.com/dotnet/runtime/releases) - [Commits](dotnet/runtime@v8.0.0...v5.0.0) Updates `Microsoft.Extensions.Configuration.UserSecrets` from 8.0.1 to 5.0.0 - [Release notes](https://github.com/dotnet/runtime/releases) - [Commits](dotnet/runtime@v8.0.1...v5.0.0) Updates `Microsoft.Extensions.DependencyInjection` from 8.0.1 to 5.0.0 - [Release notes](https://github.com/dotnet/runtime/releases) - [Commits](dotnet/runtime@v8.0.1...v5.0.0) Updates `Microsoft.Extensions.Options.ConfigurationExtensions` from 8.0.0 to 5.0.0 - [Release notes](https://github.com/dotnet/runtime/releases) - [Commits](dotnet/runtime@v8.0.0...v5.0.0) --- updated-dependencies: - dependency-name: Microsoft.Azure.Functions.Worker.Extensions.Storage.Queues dependency-version: 5.5.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: azure - dependency-name: Microsoft.Extensions.Configuration dependency-version: 5.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: azure - dependency-name: Microsoft.Extensions.Configuration.EnvironmentVariables dependency-version: 5.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: azure - dependency-name: Microsoft.Extensions.Configuration.UserSecrets dependency-version: 5.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: azure - dependency-name: Microsoft.Extensions.DependencyInjection dependency-version: 5.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: azure - dependency-name: Microsoft.Extensions.Options.ConfigurationExtensions dependency-version: 5.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: azure ... Signed-off-by: dependabot[bot] <support@github.com>
JQ dependency should exclude contentFiles Since we compile the JQ.cs type in our package itself, we don't need to make that a transitive dep for consumers of our package. If they want to access the JQ type themselves, they'd need to install JQ explicitly. This is more aligned with the intended usage of the JQ package.
Clarify license in readme for commercial use Set the right license expression to match repo license.
PreviousNext