Bump the nuget-safe group with 15 updates - #132
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps Azure.Core from 1.52.0 to 1.62.0 Bumps CSharpier.MsBuild from 1.2.6 to 1.3.0 Bumps Microsoft.AspNetCore.Mvc.NewtonsoftJson from 10.0.5 to 10.0.11 Bumps Microsoft.AspNetCore.SpaServices.Extensions from 10.0.5 to 10.0.11 Bumps Microsoft.Extensions.Caching.Memory from 10.0.2 to 10.0.11 Bumps Microsoft.Extensions.Http from 10.0.2 to 10.0.11 Bumps Microsoft.OpenApi from 2.7.5 to 2.12.2 Bumps Microsoft.PowerPlatform.Dataverse.Client from 1.2.10 to 1.2.26 Bumps Microsoft.PowerPlatform.Dataverse.Client.Dynamics from 1.2.10 to 1.2.26 Bumps Serilog from 4.3.1 to 4.4.0 Bumps Swashbuckle.AspNetCore from 10.1.7 to 10.2.3 Bumps Swashbuckle.AspNetCore.Swagger from 10.1.7 to 10.2.3 Bumps Swashbuckle.AspNetCore.SwaggerUI from 10.1.7 to 10.2.3 Bumps System.Security.Cryptography.Pkcs from 10.0.10 to 10.0.11 Bumps System.Security.Cryptography.Xml from 10.0.10 to 10.0.11 --- updated-dependencies: - dependency-name: CSharpier.MsBuild dependency-version: 1.3.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-safe - dependency-name: Microsoft.Extensions.Caching.Memory dependency-version: 10.0.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-safe - dependency-name: Microsoft.Extensions.Http dependency-version: 10.0.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-safe - dependency-name: Microsoft.PowerPlatform.Dataverse.Client dependency-version: 1.2.26 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-safe - dependency-name: Microsoft.PowerPlatform.Dataverse.Client.Dynamics dependency-version: 1.2.26 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-safe - dependency-name: System.Security.Cryptography.Pkcs dependency-version: 10.0.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-safe - dependency-name: System.Security.Cryptography.Xml dependency-version: 10.0.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-safe - dependency-name: Azure.Core dependency-version: 1.62.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-safe - dependency-name: CSharpier.MsBuild dependency-version: 1.3.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-safe - dependency-name: CSharpier.MsBuild dependency-version: 1.3.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-safe - dependency-name: Microsoft.AspNetCore.Mvc.NewtonsoftJson dependency-version: 10.0.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-safe - dependency-name: Microsoft.AspNetCore.SpaServices.Extensions dependency-version: 10.0.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-safe - dependency-name: Microsoft.Extensions.Caching.Memory dependency-version: 10.0.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-safe - dependency-name: Microsoft.Extensions.Http dependency-version: 10.0.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-safe - dependency-name: Microsoft.OpenApi dependency-version: 2.12.2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-safe - dependency-name: Microsoft.PowerPlatform.Dataverse.Client dependency-version: 1.2.26 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-safe - dependency-name: Microsoft.PowerPlatform.Dataverse.Client.Dynamics dependency-version: 1.2.26 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-safe - dependency-name: Serilog dependency-version: 4.4.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-safe - dependency-name: Swashbuckle.AspNetCore dependency-version: 10.2.3 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-safe - dependency-name: Swashbuckle.AspNetCore.Swagger dependency-version: 10.2.3 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-safe - dependency-name: Swashbuckle.AspNetCore.SwaggerUI dependency-version: 10.2.3 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-safe - dependency-name: System.Security.Cryptography.Pkcs dependency-version: 10.0.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-safe - dependency-name: System.Security.Cryptography.Xml dependency-version: 10.0.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-safe ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
|
Superseded by #148. |
dependabot
Bot
deleted the
dependabot/nuget/Database/nuget-safe-9f62b15d1b
branch
October 1, 2026 11:45
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Updated Azure.Core from 1.52.0 to 1.62.0.
Release notes
Sourced from Azure.Core's releases.
1.62.0
1.62.0 (2026-08-20)
Features Added
SCME0002)AzureCredentialResolver.Defaultpublic static property so standalone callers can share the process-wide credential cache used by DI-resolved paths.AzureCredentialResolvernow resolves everyChainedTokenCredentialSources[]entry through the active resolver chain, so any registeredCredentialResolver(built-in, broker, or third-party) can claim or override an entry. Entries are constructed as chained, so transient failures surface asCredentialUnavailableExceptionand the chain falls through.Breaking Changes
AzureCredentialResolvernow resolves a top-level single source (e.g.CredentialSource: AzureCliCredential) to the concrete credential type (AzureCliCredential) rather than aDefaultAzureCredentialwrapper. Construction is unchanged (it uses the sameDefaultAzureCredentialFactoryhelpers) — only the returned type differs; callers usingCredentialSettings.TokenProvideras aTokenCredentialare unaffected.AzureCredentialResolverno longer claims top-levelBrokerCredentialsections (canonical name orbrokeralias); they now requireBrokerCredentialResolverfromAzure.Identity.Broker1.7.0+ (e.g. viaAddBrokerCredentialResolver()).BrokerCredentialentries nested inside aChainedTokenCredentialcontinue to resolve. Note: ifBrokerCredentialResolverfromAzure.Identity.Broker1.7.0 is registered ahead ofAzureCredentialResolver, a nestedBrokerCredentialentry is currently built as non-chained, so it may surfaceAuthenticationFailedExceptionand abort the chain instead of falling through to the next entry. Without a broker resolver registered, the built-in chain path builds the broker entry as chained (correct fall-through). A futureAzure.Identity.Brokerrelease will make its resolver honor chained semantics for nested entries.1.61.0
1.61.0 (2026-07-30)
Features Added
AzureAuthorityHosts.AzureBleuCloud(https://login.sovcloud-identity.fr/), the Microsoft Entra authority host for Bleu Cloud, the national partner cloud for France. Interactive credentials'Authenticatemethods now also resolve the default Azure Resource Manager scope for Bleu Cloud.Bugs Fixed
LoggedContentSizeLimitwas not applied. The logging policy now logs only the bytes that were read. (#61399)RequestFailedExceptioncould throw a secondaryArgumentNullExceptionwhile formatting a failed response that had a text content-type header but an empty body, masking the actual service failure. The exception now preserves the original HTTP status, reason phrase, and headers, and no longer formats empty response content.AzureCliCredentialto not pass both--tenantand--subscriptionflags to the Azure CLI, as the CLI rejects this combination. When a tenant is requested (for example, via challenge-based authentication) it now takes precedence and--subscriptionis omitted;--subscriptionis used only when no tenant is requested. (#58949)Other Changes
azure-deprecatingto the default list of allowed (non-redacted) headers inDiagnosticsOptionsto support deprecating behavior notification.Commits viewable in compare view.
Updated CSharpier.MsBuild from 1.2.6 to 1.3.0.
Release notes
Sourced from CSharpier.MsBuild's releases.
1.3.0
1.3.0
Breaking Changes
Change xml formatting to return error when it runs into syntax error so it is consistent with c# #1854
Previously CSharpier treated an invalid xml file as a warning instead of an error. This was inconsistent with how it treated c# files.
Invalid c# or xml files are not treated as errors.
The
--compilation-errors-as-warningsargument has been renamed to--syntax-errors-as-warningsand can be used to return warnings instead of errors when encountering invalid files.What's Changed
Feature: Configurable whitespace handling for xml #1790
CSharpier now supports two types of xml whitespace formatting strict or ignore.
By default all xml except
xamloraxamlis treated as strict whitespace. See detailsFeature: Move closing bracket for xml elements to the same line. #1598
With strict xml whitespace handling, csharpier now keeps the closing bracket for an element on the same line instead of breaking it to a new line.
Feature: Support for csharpier-ignore with XML formatter #1788
CSharpier now supports
csharpier-ignorein xml files. See detailsFeature: Add MSBuild transitive and multi-target support #1833
CSharpier.MSBuild can now work as a transitive dependency.
Feature: allow checking formatting with cache #1830
The
csharpier checkcommand now supports a--use-cacheoption.Feature: remove dependency on Microsoft.AspNetCore.App #1508
Previously CSharpier required that Microsoft.AspNetCore.App be installed. CSharpier has been modified to use an HttpListener when it is run using
serverto remove the need for this dependency.Fix: csharpier-ignore comment removes linespaces before block #1867
CSharpier was removing blank lines before csharpier-ignore comments in some cases