chore(deps): update nuget#722
Open
projectorigin-renovate[bot] wants to merge 1 commit into
Open
Conversation
562980c to
f64f12a
Compare
1c40cb4 to
cb02d24
Compare
9da6e26 to
cdf6acf
Compare
07f89d0 to
e3c5b91
Compare
62a89ae to
5a3b0ca
Compare
580429d to
88eb80d
Compare
31c69cf to
67ea843
Compare
12bfacd to
f749d32
Compare
4a07afc to
1d95e83
Compare
54406ad to
d6c70a8
Compare
c82646c to
f80584c
Compare
f80584c to
f26fcb2
Compare
77e774c to
bc6fe3d
Compare
bc6fe3d to
18b10f3
Compare
091dc82 to
b28b173
Compare
Contributor
Author
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
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.
This PR contains the following updates:
2.1.66→2.1.792.71.0→2.80.08.5.4→8.5.108.5.4→8.5.109.0.10→9.0.179.0.10→9.0.179.0.10→9.0.179.0.10→9.0.179.0.10→9.0.179.0.10→9.0.174.0.0→4.10.018.0.0→18.6.09.0.4→9.0.59.0.4→9.0.51.13.1→1.16.01.13.1→1.16.01.13.1→1.16.01.12.0→1.15.21.12.0→1.15.11.12.0→1.15.14.7.0→4.12.04.7.0→4.12.031.0.2→31.12.51.14.0→1.25.06.0.3→6.1.52.71.0→2.80.0Release Notes
DapperLib/Dapper (Dapper)
v2.1.79Compare Source
What's Changed
New Contributors
Full Changelog: DapperLib/Dapper@2.1.72...2.1.79
v2.1.72Compare Source
What's Changed
New Contributors
Full Changelog: DapperLib/Dapper@2.1.66...2.1.72
grpc/grpc-dotnet (Grpc.AspNetCore)
v2.80.0What's Changed
New Contributors
Full Changelog: grpc/grpc-dotnet@v2.76.0...v2.80.0
v2.76.0What's Changed
New Contributors
Full Changelog: grpc/grpc-dotnet@v2.71.0...v2.76.0
AzureAD/microsoft-identity-web (Microsoft.Identity.Web)
v4.10.0Compare Source
New features
WithExtraBodyParametersfluent API for attaching extra body parameters to token acquisition requests. See #3819.IConfidentialClientApplicationProviderextensibility interface andCachePartitionKeysupport for silent token acquisition. See #3822.Bug fixes
Authorityvalues with a clearer exception, steering users to useInstance+TenantIdinstead. See #3805.Behavior changes
Dependencies updates
Microsoft.Kiota.Abstractionsto 1.22.0 for GraphServiceClient. See #3817.uuidand@azure/msal-nodein SidecarAdapter TypeScript test app. See #3826.qsin SidecarAdapter TypeScript test app. See #3829.v4.9.0Compare Source
New features
Sidecar:AllowOverridesconfiguration section provides explicit, per-route control over whetheroptionsOverride.*query-string parameters are honored. Authenticated routes default to allowing overrides (preserving existing behavior); unauthenticated routes default to rejecting them.optionsOverride.BaseUrlis unconditionally rejected on all routes as a hardening measure. See #3794.Bug fixes
AccountController.Challengeredirect URI validation to reject percent-encoded protocol-relative bypasses (%2F%2F,%5C%2F, etc.) that could be decoded by misconfigured reverse proxies. See #3792.Behavior changes
DownstreamApiOptions.ExtraHeaderParameterswhose names match reserved HTTP headers (Authorization,Host,Content-Length,Proxy-Authorization,Sec-*,Proxy-*, etc.) or duplicate a header the library already set are now silently skipped. A warning-level log entry (ReservedHeaderIgnored/DuplicateHeaderIgnored) is emitted so operators can spot misconfigurations. No exception is thrown. See #3793.Dependencies updates
Microsoft.Extensions.DependencyInjection.Abstractions8.0.2 on non-framework-coupled TFMs (net462, net472, netstandard2.0). This caused aCS0433type collision with the previously-pinnedMicrosoft.Extensions.DependencyInjection2.1.0. The entireMicrosoft.Extensions.*stack on these older TFMs has been bumped to 8.x for consistency. If your application targets net462, net472, or netstandard2.0, your resolvedMicrosoft.Extensions.*versions will increase (e.g.,Extensions.Http3.1.3 → 8.0.0,Extensions.DependencyInjection2.1.0 → 8.0.0,Extensions.Caching.Memory2.1.0/6.0.2 → 8.0.1). Applications already targeting net8.0+ are unaffected. See #3787.System.Text.Json8.0.5 → 8.0.6 (CVE-2024-43485). See #3787.Microsoft.AspNetCore.DataProtectionto 10.0.7 for CVE fix on net10.0. See #3796.OpenTelemetry.Exporter.OpenTelemetryProtocol1.14.0 → 1.15.3. See #3788.v4.8.0Compare Source
New features
DownstreamApi. When protocol is set to MTLS, the configured certificate is attached to the request without an authorization header. See #3747.MicrosoftIdentityMessageHandler. See #3743.Bug fixes
MergedOptionscausing sporadic "No ClientId was specified" errors under concurrentGraphServiceClientusage. See #3760.CredentialsProviderDI lifetime mismatch causing startup crash in Development mode when usingAddMicrosoftIdentityWebApi(). See #3783.Behavior changes
/MicrosoftIdentity/Account/Challenge— redirect URI validation. TheredirectUriquery-string parameter is now validated. Accepted values:/home,/counter?tab=1) — unchanged behavior.AuthenticationProperties.RedirectUri. This preserves the canonical[AuthorizeForScopes]/MsalUiRequiredExceptionstep-up consent flow, which goes throughMicrosoftIdentityConsentAndConditionalAccessHandler.ChallengeUser()and passesNavigationManager.Uri(always absolute) for Blazor Server, or an absolute request URL for Razor Pages / MVC.//host, empty, ornull) falls back to~/.#section) are dropped when a same-origin absolute URL is coerced. If a Blazor Server page depends on a fragment being preserved across step-up consent, pass a relative path explicitly rather than relying onNavigationManager.Uri.app.UseForwardedHeaders(new ForwardedHeadersOptions { ForwardedHeaders = ForwardedHeaders.XForwardedProto | ForwardedHeaders.XForwardedHost })beforeUseAuthentication(). Without it,Request.Scheme/Request.Hostreflect the internal container/pod hostname, the same-origin check fails for the externalNavigationManager.Uri, and step-up lands the user on/rather than the original page.Blazor
MapGroup(...).MapLoginAndLogout()—/logoutendpoint. The generatedPOST /logoutendpoint now (a) requires authentication (RequireAuthorization()) and (b) requires an antiforgery token (the previousDisableAntiforgery()opt-out has been removed). UX and integration implications:SignOutLink/LogInOrOutalready include the antiforgery token and continue to work without code changes.fetch/XMLHttpRequestto/logoutmust now include the antiforgery token. Obtain it viaIAntiforgery.GetAndStoreTokens(context).RequestTokenand send it in the request header configured byAddAntiforgery(options => options.HeaderName = "...")(defaultRequestVerificationToken) or as the configured form field.ReturnUrlform value is now treated as strictly local: any non-local value (absolute URL, protocol-relative,/\host, etc.) is coerced to/. Apps that previously passed an absolute URL should switch to a relative path.RequireAuthorization()) rather than seeing a silent no-op. This is a minor change from previous behavior; the happy path (authenticated user clicking logout) is unchanged.Microsoft.Authentication.WebAssembly.Msal/ the/authentication/logoutJS interop path, not by POSTing to the server-side/logoutendpoint, so no client code changes are needed.AuthenticationStateProvider/SignOutAsyncis unaffected. The new gate only applies to direct HTTP POSTs to/logout. Components that callAuthenticationStateProvider.GetAuthenticationStateAsync()or sign out through the scheme handler continue to work unchanged.IAntiforgeryfrom request services (not via endpoint metadata / middleware coupling). This means the/logoutendpoint works correctly on every pipeline shape: (a) minimal API with bothAddAntiforgery()andUseAntiforgery()wired — token is validated by middleware and re-checked by the handler (idempotent); (b) MVC / Razor Pages hosts that callAddControllersWithViews()orAddRazorPages()(which transitively registerIAntiforgery) but do not callUseAntiforgery()— the handler validates the token directly; (c) hosts that reuseMapLoginAndLogoutwithout any antiforgery configuration — the handler skips validation andRequireAuthorization()+ cookieSameSite=Laxremain the CSRF gate, matching pre-4.8.0 behavior. For scenario (c), a single warning is logged at endpoint map time recommending thatAddAntiforgery()be configured./MicrosoftIdentity/Account/Challenge—%2f/%5cdefense-in-depth. In addition to the path-and-query re-check for protocol-relative shapes (//host,/\host),redirectUrivalues whose path begins with/%2f,/%5c,/%2F, or/%5Care now rejected and coerced to~/. Browsers per RFC 3986 treat these as literal path characters (a direct hit yields a 404), so this change does not affect legitimate deep-links. It guards against misconfigured reverse proxies (NGINX, IIS ARR, F5) that can decode%2f→/while rewritingLocationheaders, which would otherwise reopen the protocol-relative bypass after the proxy pass.Dependencies updates
Documentation
v4.7.0Compare Source
Bug fixes
Certificateextension method inCredentialDescriptionwas reverted to normal property.) See #3767.v4.6.0Compare Source
New features
Dependencies updates
v4.5.0Compare Source
New features
Dependencies updates
v4.4.0Compare Source
New features
WithClientClaimsflow for token acquisition. See #3623.OnBeforeTokenAcquisitionForOnBehalfOfevent. See #3680.Bug fixes
InvalidOperationExceptionwith actionable message when a custom credential is not registered. See #3626.InvokeOnBeforeTokenAcquisitionForOnBehalfOfAsync. See #3717.OnBeforeTokenAcquisitionForOnBehalfOfto constructClaimsPrincipalfrom token. See #3714.SendX5Cto MSAL. See #3671.Dependencies updates
qsin/tests/DevApps/SidecarAdapter/typescript. See #3725.Documentation
CertificatelessOptions.ManagedIdentityClientId. See #3667.Fundamentals
CertificatesObserverTests. See #3687.v4.3.0Compare Source
New features
Dependencies updates
Documentation
v4.2.0Compare Source
New features
AddMicrosoftIdentityMessageHandlerextension methods forIHttpClientBuilder. See #3649 for details.Bug fixes
ForAgentIdentityhardcoded 'AzureAd'ConfigurationSectionto respectAuthenticationOptionsName. See #3635 for details.GetTokenAcquirerto propagateMicrosoftEntraApplicationOptionsproperties. See #3651 for details.Dependencies updates
Fundamentals
v4.1.1Compare Source
Bug fixes
New features
Fundamentals
v4.1.0Compare Source
=========
New features
Dependencies updates
Entra ID SDK sidecar
Documentation
Fundamentals
v4.0.1Compare Source
=========
Bugs fixes
Fundamentals
Entra ID SDK sidecar
microsoft/vstest (Microsoft.NET.Test.Sdk)
v18.6.0What's Changed
Changes to tests and infra
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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 has been generated by Mend Renovate.