Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 24, 2025

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
Microsoft.AspNetCore.Authentication.JwtBearer (source) 8.0.10 -> 10.0.0 age confidence
Microsoft.AspNetCore.DataProtection (source) 8.0.10 -> 10.0.0 age confidence
Microsoft.AspNetCore.Mvc.Testing (source) 8.0.10 -> 10.0.0 age confidence
Microsoft.AspNetCore.SignalR.Protocols.MessagePack (source) 8.0.8 -> 10.0.0 age confidence
Microsoft.AspNetCore.SignalR.StackExchangeRedis (source) 8.0.8 -> 10.0.0 age confidence
Microsoft.Extensions.Caching.Memory (source) 8.0.1 -> 10.0.0 age confidence
Microsoft.Extensions.Caching.SqlServer (source) 8.0.10 -> 10.0.0 age confidence
Microsoft.Extensions.Caching.StackExchangeRedis (source) 8.0.10 -> 10.0.0 age confidence
Microsoft.Extensions.Configuration (source) 8.0.0 -> 10.0.0 age confidence
Microsoft.Extensions.Configuration.EnvironmentVariables (source) 8.0.0 -> 10.0.0 age confidence
Microsoft.Extensions.Configuration.UserSecrets (source) 8.0.0 -> 10.0.0 age confidence
Microsoft.Extensions.DependencyInjection (source) 8.0.1 -> 10.0.0 age confidence
Microsoft.Extensions.DependencyInjection.Abstractions (source) 8.0.2 -> 10.0.0 age confidence
Microsoft.Extensions.Diagnostics.Testing (source) 9.3.0 -> 10.0.0 age confidence
Microsoft.Extensions.Identity.Stores (source) 8.0.10 -> 10.0.0 age confidence
Microsoft.Extensions.Logging (source) 8.0.1 -> 10.0.0 age confidence
Microsoft.Extensions.Logging.Console (source) 8.0.1 -> 10.0.0 age confidence
Microsoft.Extensions.TimeProvider.Testing (source) 8.10.0 -> 10.0.0 age confidence
System.Text.Json (source) 8.0.5 -> 10.0.0 age confidence

Release Notes

dotnet/dotnet (Microsoft.AspNetCore.Authentication.JwtBearer)

v9.0.7: .NET 9.0.7

You can build .NET 9.0 from the repository by cloning the release tag v9.0.7 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

v9.0.6: .NET 9.0.6

You can build .NET 9.0 from the repository by cloning the release tag v9.0.6 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

v9.0.5: .NET 9.0.5

You can build .NET 9.0 from the repository by cloning the release tag v9.0.5 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

v9.0.4: .NET 9.0.4

You can build .NET 9.0 from the repository by cloning the release tag v9.0.4 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

v9.0.3: .NET 9.0.3

You can build .NET 9.0 from the repository by cloning the release tag v9.0.3 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

v9.0.2: .NET 9.0.2

You can build .NET 9.0 from the repository by cloning the release tag v9.0.2 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

v9.0.1: .NET 9.0.1

You can build .NET 9.0 from the repository by cloning the release tag v9.0.1 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

v9.0.0: .NET 9.0.0

You can build .NET 9.0 from the repository by cloning the release tag v9.0.0 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

v8.0.18: .NET 8.0.18

You can build .NET 8.0 from the repository by cloning the release tag v8.0.18 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

v8.0.17: .NET 8.0.17

You can build .NET 8.0 from the repository by cloning the release tag v8.0.17 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

v8.0.16: .NET 8.0.16

You can build .NET 8.0 from the repository by cloning the release tag v8.0.16 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

v8.0.15: .NET 8.0.15

You can build .NET 8.0 from the repository by cloning the release tag v8.0.15 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

v8.0.14: .NET 8.0.14

You can build .NET 8.0 from the repository by cloning the release tag v8.0.14 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

v8.0.13: .NET 8.0.13

You can build .NET 8.0 from the repository by cloning the release tag v8.0.13 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

v8.0.12: .NET 8.0.12

You can build .NET 8.0 from the repository by cloning the release tag v8.0.12 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

v8.0.11: .NET 8.0.11

You can build .NET 8.0 from the repository by cloning the release tag v8.0.11 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

dotnet/extensions (Microsoft.Extensions.Diagnostics.Testing)

v10.0.0

What's Changed
New Contributors

Full Changelog: dotnet/extensions@v9.10.0...v10.0.0

v9.10.0

What's Changed

New Contributors

Full Changelog: dotnet/extensions@v9.9.0...v9.10.0

v9.9.0

Highlights

AI
  • Abstractions for remote MCP servers; response/approval flow support via new experimental types
  • Function approvals via new experimental types (e.g., ApprovalRequiredAIFunction, user input/approval request & response content).
  • Reasoning text streaming for OpenAI Responses ChatClient streaming.
  • AIFunction split into a base class to improve extensibility.
  • IChatReducer moved to Microsoft.Extensions.AI.Abstractions.
  • Updated to OpenAI 2.4.0 and genai standard convention 1.37.
  • Coalescing logic now treats ChatMessage.Role changes as new messages.
  • GetResponseAsync<T> now reads only the last message (bug fix).
  • OpenTelemetry ChatClient/EmbeddingGenerator logs raw additional properties (no key mangling).
  • Fixed empty annotated text chunk handling in streaming with OpenAI Assistants.
Telemetry & Diagnostics
  • HTTP diagnostics log query string params with proper redaction (emitted on url.query).
  • server.address telemetry emits host only (per OpenTelemetry semantic conventions).
  • Heuristics added to detect well-known model hosts.
  • Resource monitoring can consider Environment.CpuUsage.

New Contributors

Full Changelog: dotnet/extensions@v9.8.0...v9.9.0

v9.8.0

What's Changed

New Contributors

Full Changelog: dotnet/extensions@v9.7.0...v9.8.0

v9.7.0

What's Changed


Configuration

📅 Schedule: Branch creation - "every 2nd week starting on the 2 week of the year before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested review from a team as code owners November 24, 2025 02:50
@bitwarden-bot bitwarden-bot changed the title [deps] Auth: Update dotnet monorepo to v10 (major) [PM-28727] [deps] Auth: Update dotnet monorepo to v10 (major) Nov 24, 2025
@bitwarden-bot
Copy link

Internal tracking:

@renovate renovate bot changed the title [PM-28727] [deps] Auth: Update dotnet monorepo to v10 (major) [deps] Auth: Update dotnet monorepo to v10 (major) Nov 24, 2025
@dani-garcia
Copy link
Member

Note: This is blocked on the update of swashbuckle to v10: https://bitwarden.atlassian.net/browse/PM-28105

@renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch from e68985c to a603865 Compare November 26, 2025 19:49
@renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch from a603865 to 43db73c Compare November 28, 2025 11:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants