-
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 #212
Merged
Merged
Bump dependencies #212
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 0f5711d |
renovate
bot
force-pushed
the
renovate/minor
branch
3 times, most recently
from
June 22, 2023 21:25
e6979fd
to
3d4deb1
Compare
renovate
bot
force-pushed
the
renovate/minor
branch
3 times, most recently
from
July 3, 2023 11:26
36c8c18
to
4a159a1
Compare
renovate
bot
force-pushed
the
renovate/minor
branch
5 times, most recently
from
July 11, 2023 15:40
49b7d31
to
fe1f1b6
Compare
renovate
bot
force-pushed
the
renovate/minor
branch
3 times, most recently
from
July 14, 2023 15:58
094bc38
to
843ed7b
Compare
renovate
bot
force-pushed
the
renovate/minor
branch
3 times, most recently
from
August 11, 2023 14:14
6a94b2f
to
e4923a2
Compare
renovate
bot
force-pushed
the
renovate/minor
branch
2 times, most recently
from
August 13, 2023 21:11
7b55927
to
d5d8a05
Compare
renovate
bot
force-pushed
the
renovate/minor
branch
from
August 13, 2023 22:44
d5d8a05
to
0f5711d
Compare
gitfool
approved these changes
Aug 13, 2023
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.5.2
->11.7.1
3.0.124
->3.0.134
17.6.2
->17.7.0
7.2.3
->7.2.4
13.1.0
->13.1.1
3.0.0
->3.1.0
v2.6.0
->v2.9.1
v3.7.7
->v3.8.0
2.4.2
->2.5.0
2.4.5
->2.5.0
Release Notes
JeremySkinner/fluentvalidation (FluentValidation)
v11.7.1
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.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:
v11.7.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.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:
v11.6.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.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:
spekt/junit.testlogger (JunitXml.TestLogger)
v3.0.134
Changes
Nuget release: https://www.nuget.org/packages/JunitXml.TestLogger/3.0.134
microsoft/vstest (Microsoft.NET.Test.Sdk)
v17.7.0
The most pressing issues were all backported to 17.6.1, 17.6.2 and 17.6.3.
Issues fixed (since 17.6.3)
Don't print socket transport error in console by @nohwnd in #4493 which fixes #4461
When testhost crashes, we no longer print the transport error:
This error is a side-effect or our architecture is almost never the culprit. Instead it leads developers away from the actual issue which is crash of testhost, or datacollector.
Pass workloads to proxy managers in #4422 by @nohwnd
Which allows datacollector users to only receive the sources that are currently running in the testhost associated to datacollector, instead of all the sources that have the same target framework.
Fix Newtonsoft versions in testhost.deps.json in #4367 by @nohwnd
testhost.runtimeconfig.json files that we ship with testhost contained an old version of Newtonsoft.Json. The version in this file does not have an effect on execution, but some compliance tools statically analyze it and report possible vulnerabilities.
Other fixes:
Special thanks to @SimonCropp for the many fixes regarding nullability spelling and code style in #4518, #4520, #4525, #4526, #4521, #4519, #4522, #4529 🙇
Full Changelog: microsoft/vstest@v17.6.3...v17.7.0
Drops
v17.6.3
Issues Fixed
Full Changelog: microsoft/vstest@v17.6.2...v17.6.3
Artifacts
App-vNext/Polly (Polly)
v7.2.4
Compare Source
aaubry/YamlDotNet (YamlDotNet)
v13.1.1
: Release 13.1.1Fix Emitter to handle comments between a mapping key and a mapping/sequence value
cake-build/cake (cake.tool)
v3.1.0
docker/setup-buildx-action (docker/setup-buildx-action)
v2.9.1
Compare Source
Full Changelog: docker/setup-buildx-action@v2.9.0...v2.9.1
v2.9.0
Compare Source
Full Changelog: docker/setup-buildx-action@v2.8.0...v2.9.0
v2.8.0
Compare Source
Full Changelog: docker/setup-buildx-action@v2.7.0...v2.8.0
v2.7.0
Compare Source
Full Changelog: docker/setup-buildx-action@v2.6.0...v2.7.0
mikepenz/action-junit-report (mikepenz/action-junit-report)
v3.8.0
Compare Source
🚀 Features
💬 Other
📦 Dependencies
v3.7.8
Compare Source
💬 Other
📦 Dependencies
xunit/xunit (xunit)
v2.5.0
Compare Source
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 has been generated by Mend Renovate. View repository job log here.