Bump AutoMapper and 2 others #194
Closed
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 AutoMapper from 13.0.1 to 15.0.1.
Release notes
Sourced from AutoMapper's releases.
15.0.1
What's Changed
Full Changelog: LuckyPennySoftware/AutoMapper@v15.0.0...v15.0.1
This release supersedes the 15.0.0 release, reverting behavior and overloads so that the
AddAutoMapper
overloads separate the "scanning for maps" from the "scanning for dependencies". Unfortunately it's not really possible to combine these two together.This also fixes a critical bug in #4545 that does not work with .NET 4.x applications (as intended).
Because of this, the 15.0.0 will be delisted because of the breaking changes there.
15.0.0
Full Changelog: LuckyPennySoftware/AutoMapper@v14.0.0...v15.0.0
To set your license key:
This also introduced a breaking change with
MapperConfiguration
requiring anILoggerFactory
for logging purposes:Registering AutoMapper with
services.AddAutoMapper
will automatically supply this parameter. Otherwise you'll need to supply the logger factory.You can obtain your license key at AutoMapper.io
14.0.0
What's Changed
New Contributors
Full Changelog: LuckyPennySoftware/AutoMapper@v13.0.1...v14.0.0
Commits viewable in compare view.
Updated Microsoft.Data.SqlClient from 5.2.3 to 6.1.0.
Release notes
Sourced from Microsoft.Data.SqlClient's releases.
6.1.0
Release Notes
Stable Release 6.1.0 - 2025-07-25
This update brings the following changes since the
6.0.2 stable release:
Added
Added dedicated SQL Server vector datatype support
What Changed:
custom binary format over the TDS protocol.
(#3433,
#3443)
Who Benefits:
to processing times and memory requirements.
a consistent look-and-feel.
Impact:
using SQL Server 2025 preview:
operation.)
serialization/deserialization and string representation bloat.
applications may continue to use JSON strings to send/receive vector data,
although they will not see any of the performance improvements noted above.
Revived .NET Standard 2.0 target support
What Changed:
(#3381)
community voicing concerns.
... (truncated)
6.1.0-preview2
Preview Release 6.1.0-preview2.25178.5 - 2025-06-27
This update brings the following changes since the 6.1.0-preview1 release:
Added
Added dedicated SQL Server vector datatype support
What Changed:
Who Benefits:
Impact:
Revived .NET Standard 2.0 target support
What Changed:
Who Benefits:
Impact:
... (truncated)
6.1.0-preview1
This update brings the following changes over the previous release:
Added
Fixed
Data Source
parameter begins with a comma. #3250.Changed
SqlBulkCopy
to explicitly identify mismatched column names. #3183.IBufferWriter<byte>
. #2452.byte[]
withstring
for SNI to improve efficiency. #2790.New Contributors
DockerLinuxTest/Program.cs
reference dotnet/SqlClient#30416.0.2
This update brings the below changes over the previous release:
Fixed
NullPointerException
during socket receive #3283Changed
6.0.1
Released to NuGet.org on 2025-01-23
Breaking Changes
Added
JSON Support
JSON data type support is now available in Microsoft.Data.SqlClient v6.0. This release introduces
SqlJson
type available as an extension toSystem.Data.SqlDbTypes
: