Repository navigation
Bump the dotnet-dependencies group with 27 updates - #41
Open
dependabot[bot] wants to merge 1 commit into
Open
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps AWSSDK.S3 from 4.0.102.3 to 4.1.0 Bumps Confluent.Kafka from 2.15.0 to 2.16.0 Bumps Dapper from 2.1.79 to 2.1.89 Bumps DocumentFormat.OpenXml from 3.3.0 to 3.5.1 Bumps Google.Apis.Auth from 1.76.0 to 1.78.0 Bumps Mapster from 10.0.12 to 10.0.14 Bumps Microsoft.AspNetCore.Authentication.JwtBearer from 10.0.11 to 10.0.15 Bumps Microsoft.AspNetCore.Identity.EntityFrameworkCore from 10.0.11 to 10.0.15 Bumps Microsoft.AspNetCore.Mvc.Testing from 10.0.11 to 10.0.15 Bumps Microsoft.AspNetCore.OpenApi from 10.0.11 to 10.0.15 Bumps Microsoft.AspNetCore.SignalR.StackExchangeRedis from 10.0.11 to 10.0.15 Bumps Microsoft.EntityFrameworkCore from 10.0.11 to 10.0.15 Bumps Microsoft.EntityFrameworkCore.Design from 10.0.11 to 10.0.15 Bumps Microsoft.EntityFrameworkCore.InMemory from 10.0.11 to 10.0.15 Bumps Microsoft.EntityFrameworkCore.Relational from 10.0.11 to 10.0.15 Bumps Microsoft.Extensions.Caching.StackExchangeRedis from 10.0.11 to 11.0.0 Bumps Microsoft.NET.Test.Sdk from 18.9.0 to 18.12.0 Bumps OpenTelemetry.Exporter.OpenTelemetryProtocol from 1.18.0 to 1.21.0 Bumps OpenTelemetry.Extensions.Hosting from 1.18.0 to 1.21.0 Bumps OpenTelemetry.Instrumentation.AspNetCore from 1.18.0 to 1.21.0 Bumps OpenTelemetry.Instrumentation.Http from 1.18.0 to 1.21.0 Bumps OpenTelemetry.Instrumentation.Runtime from 1.18.0 to 1.21.0 Bumps Scalar.AspNetCore from 2.17.1 to 3.0.0 Bumps StackExchange.Redis from 3.1.31 to 3.4.35 Bumps Testcontainers.PostgreSql from 4.14.0 to 4.17.0 Bumps xunit.runner.visualstudio from 4.0.0 to 4.0.1 Bumps xunit.v3 from 4.0.0 to 4.0.3 --- updated-dependencies: - dependency-name: AWSSDK.S3 dependency-version: 4.1.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet-dependencies - dependency-name: Confluent.Kafka dependency-version: 2.16.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet-dependencies - dependency-name: Dapper dependency-version: 2.1.89 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet-dependencies - dependency-name: DocumentFormat.OpenXml dependency-version: 3.5.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet-dependencies - dependency-name: Google.Apis.Auth dependency-version: 1.78.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet-dependencies - dependency-name: Mapster dependency-version: 10.0.14 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet-dependencies - dependency-name: Microsoft.AspNetCore.Authentication.JwtBearer dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet-dependencies - dependency-name: Microsoft.AspNetCore.Identity.EntityFrameworkCore dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet-dependencies - dependency-name: Microsoft.EntityFrameworkCore.Relational dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet-dependencies - dependency-name: Microsoft.AspNetCore.Mvc.Testing dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet-dependencies - dependency-name: Microsoft.AspNetCore.OpenApi dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet-dependencies - dependency-name: Microsoft.AspNetCore.SignalR.StackExchangeRedis dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet-dependencies - dependency-name: Microsoft.EntityFrameworkCore dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet-dependencies - dependency-name: Microsoft.EntityFrameworkCore.Design dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet-dependencies - dependency-name: Microsoft.EntityFrameworkCore.InMemory dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet-dependencies - dependency-name: Microsoft.Extensions.Caching.StackExchangeRedis dependency-version: 11.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: dotnet-dependencies - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 18.12.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet-dependencies - dependency-name: OpenTelemetry.Exporter.OpenTelemetryProtocol dependency-version: 1.21.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet-dependencies - dependency-name: OpenTelemetry.Extensions.Hosting dependency-version: 1.21.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet-dependencies - dependency-name: OpenTelemetry.Instrumentation.AspNetCore dependency-version: 1.21.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet-dependencies - dependency-name: OpenTelemetry.Instrumentation.Http dependency-version: 1.21.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet-dependencies - dependency-name: OpenTelemetry.Instrumentation.Runtime dependency-version: 1.21.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet-dependencies - dependency-name: Scalar.AspNetCore dependency-version: 3.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: dotnet-dependencies - dependency-name: StackExchange.Redis dependency-version: 3.4.35 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet-dependencies - dependency-name: Testcontainers.PostgreSql dependency-version: 4.17.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet-dependencies - dependency-name: xunit.runner.visualstudio dependency-version: 4.0.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet-dependencies - dependency-name: xunit.v3 dependency-version: 4.0.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
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 AWSSDK.S3 from 4.0.102.3 to 4.1.0.
Release notes
Sourced from AWSSDK.S3's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Confluent.Kafka from 2.15.0 to 2.16.0.
Release notes
Sourced from Confluent.Kafka's releases.
2.16.0
New experimental features
producer or consumer as a builder, which the client invokes during its own
construction and then owns, disposing it (and any Schema Registry client it
created) when the client itself is disposed. See the AvroGeneric example (#2661)
each configurable with a Schema Registry client you own or the
configuration to build one from. See the AvroGeneric,
JsonSerialization and Protobuf examples (#2661)
cluster they're connected to (#2661)
deserializers automatically, and resolved lazily on first use, so subject
name strategies based on the cluster no longer need it configured by hand.
See the AvroGenericAssociation example (#2661)
Set*SerializerBuilderandSet*DeserializerBuilderon the producer and consumer builders, the SchemaRegistry serde builders),
IClusterIdAware,ISerdeDisposable,SerdeExtensionsand the
ClusterIdclient extension are experimental: they are subject tochange or removal in a future release (#2661)
Enhancements
Fixes
platforms, which made encrypted fields unreadable across architectures
Timestamp.Typebeing read asNotAvailableon big-endian platforms(e.g. s390x): librdkafka's
rd_kafka_timestamp_type_tout-parameter (a 32-bit enum)was marshalled as a pointer-sized
IntPtr, so the value landed in the high word andwas truncated to
0on big-endian2.15.1
Enhancements
Fixes
Confluent.Kafkatests (#2656)Commits viewable in compare view.
Updated Dapper from 2.1.79 to 2.1.89.
Release notes
Sourced from Dapper's releases.
2.1.89
What's Changed
New Contributors
Full Changelog: DapperLib/Dapper@2.1.86...2.1.89
2.1.86
What's Changed
Full Changelog: DapperLib/Dapper@2.1.79...2.1.86
Commits viewable in compare view.
Updated DocumentFormat.OpenXml from 3.3.0 to 3.5.1.
Release notes
Sourced from DocumentFormat.OpenXml's releases.
3.5.1
Added
DocumentFormat.OpenXml.Office2016.Drawing.ChartDrawing.OffsetclassVersionattribute toDocumentFormat.OpenXml.Office2016.Drawing.ChartDrawing.ChartSpaceFeatureListattribute toDocumentFormat.OpenXml.Office2016.Drawing.ChartDrawing.ChartSpaceFalbackImgattribute toDocumentFormat.OpenXml.Office2016.Drawing.ChartDrawing.ChartSpaceDocumentFormat.OpenXml.Office2016.Drawing.ChartDrawing.ExtensionDropModeenum3.4.1
Added
MediaDataPartType.Mp4to support MP4 video media parts in presentations and documents (#1866)Changed
FromChunkedBase64Stringto significantly reduce allocations and improve throughput when decoding chunked base64 content (≈2.4× faster, ≈70% less memory) (#1868)Fixed
XmlDOMTextWriterinstead ofXmlWriter.Createto correctly handle serialization of certain XML content (#1869, #1961)Documentation
AutoSaveset tofalsedoes not persist changes (#1873)Thanks to the following for their contributions:
@QuocDatHoang
@Varorbc
Commits viewable in compare view.
Updated Google.Apis.Auth from 1.76.0 to 1.78.0.
Release notes
Sourced from Google.Apis.Auth's releases.
1.78.0
Features:
1.77.0
Bug fixes:
Commits viewable in compare view.
Updated Mapster from 10.0.12 to 10.0.14.
Release notes
Sourced from Mapster's releases.
10.0.14
What's Changed
Full Changelog: MapsterMapper/Mapster@v10.0.13...v10.0.14
10.0.14-pre01
What's Changed
Full Changelog: MapsterMapper/Mapster@v10.0.13...v10.0.14-pre01
10.0.13
What's Changed
New Contributors
Full Changelog: MapsterMapper/Mapster@v10.0.12...v10.0.13
10.0.13-pre02
What's Changed
Full Changelog: MapsterMapper/Mapster@v10.0.12...v10.0.13-pre02
Commits viewable in compare view.
Updated Microsoft.AspNetCore.Authentication.JwtBearer from 10.0.11 to 10.0.15.
Release notes
Sourced from Microsoft.AspNetCore.Authentication.JwtBearer's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.AspNetCore.Identity.EntityFrameworkCore from 10.0.11 to 10.0.15.
Release notes
Sourced from Microsoft.AspNetCore.Identity.EntityFrameworkCore's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.AspNetCore.Mvc.Testing from 10.0.11 to 10.0.15.
Release notes
Sourced from Microsoft.AspNetCore.Mvc.Testing's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.AspNetCore.OpenApi from 10.0.11 to 10.0.15.
Release notes
Sourced from Microsoft.AspNetCore.OpenApi's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.AspNetCore.SignalR.StackExchangeRedis from 10.0.11 to 10.0.15.
Release notes
Sourced from Microsoft.AspNetCore.SignalR.StackExchangeRedis's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.EntityFrameworkCore from 10.0.11 to 10.0.15.
Release notes
Sourced from Microsoft.EntityFrameworkCore's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.EntityFrameworkCore.Design from 10.0.11 to 10.0.15.
Release notes
Sourced from Microsoft.EntityFrameworkCore.Design's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.EntityFrameworkCore.InMemory from 10.0.11 to 10.0.15.
Release notes
Sourced from Microsoft.EntityFrameworkCore.InMemory's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.EntityFrameworkCore.Relational from 10.0.11 to 10.0.15.
Release notes
Sourced from Microsoft.EntityFrameworkCore.Relational's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.Extensions.Caching.StackExchangeRedis from 10.0.11 to 11.0.0.
Release notes
Sourced from Microsoft.Extensions.Caching.StackExchangeRedis's releases.
10.0.404
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.404and 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
Important
Please use https://builds.dotnet.microsoft.com/dotnet/source-build/dotnet-source-10.0.404-servicing.26529.119.tar.gz instead of the GitHub-generated sources tarball. This is due to a discrepancy in the ownership metadata. The signatures were generated from build-produced source archives with ownership normalized to UID/GID
2001:2001, while GitHub’s automatically generated archives use0:0. The source contents are identical, but the ownership metadata changes the archive bytes, causing signature verification to fail.10.0.403
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.403and 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
10.0.402
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.402and 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
10.0.401
Release
What's Changed
... (truncated)
10.0.400
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.400and 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
10.0.303
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.303and 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
10.0.302
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.302and 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
10.0.301
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.301and 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
10.0.300
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.300and 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
10.0.204
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.204and 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
10.0.203
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.203and 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
10.0.202
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.202and 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
10.0.201
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.201and 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
10.0.200
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.200and 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
10.0.115
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.115and 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
Important
Please use https://builds.dotnet.microsoft.com/dotnet/source-build/dotnet-source-10.0.115-servicing.26529.108.tar.gz instead of the GitHub-generated sources tarball. This is due to a discrepancy in the ownership metadata. The signature was generated from a build-produced source archive with ownership normalized to UID/GID
2001:2001, while GitHub’s automatically generated archive uses0:0. The source contents are identical, but the ownership metadata changes the archive bytes, causing signature verification to fail.10.0.114
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.114and 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
Important
Please use https://builds.dotnet.microsoft.com/dotnet/source-build/dotnet-source-10.0.114-servicing.26522.126.tar.gz instead of the GitHub-generated sources tarball. This is due to a discrepancy in the ownership metadata. The signatures were generated from build-produced source archives with ownership normalized to UID/GID
2001:2001, while GitHub’s automatically generated archives use0:0. The source contents are identical, but the ownership metadata changes the archive bytes, causing signature verification to fail.10.0.113
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.113and 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
10.0.112
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.112and 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
10.0.111
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.111and 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
10.0.110
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.110and 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
10.0.109
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.109and 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
10.0.108
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.108and 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
10.0.107
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.107and 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
10.0.106
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.106and 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
10.0.105
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.105and 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
10.0.104
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.104and 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
10.0.103
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.103and 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 is the PGP signature for the GitHub generated tarball. You can find the public key at https://dot.net/release-key-2023
10.0.102-sb1
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.102-sb1and 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
10.0.101
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.101and 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
10.0.100
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.100and 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
To produce artifacts with the .NET 10 GA version strings, users must pass the branding argument to the build:
--branding rtm.10.0.100-rc.2.25502.107
You can build .NET 10.0 RC 2 from the repository by cloning the release tag
v10.0.100-rc.2.25502.107and 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
Note: GitHub automatically generates the "Source code (tar.gz/zip)" archives included in this release. Please download the official source code from:
10.0.100-rc.1.25451.107
You can build .NET 10.0 RC 1 from the repository by cloning the release tag
v10.0.100-rc.1.25451.107and 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
10.0.100-preview.7.25380.108
You can build .NET 10.0 Preview 7 from the repository by cloning the release tag
v10.0.100-preview.7.25380.108and 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
Commits viewable in compare view.
Updated Microsoft.NET.Test.Sdk from 18.9.0 to 18.12.0.
Release notes
Sourced from Microsoft.NET.Test.Sdk's releases.
18.12.0
Security fix
This release includes the fix for CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged
executionComplete.jsonwritten by another local user, and then run attacker-controlled output handling.Affected:
Microsoft.TestPlatform.CLI18.11.0 and earlier. Every version from 18.11.1 on is fixed, including 18.12.0.Microsoft.TestPlatform.CLIis the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.The fix is also released in the
Microsoft.TestPlatform.CLIpackage, for completeness. That package is rarely used directly. It is not a dependency ofMicrosoft.NET.Test.SdkorMicrosoft.TestPlatform, so those packages do not bring it in.Details: microsoft/vstest#16654 and dotnet/announcements#517
Using custom Docker images or Nano Server? See microsoft/vstest#16652
What's Changed
Full Changelog: microsoft/vstest@v18.11.0...v18.12.0
18.11.1
Security fix
This release fixes CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged
executionComplete.jsonwritten by another local user, and then run attacker-controlled output handling.Affected:
Microsoft.TestPlatform.CLI18.11.0.Fixed in:
Microsoft.TestPlatform.CLI18.11.1.Microsoft.TestPlatform.CLIis the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.The fix is also released in the
Microsoft.TestPlatform.CLIpackage, for completeness. That package is rarely used directly. It is not a dependency ofMicrosoft.NET.Test.SdkorMicrosoft.TestPlatform, so those packages do not bring it in.Details: microsoft/vstest#16654 and dotnet/announcements#517
Using custom Docker images or Nano Server? See microsoft/vstest#16652
What's Changed
Full Changelog: microsoft/vstest@v18.11.0...v18.11.1
18.11.0
What's Changed
New Contributors
Full Changelog: microsoft/vstest@v18.10.1...v18.11.0
18.10.2
Security fix
This release fixes CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged
executionComplete.jsonwritten by another local user, and then run attacker-controlled output handling.Affected:
Microsoft.TestPlatform.CLI18.10.0 and 18.10.1.Fixed in:
Microsoft.TestPlatform.CLI18.10.2.Microsoft.TestPlatform.CLIis the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.The fix is also released in the
Microsoft.TestPlatform.CLIpackage, for completeness. That package is rarely used directly. It is not a dependency ofMicrosoft.NET.Test.SdkorMicrosoft.TestPlatform, so those packages do not bring it in.Details: microsoft/vstest#16654 and dotnet/announcements#517
Using custom Docker images or Nano Server? See microsoft/vstest#16652
What's Changed
Full Changelog: microsoft/vstest@v18.10.1...v18.10.2
18.10.1
What's Changed
Full Changelog: microsoft/vstest@v18.10.0...v18.10.1
18.10.0
What's Changed
vstest.consoleand datacollector by @nohwnd in Run Microsoft.Testing.Platform test apps under vstest.console and datacollector microsoft/vstest#16201Full Changelog: microsoft/vstest@v18.9.0...v18.10.0
Commits viewable in compare view.
Updated OpenTelemetry.Exporter.OpenTelemetryProtocol from 1.18.0 to 1.21.0.
Release notes
Sourced from OpenTelemetry.Exporter.OpenTelemetryProtocol's releases.
1.21.0
For highlights and announcements pertaining to this release see: Release Notes > 1.21.0.
The following changes are from the previous release 1.21.0-rc.2.
NuGet: OpenTelemetry v1.21.0
OpenTelemetryLoggerOptionsis now bound from theLogging:OpenTelemetryconfiguration section using the configuration binding source generator instead
of reflection, making it fully trim and Native AOT compatible. An empty value
for a boolean option is now ignored on all target frameworks rather than
throwing on some, depending on the version of
Microsoft.Extensions.Configuration.Binderin use.(#8100)
Fixed the self-diagnostics environment snapshot leaving a dangling comma in a
redacted
OTEL_RESOURCE_ATTRIBUTESvalue when it contained empty entries.(#8104)
See CHANGELOG for details.
NuGet: OpenTelemetry.Api v1.21.0
System.Diagnostics.DiagnosticSourcedependency to11.0.0for all target frameworks.
(#8066)
See CHANGELOG for details.
NuGet: OpenTelemetry.Api.ProviderBuilderExtensions v1.21.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.Console v1.21.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.InMemory v1.21.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.OpenTelemetryProtocol v1.21.0
... (truncated)
1.21.0-rc.2
The following changes are from the previous release 1.21.0-rc.1.
NuGet: OpenTelemetry v1.21.0-rc.2
Fixed an exception when downscaling empty exponential histogram buckets after
a reset.
(#8064)
Fixed tracing callbacks continuing after provider shutdown or disposal on older
target frameworks.
(#8065)
Fixed initialization failures when environment variable access is denied.
Configuration reloads retain the last successful values when access is denied.
(#8070)
Fixed a source, meter or legacy activity name with a trailing line feed
matching a wildcard pattern which does not end in a wildcard.
(#8074)
Fixed
OTEL_RESOURCE_ATTRIBUTESvalues being decoded as form data, whichchanged a
+to a space. Values are now only percent-decoded, as defined bythe Resource SDK specification.
(#8074)
Updated the schema URL of resources created by the SDK to use OpenTelemetry
Semantic Conventions version
1.45.0.(#8079)
Added support for batching the metric points exported by
PeriodicExportingMetricReader. When a maximum export batch size is set,using the new constructor overload or
PeriodicExportingMetricReaderOptions.MaxExportBatchSize, the metricpoints of each collection are split into batches of at most that many
metric points, even if that splits up the metric points of a single
metric. The batches are exported serially with the export timeout
applying to each export. It can also be configured with the
OTEL_METRIC_EXPORT_MAX_BATCH_SIZEenvironment variable.(#8053)
Fixed
PeriodicExportingMetricReaderexporting a collection which was stillin progress when
Shutdown()timed out to its exporter after the exporterhad been shut down.
(#8053)
Fixed
PeriodicExportingMetricReadernot making its final collection whenShutdown()was called before its background task had started running onplatforms where threading is not available, such as browsers.
(#8053)
... (truncated)
1.21.0-rc.1
The following changes are from the previous release 1.20.1.
NuGet: OpenTelemetry v1.21.0-rc.1
Fixed a race in the self-diagnostics sink dispatcher where disposing it
while its pump thread was exiting could throw
ArgumentNullExceptionon.NET Framework.
(#7983)
SelfDiagnosticsOptionsis now automatically bound from theOpenTelemetry:SelfDiagnosticsconfiguration section, when present.(#8008)
Fixed a race where collecting a metric with delta temporality concurrently
with the creation of a new
MetricPointcould reclaim theMetricPointwhile it was being created, losing the measurement.
(#8019)
Fixed a race where collecting a metric with delta temporality could export
the same series twice in a single collection.
(#8019)
Fixed wildcard matching timeouts that could prevent configured source, meter,
legacy activity, or metric view patterns from matching.
(#8014)
The timeout passed to
MetricReader.Collect()(for example byMeterProvider.ForceFlush()), theExportTimeoutMillisecondsofPeriodicExportingMetricReaderand theExporterTimeoutMillisecondsofBatchExportProcessor<T>are now made available to the exporter instead ofbeing ignored once the export has started, so that the OTLP exporter can
cancel an export which runs past the timeout. The
ExportTimeoutMillisecondsof
PeriodicExportingMetricReadernow also limits exports which are notstarted by the reader itself, such as those of
MeterProvider.ForceFlush().(#7996)
Fixed a race where collecting a cumulative metric concurrently with the
creation of a new
MetricPointcould export aMetricPointthat was not yetfully initialized, could case a
NullReferenceExceptionwhen enumeratingTags.(#8018)
Breaking Change Dropped support for
net8.0andnet9.0.(#6899)
Add support for .NET 11.0.
(#6899)
Added support for enabling
ActivitySources from configuration using theMicrosoft.Extensions.Diagnosticstracing APIs introduced in .NET 11 (forexample,
services.AddTracing(b => b.AddConfiguration(section))).... (truncated)
1.21.0-beta.1
The following changes are from the previous release 1.20.1-beta.1.
NuGet: OpenTelemetry.Exporter.Prometheus.AspNetCore v1.21.0-beta.1
Fixed OpenMetrics scrape responses containing a
# UNITline whose unit isnot an underscore-separated suffix of the metric family name (for example
auth.failedloginswith the unitlogins), which caused scrapers such asPrometheus to reject the whole response. The
# UNITline is now omittedfor such metrics; exported metric names are unchanged.
(#7993)
Fixed scrapes that negotiate different response formats within the
ScrapeResponseCacheDurationMillisecondswindow each triggering their ownmetrics collection. A collection now also writes the response for other
formats whose scrapes arrived alongside a previous collection, so scrapes
that keep arriving together are served from the cache. Fresh cached responses
remain available while another format is serialized, even if that
serialization fails.
(#7994)
Fixed array- and map-valued attributes being serialized as the .NET type
name (e.g.
System.Byte[],System.Int32[]) instead of being JSON-encodedas per the specification.
byte[]-valued attributes are nowBase64-encoded, and other array- and map-valued attributes are now
JSON-encoded.
(#7694)
Fixed arrays of string-valued key/value pairs being
serialized as JSON arrays of strings instead of JSON objects.
(#7694)
Fixed scrape clients which stop reading their response delaying other
scrapes until
ScrapeResponseTimeoutMillisecondselapses.(#8041)
Breaking Change Dropped support for
net8.0andnet9.0.(#6899)
Add support for .NET 11.0.
(#6899)
Fixed a scrape response containing the same series (metric name and labels)
more than once, which causes Prometheus to reject the whole response, such as
when metric or tag names are the same once escaped, tag names become the same
when UTF-8 encoded, or the scope information is disabled. Duplicate series are
now dropped, and a warning event is written.
A metric which has the name of a sample that is generated for another one
(for example
_sumof a histogram) is now dropped, and a warning event iswritten.
(#8076)
... (truncated)
1.20.1
For highlights and announcements pertaining to this release see: Release Notes > 1.20.1.
The following changes are from the previous release 1.20.0.
NuGet: OpenTelemetry v1.20.1
Fixed a possible race condition on ARM64 when multiple threads record the
first measurement with no tags, or the first overflow measurement, that could
cause the measurement to be recorded incorrectly.
(#7951)
Fixed self-diagnostics preamble redaction of quoted or encoded PEM material
and prefixed JWTs.
(#7955)
Fixed de...
Description has been truncated