-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump dependencies #263
Merged
Merged
Bump dependencies #263
+80
−80
Conversation
This file contains 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
coverage
Minimum allowed coverage is Generated by 🐒 cobertura-action against 1c64c8c |
ba3970d
to
ce8fbf9
Compare
c2c90c7
to
f2225f5
Compare
7015bcd
to
19058d3
Compare
19058d3
to
fbb8b23
Compare
fbb8b23
to
14e59c5
Compare
007edc0
to
071b79f
Compare
071b79f
to
40a615e
Compare
40a615e
to
6ac44bc
Compare
6ac44bc
to
1c64c8c
Compare
gitfool
approved these changes
Feb 10, 2025
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:
11.10.0
->11.11.0
17.11.1
->17.12.0
8.4.2
->8.5.2
3.0.5
->3.0.19
16.2.0
->16.3.0
v4.1.2
->v4.2.0
6.0.2
->6.0.4
v3.7.1
->v3.9.0
8.0.10-jammy
->8.0.12-jammy
2.9.2
->2.9.3
Release Notes
JeremySkinner/fluentvalidation (FluentValidation)
v11.11.0
Compare Source
Release notes
Please read the upgrade guide if you are moving from 10.x to 11.x
Note that the after 11.1.0 release, the
FluentValidation.AspNetCore
package has been moved to a separate repository and is now versioned and released separately. These release notes now only apply to the coreFluentValidation
package. ForFluentValidation.AspNetCore
release notes, please visit the FluentValidation.AspNetCore repository.Changes in 11.11.0
Changes in 11.10.0
Changes in 11.9.2
ScalePrecisionValidator
error message clarification (#2211)Changes in 11.9.1
Changes in 11.9.0
NullReferenceException
(#2152)RuleFor(x => x)
) (#2168)AddValidatorsFromAssemblyContaining
from registering validators twice (#2182)Changes in 11.8.1
Changes in 11.8.0
AbstractValidator.OnRuleAdded
to allow customization of rule instances after creation (#2114)Changes in 11.7.1
Changes in 11.7.0
Changes in 11.6.0
Changes in 11.5.2
Changes in 11.5.1
AbstractValidator.EnsureInstanceNotNull
(See #2069 for migration steps)Transform
andTransformAsync
methods (See #2072 for migration steps)Changes in 11.5.0
Changes in 11.4.0
ScalePrecision
validator and introducePrecisionScale
validator as its replacement (#2030)Changes in 11.3.0
StringSyntaxAttribute.Regex
in net7 builds (#1957)Changes in 11.2.2
MemberNameValidatorSelector
should make use ofPropertyNameResolver
when parsing expressions (#2003)Changes in 11.2.1
Only()
not taking into account parent-level unmatched failures (#1986)Changes in 11.2.0
Include
calls with theMemberNameValidatorSelector
(#1989)Changes in 11.1.1
Changes in 11.1.0
ToDictionary
method toValidationResult
(particularly useful when working with Minimal APIs)-InjectValidator
(#1960)IValidatorFactory
andServiceProviderValidatorFactory
(#1961)services.AddFluentValidationAutoValidation()
andservices.AddFluentValidationClientsideAdapters()
as replacements forservices.AddFluentValidation()
(#1965)Changes in 11.0.3
AsyncValidatorInvokedSynchronouslyException
being incorrectly thrown when the top-levelWhen
method withRuleForEach
, even when invoked asynchronously (#1955)Changes in 11.0.2
ValidationResult
using System.Text.Json (#1928)Changes in 11.0.1
With*
andWithout*
assertion methods (#1937)Changes in 11.0
RunDefaultMvcValidationAfterFluentValidationExecutes
option from ASP.NET integration.Options
property from RuleComponent.PropertyValidator
backwards compatibility layer.Only()
to the test helper asserting that no other validation errors were raised.Downloads
Binaries can be downloaded from nuget:
microsoft/vstest (Microsoft.NET.Test.Sdk)
v17.12.0
What's Changed
Internal and infrastructure fixes:
Full Changelog: microsoft/vstest@v17.11.1...v17.12.0
App-vNext/Polly (Polly)
v8.5.2
Compare Source
v8.5.1
Compare Source
System.ComponentModel.DataAnnotations.Validator
by @kmcclellan in https://github.com/App-vNext/Polly/pull/2428v8.5.0
Compare Source
RetryAfter
toBrokenCircuitException
. by @DL444 in https://github.com/App-vNext/Polly/pull/2324[DebuggerDisableUserUnhandledExceptions]
by @martincostello in https://github.com/App-vNext/Polly/pull/2003aaubry/YamlDotNet (YamlDotNet)
v16.3.0
: Release 16.3.0What's Changed
New Contributors
Full Changelog: aaubry/YamlDotNet@v16.2.1...v16.3.0
v16.2.1
: Release 16.2.1What's Changed
Full Changelog: aaubry/YamlDotNet@v16.2.0...v16.2.1
actions/cache (actions/cache)
v4.2.0
Compare Source
The cache backend service has been rewritten from the ground up for improved performance and reliability. actions/cache now integrates with the new cache service (v2) APIs.
The new service will gradually roll out as of February 1st, 2025. The legacy service will also be sunset on the same date. Changes in these release are fully backward compatible.
We are deprecating some versions of this action. We recommend upgrading to version
v4
orv3
as soon as possible before February 1st, 2025. (Upgrade instructions below).If you are using pinned SHAs, please use the SHAs of versions
v4.2.0
orv3.4.0
If you do not upgrade, all workflow runs using any of the deprecated actions/cache will fail.
Upgrading to the recommended versions will not break your workflows.
Read more about the change & access the migration guide: reference to the announcement.
Minor changes
Minor and patch version updates for these dependencies:
1.11.1
1.1.3
0.38.3
Full Changelog: actions/cache@v4...v4.2.0
coverlet-coverage/coverlet (coverlet.collector)
v6.0.4
Fixed
Diff between 6.0.3 and 6.0.4
v6.0.3
Fixed
Improvements
Diff between 6.0.2 and 6.0.3
docker/setup-buildx-action (docker/setup-buildx-action)
v3.9.0
Compare Source
v3.8.0
Compare Source
dotnet/runtime (mcr.microsoft.com/dotnet/runtime)
v8.0.12
: .NET 8.0.12Compare Source
Release
What's Changed
HybridGlobalization
by @ilonatommy in https://github.com/dotnet/runtime/pull/110183Full Changelog: dotnet/runtime@v8.0.11...v8.0.12
v8.0.11
: .NET 8.0.11Compare Source
Release
What's Changed
Full Changelog: dotnet/runtime@v8.0.10...v8.0.11
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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 was generated by Mend Renovate. View the repository job log.