Skip to content

Bump Azure.Identity and 6 others#253

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/backend/Orqentis.AI/nuget-minor-patch-14e9fb895b
Closed

Bump Azure.Identity and 6 others#253
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/backend/Orqentis.AI/nuget-minor-patch-14e9fb895b

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 13, 2026

Copy link
Copy Markdown

Pinned Azure.Identity at 1.21.0.

Release notes

Sourced from Azure.Identity's releases.

1.18.0-beta.1

1.18.0-beta.1 (2026-06-30)

Features Added

  • Upgraded api-version to 2026-04-15-preview. Tag detail available at https://github.com/Azure/azure-rest-api-specs/blob/main/specification/netapp/resource-manager/Microsoft.NetApp/NetApp/readme.md.
  • Added first-class Active Directory configuration resource support, including NetAppActiveDirectoryConfigResource, NetAppActiveDirectoryConfigCollection, and related create, update, get, and list operations.
  • Added first-class Elastic resource support, including NetAppElasticAccountResource, NetAppElasticCapacityPoolResource, NetAppElasticVolumeResource, NetAppElasticSnapshotPolicyResource, NetAppElasticSnapshotResource, NetAppElasticBackupVaultResource, NetAppElasticBackupPolicyResource, and NetAppElasticBackupResource, together with their related models and operations.
  • Added account-level LDAP and Entra ID configuration models, including LdapConfiguration, LdapConfigurationPatch, BindPasswordAkvConfig, BindPasswordAkvConfigPatch, EntraIdConfig, and EntraIdConfigPatch.
  • Added new supporting Elastic and NetApp models and enums, including CheckElasticResourceAvailabilityResult, CheckElasticVolumeFilePathAvailabilityContent, BreakthroughMode, BindAuthenticationLevel, LargeVolumeType, and related Elastic policy, encryption, protocol, snapshot, and availability types.

Breaking Changes

  • Preview account configuration and patch APIs were reshaped to align with the 2026-04-15-preview service contract. Code using preview-only NetAppAccountPatch, LDAP, Entra ID, Active Directory configuration, or Elastic resource types may need to be updated.

Other Changes

  • Refreshed generated models, resource operations, and samples to align with the latest preview service definitions.

1.17.0

1.17.0 (2026-06-23)

Features Added

Breaking Changes

  • Cache operation return type changes: Method NetAppCacheResource.PoolChange() now returns Operation<NetAppCacheResource> instead of Operation
  • Cache operation return type changes: Method NetAppCacheResource.ResetSmbPassword() now returns Operation<NetAppCacheResource> instead of Operation
  • Some legacy Elastic and Active Directory compatibility APIs are now runtime compatibility stubs. These members are kept for source compatibility but throw NotSupportedException when invoked.
  • Impacted compatibility areas include Elastic compatibility APIs, NetAppActiveDirectoryConfig*, EntraId*, CheckElastic*, and LdapConfiguration related compatibility types.

1.16.1

1.16.1 (2026-06-30)

Bugs Fixed

  • Fixed duplicate public APIs with different casing that were accidentally introduced during TypeSpec migration, and restored affected model properties to their previous GA API shape.

1.16.0

1.16.0 (2026-06-22)

Features Added

  • Upgraded api-version to 2025-07-01.

Breaking Changes

  • This is the first GA release generated from TypeSpec. Some obsolete APIs were added as migration compatibility shims and are not supported by the TypeSpec-generated SDK; please review obsolete messages for replacement guidance.

Other Changes

  • Migrated code generation from AutoRest to TypeSpec.

1.15.0

1.15.0 (2026-06-29)

Features Added

  • Upgraded Compute API version from 2025-04-01 to 2025-11-01.

Breaking Changes

  • This is the first GA release generated from TypeSpec. Some obsolete APIs were added as migration compatibility shims and are not supported by the TypeSpec-generated SDK; please review obsolete messages for replacement guidance.
  • Cloud Services (classic) APIs are no longer supported by the TypeSpec-generated SDK and are preserved only as obsolete compatibility shims.

Other Changes

  • Migrated code generation from AutoRest to TypeSpec.

Commits viewable in compare view.

Pinned Azure.Storage.Files.DataLake at 12.27.1.

Release notes

Sourced from Azure.Storage.Files.DataLake's releases.

12.27.1

12.27.1 (2026-06-23)

Bugs Fixed

  • Fixed an issue where the GenerateSasUri and GenerateUserDelegationSasUri convenience methods on Data Lake clients did not honor the RequestHeaders and RequestQueryParameters properties, and where GenerateUserDelegationSasUri did not honor DelegatedUserObjectId, set on the supplied DataLakeSasBuilder.

Commits viewable in compare view.

Pinned Microsoft.Data.SqlClient at 5.2.3.

Release notes

Sourced from Microsoft.Data.SqlClient's releases.

5.2.3

This update brings the following changes since the 5.2.2 release:

Fixed

  • Fixed possible NullPointerException during socket receive (PR #​3284)
  • Fixed inconsistencies between source and reference projects (PR #​3124)
  • Adjusted retry logic to allow errors with negative numbers to be considered transient (PR #​3185)

Changed

Commits viewable in compare view.

Updated Microsoft.Extensions.Logging.Abstractions from 8.0.2 to 8.0.3.

Release notes

Sourced from Microsoft.Extensions.Logging.Abstractions's releases.

8.0.3

Release

Commits viewable in compare view.

Pinned NJsonSchema at 11.6.1.

Release notes

Sourced from NJsonSchema's releases.

11.6.1

[!IMPORTANT]
v11.6.0 should not be used — it introduced a regression that caused required T? / [JsonRequired] T? properties to incorrectly lose their nullability and gain a spurious MinLength=1 on strings. Please upgrade directly from v11.5.x to v11.6.1.

Corrections to v11.6.0

v11.6.0 added support for the C# 11 required keyword and [JsonRequired] in schema generation (#​1908), but folded them into the same bucket as DataAnnotations [Required] — which conflated three distinct concepts:

  • Presence (belongs in schema's required array): required keyword, [JsonRequired], [Required], [DataMember(IsRequired=true)], Newtonsoft Required.Always/AllowNull
  • Non-null value (suppresses nullable): [Required] only (plus Newtonsoft Required.Always/DisallowNull for runtime correctness)
  • Non-empty string (MinLength=1 on strings): [Required] only (unless AllowEmptyStrings=true)

v11.6.1 (#​1919) restores the correct separation. The required keyword and [JsonRequired] are now presence-only markers — they add the property to the schema's required array without suppressing nullability or adding MinLength=1.

Behavioral deltas vs v11.6.0 (all restoring correctness)

C# declaration v11.6.0 (broken) v11.6.1
required string? nullable: false, MinLength: 1 nullable: true, no MinLength
required string MinLength: 1 no MinLength
[JsonRequired] string? nullable: false, MinLength: 1 nullable: true, no MinLength
[JsonRequired] string MinLength: 1 no MinLength

[Required], [JsonProperty(Required=*)], and [DataMember(IsRequired=true)] semantics are unchanged across v11.5.x / v11.6.0 / v11.6.1.

Downstream impact

The v11.6.0 regression surfaced in NSwag as NSwag#​5359: TypeScript clients generated from required T? DTO properties silently lost their | null, removing null-safety for fields the server can legitimately return as null. v11.6.1 fixes this. A matching NSwag release is required to pick up the fix.

What's Changed

New Contributors

Full Changelog: RicoSuter/NJsonSchema@v11.6.0...v11.6.1

11.6.0

[!CAUTION]
Do not use this release — upgrade to v11.6.1 or later.

v11.6.0 introduced a regression in the handling of the C# required keyword and [JsonRequired]: required T? / [JsonRequired] T? properties incorrectly lost their nullability and gained a spurious MinLength=1 on strings. This broke downstream client generation — see NSwag#​5359. Fixed in v11.6.1 (#​1919).


Potentially breaking changes

  • C# 11 required keyword now recognized as required: Properties using the C# 11 required keyword (RequiredMemberAttribute / JsonRequiredAttribute) are now correctly treated as required in schema generation and code output. Previously these were incorrectly treated as optional (Required.Default). This changes generated code: such properties now get Required.Always, [Required] attribute, and the required modifier when UseRequiredKeyword is enabled. (#​1908)
  • Both JsonStringEnumMemberName and EnumMember attributes are now emitted for enum members when using System.Text.Json, for compatibility with NSwag's reflection-based URL parameter serialization. (#​1905)
  • $schema version preserved in ToJson() instead of forcing draft-04. If you relied on the output always being draft-04, this may affect you. (#​1881)
  • patternProperties validation now correctly applies to all matching properties, not just the first. (#​1898)
  • MinLength no longer incorrectly applied to DateTime, DateTimeOffset, DateOnly, TimeOnly properties. (#​1900)

What's Changed

New Contributors

Full Changelog: RicoSuter/NJsonSchema@v11.5.2...v11.6.0

11.5.2

What's Changed

New Contributors

Full Changelog: RicoSuter/NJsonSchema@v11.5.1...v11.5.2

11.5.1

What's Changed

New Contributors

Full Changelog: RicoSuter/NJsonSchema@v11.5.0...v11.5.1

11.5.0

What's Changed

Breaking changes:

Others:

Full Changelog: RicoSuter/NJsonSchema@v11.4.0...v11.5.0

11.4.0

What's Changed

New Contributors

Full Changelog: RicoSuter/NJsonSchema@v11.3.2...v11.4.0

11.3.2

What's Changed

Full Changelog: RicoSuter/NJsonSchema@v11.3.1...v11.3.2

11.3.1

What's Changed

Full Changelog: RicoSuter/NJsonSchema@v11.3.0...v11.3.1

11.3.0

What's Changed

New Contributors

Full Changelog: RicoSuter/NJsonSchema@v11.2.0...v11.3.0

11.2.0

What's Changed

New Contributors

Commits viewable in compare view.

Pinned NJsonSchema.Yaml at 11.6.1.

Release notes

Sourced from NJsonSchema.Yaml's releases.

11.6.1

[!IMPORTANT]
v11.6.0 should not be used — it introduced a regression that caused required T? / [JsonRequired] T? properties to incorrectly lose their nullability and gain a spurious MinLength=1 on strings. Please upgrade directly from v11.5.x to v11.6.1.

Corrections to v11.6.0

v11.6.0 added support for the C# 11 required keyword and [JsonRequired] in schema generation (#​1908), but folded them into the same bucket as DataAnnotations [Required] — which conflated three distinct concepts:

  • Presence (belongs in schema's required array): required keyword, [JsonRequired], [Required], [DataMember(IsRequired=true)], Newtonsoft Required.Always/AllowNull
  • Non-null value (suppresses nullable): [Required] only (plus Newtonsoft Required.Always/DisallowNull for runtime correctness)
  • Non-empty string (MinLength=1 on strings): [Required] only (unless AllowEmptyStrings=true)

v11.6.1 (#​1919) restores the correct separation. The required keyword and [JsonRequired] are now presence-only markers — they add the property to the schema's required array without suppressing nullability or adding MinLength=1.

Behavioral deltas vs v11.6.0 (all restoring correctness)

C# declaration v11.6.0 (broken) v11.6.1
required string? nullable: false, MinLength: 1 nullable: true, no MinLength
required string MinLength: 1 no MinLength
[JsonRequired] string? nullable: false, MinLength: 1 nullable: true, no MinLength
[JsonRequired] string MinLength: 1 no MinLength

[Required], [JsonProperty(Required=*)], and [DataMember(IsRequired=true)] semantics are unchanged across v11.5.x / v11.6.0 / v11.6.1.

Downstream impact

The v11.6.0 regression surfaced in NSwag as NSwag#​5359: TypeScript clients generated from required T? DTO properties silently lost their | null, removing null-safety for fields the server can legitimately return as null. v11.6.1 fixes this. A matching NSwag release is required to pick up the fix.

What's Changed

New Contributors

Full Changelog: RicoSuter/NJsonSchema@v11.6.0...v11.6.1

11.6.0

[!CAUTION]
Do not use this release — upgrade to v11.6.1 or later.

v11.6.0 introduced a regression in the handling of the C# required keyword and [JsonRequired]: required T? / [JsonRequired] T? properties incorrectly lost their nullability and gained a spurious MinLength=1 on strings. This broke downstream client generation — see NSwag#​5359. Fixed in v11.6.1 (#​1919).


Potentially breaking changes

  • C# 11 required keyword now recognized as required: Properties using the C# 11 required keyword (RequiredMemberAttribute / JsonRequiredAttribute) are now correctly treated as required in schema generation and code output. Previously these were incorrectly treated as optional (Required.Default). This changes generated code: such properties now get Required.Always, [Required] attribute, and the required modifier when UseRequiredKeyword is enabled. (#​1908)
  • Both JsonStringEnumMemberName and EnumMember attributes are now emitted for enum members when using System.Text.Json, for compatibility with NSwag's reflection-based URL parameter serialization. (#​1905)
  • $schema version preserved in ToJson() instead of forcing draft-04. If you relied on the output always being draft-04, this may affect you. (#​1881)
  • patternProperties validation now correctly applies to all matching properties, not just the first. (#​1898)
  • MinLength no longer incorrectly applied to DateTime, DateTimeOffset, DateOnly, TimeOnly properties. (#​1900)

What's Changed

New Contributors

Full Changelog: RicoSuter/NJsonSchema@v11.5.2...v11.6.0

11.5.2

What's Changed

New Contributors

Full Changelog: RicoSuter/NJsonSchema@v11.5.1...v11.5.2

11.5.1

What's Changed

New Contributors

Full Changelog: RicoSuter/NJsonSchema@v11.5.0...v11.5.1

11.5.0

What's Changed

Breaking changes:

Others:

Full Changelog: RicoSuter/NJsonSchema@v11.4.0...v11.5.0

11.4.0

What's Changed

New Contributors

Full Changelog: RicoSuter/NJsonSchema@v11.3.2...v11.4.0

11.3.2

What's Changed

Full Changelog: RicoSuter/NJsonSchema@v11.3.1...v11.3.2

11.3.1

What's Changed

Full Changelog: RicoSuter/NJsonSchema@v11.3.0...v11.3.1

11.3.0

What's Changed

New Contributors

Full Changelog: RicoSuter/NJsonSchema@v11.2.0...v11.3.0

11.2.0

What's Changed

New Contributors

Commits viewable in compare view.

Updated Polly from 8.5.0 to 8.7.0.

Release notes

Sourced from Polly's releases.

8.7.0

Highlights

What's Changed

New Contributors

Full Changelog: App-vNext/Polly@8.6.6...8.7.0

8.6.6

Highlights

What's Changed

New Contributors

Full Changelog: App-vNext/Polly@8.6.5...8.6.6

8.6.5

What's Changed

Full Changelog: App-vNext/Polly@8.6.4...8.6.5

8.6.4

What's Changed

New Contributors

Full Changelog: App-vNext/Polly@8.6.3...8.6.4

8.6.3

What's Changed

New Contributors

Full Changelog: App-vNext/Polly@8.6.2...8.6.3

8.6.2

What's Changed

New Contributors

Full Changelog: App-vNext/Polly@8.6.1...8.6.2

8.6.1

What's Changed

New Contributors

Full Changelog: App-vNext/Polly@8.6.0...8.6.1

8.6.0

What's Changed

New Contributors

Full Changelog: App-vNext/Polly@8.5.2...8.6.0

8.5.2

What's Changed

New Contributors

Full Changelog: App-vNext/Polly@8.5.1...8.5.2

8.5.1

What's Changed

New Contributors

Full Changelog: App-vNext/Polly@8.5.0...8.5.1

Commits viewable in compare view.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it y...

Description has been truncated

Bumps Azure.Identity from 1.13.1 to 1.21.0
Bumps Azure.Storage.Files.DataLake from 12.21.0 to 12.27.1
Bumps Microsoft.Data.SqlClient from 5.2.2 to 5.2.3
Bumps Microsoft.Extensions.Logging.Abstractions from 8.0.2 to 8.0.3
Bumps NJsonSchema from 11.1.0 to 11.6.1
Bumps NJsonSchema.Yaml from 11.1.0 to 11.6.1
Bumps Polly from 8.5.0 to 8.7.0

---
updated-dependencies:
- dependency-name: Azure.Identity
  dependency-version: 1.21.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-minor-patch
- dependency-name: Azure.Storage.Files.DataLake
  dependency-version: 12.27.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-minor-patch
- dependency-name: Microsoft.Data.SqlClient
  dependency-version: 5.2.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-minor-patch
- dependency-name: Microsoft.Extensions.Logging.Abstractions
  dependency-version: 8.0.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-minor-patch
- dependency-name: NJsonSchema
  dependency-version: 11.6.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-minor-patch
- dependency-name: NJsonSchema.Yaml
  dependency-version: 11.6.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-minor-patch
- dependency-name: Polly
  dependency-version: 8.7.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-minor-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Jul 13, 2026

Copy link
Copy Markdown
Author

Labels

The following labels could not be found: auto, dependencies. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot
dependabot Bot requested a review from mjtpena as a code owner July 13, 2026 23:38
@dependabot @github

dependabot Bot commented on behalf of github Jul 13, 2026

Copy link
Copy Markdown
Author

Superseded by #254.

@dependabot dependabot Bot closed this Jul 13, 2026
@dependabot
dependabot Bot deleted the dependabot/nuget/backend/Orqentis.AI/nuget-minor-patch-14e9fb895b branch July 13, 2026 23:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants