Repository navigation
deps: Bump the dotnet-dependencies group with 7 updates - #716
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 FluentValidation.DependencyInjectionExtensions from 12.1.1 to 12.2.0 Bumps Quartz from 3.22.3 to 3.22.4 Bumps Quartz.Extensions.Hosting from 3.22.3 to 3.22.4 Bumps Quartz.Serialization.SystemTextJson from 3.22.3 to 3.22.4 Bumps Swashbuckle.AspNetCore from 10.2.3 to 10.3.0 Bumps Swashbuckle.AspNetCore.Annotations from 10.2.3 to 10.3.0 Bumps xunit.runner.visualstudio from 4.0.0 to 4.0.1 --- updated-dependencies: - dependency-name: FluentValidation.DependencyInjectionExtensions dependency-version: 12.2.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet-dependencies - dependency-name: FluentValidation.DependencyInjectionExtensions dependency-version: 12.2.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet-dependencies - dependency-name: Quartz dependency-version: 3.22.4 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet-dependencies - dependency-name: Quartz dependency-version: 3.22.4 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet-dependencies - dependency-name: Quartz.Extensions.Hosting dependency-version: 3.22.4 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet-dependencies - dependency-name: Quartz.Extensions.Hosting dependency-version: 3.22.4 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet-dependencies - dependency-name: Quartz.Serialization.SystemTextJson dependency-version: 3.22.4 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet-dependencies - dependency-name: Quartz.Serialization.SystemTextJson dependency-version: 3.22.4 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet-dependencies - dependency-name: Swashbuckle.AspNetCore dependency-version: 10.3.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet-dependencies - dependency-name: Swashbuckle.AspNetCore.Annotations dependency-version: 10.3.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.runner.visualstudio dependency-version: 4.0.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
This branch has not been deployed
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 FluentValidation.DependencyInjectionExtensions from 12.1.1 to 12.2.0.
Release notes
Sourced from FluentValidation.DependencyInjectionExtensions's releases.
12.2.0
Release notes
Please read the upgrade guide if you are moving from 11.x to 12.x
Changes in 12.2.0
Changes in 12.1.0
Changes in 12.0.0
Downloads
Binaries can be downloaded from nuget:
Commits viewable in compare view.
Updated Quartz from 3.22.3 to 3.22.4.
Release notes
Sourced from Quartz's releases.
3.22.4
Fixes for the 3.x line. The public API gains one property, and there is no schema change. These are ports of fixes found while building Quartz.NET 4.4.
Fixed
A trigger whose fire fails every time is stored
ERRORinstead of being acquired again forever. A trigger whose fire failed on each attempt was released and acquired again in a tight loop, and starved its[DisallowConcurrentExecution]job's other triggers. Five consecutive failed fires of the same occurrence now store itERROR;ResetTriggerFromErrorStatebrings it back. (#3963)A calendar that throws fails only its own trigger. An
ICalendarthat threw used to strand everything around it:BLOCKEDand the worker thread never returned (#4006). The misfire handler also logged the same trigger on every scan.Now the trigger whose calendar threw is left as it was and counted as a failure. The rest of the batch, pass or completion carries on, and a database error is still retried as before.
New
JobStoreSupport.MaxConsecutiveFireFailuresandRAMJobStore.MaxConsecutiveFireFailures(flat keyquartz.jobStore.maxConsecutiveFireFailures), default 5;0turns parking off.Behaviour changes
ERRORafter 5 consecutive failed fires. A calendar that keeps throwing while a misfire is handled parks its trigger after 5 failures that are at least a misfire threshold apart, not after 5 quick passes. SetMaxConsecutiveFireFailures = 0to keep the old behaviour.ResumeTrigger,ResumeTriggers,ResumeJob,ResumeJobsandResumeAllno longer throw a calendar's exception. They log it and resume the trigger, and its misfire is handled again later.JobStoreSupport.UpdateMisfiredTriggerreturnsfalseinstead of throwing when a misfire policy throws. It returnstruewhen that failure stored the triggerERROR.The same fixes ship in Quartz.NET 4.4.
Full Changelog: quartznet/quartznet@v3.22.3...v3.22.4
Commits viewable in compare view.
Updated Quartz.Extensions.Hosting from 3.22.3 to 3.22.4.
Release notes
Sourced from Quartz.Extensions.Hosting's releases.
3.22.4
Fixes for the 3.x line. The public API gains one property, and there is no schema change. These are ports of fixes found while building Quartz.NET 4.4.
Fixed
A trigger whose fire fails every time is stored
ERRORinstead of being acquired again forever. A trigger whose fire failed on each attempt was released and acquired again in a tight loop, and starved its[DisallowConcurrentExecution]job's other triggers. Five consecutive failed fires of the same occurrence now store itERROR;ResetTriggerFromErrorStatebrings it back. (#3963)A calendar that throws fails only its own trigger. An
ICalendarthat threw used to strand everything around it:BLOCKEDand the worker thread never returned (#4006). The misfire handler also logged the same trigger on every scan.Now the trigger whose calendar threw is left as it was and counted as a failure. The rest of the batch, pass or completion carries on, and a database error is still retried as before.
New
JobStoreSupport.MaxConsecutiveFireFailuresandRAMJobStore.MaxConsecutiveFireFailures(flat keyquartz.jobStore.maxConsecutiveFireFailures), default 5;0turns parking off.Behaviour changes
ERRORafter 5 consecutive failed fires. A calendar that keeps throwing while a misfire is handled parks its trigger after 5 failures that are at least a misfire threshold apart, not after 5 quick passes. SetMaxConsecutiveFireFailures = 0to keep the old behaviour.ResumeTrigger,ResumeTriggers,ResumeJob,ResumeJobsandResumeAllno longer throw a calendar's exception. They log it and resume the trigger, and its misfire is handled again later.JobStoreSupport.UpdateMisfiredTriggerreturnsfalseinstead of throwing when a misfire policy throws. It returnstruewhen that failure stored the triggerERROR.The same fixes ship in Quartz.NET 4.4.
Full Changelog: quartznet/quartznet@v3.22.3...v3.22.4
Commits viewable in compare view.
Updated Quartz.Serialization.SystemTextJson from 3.22.3 to 3.22.4.
Release notes
Sourced from Quartz.Serialization.SystemTextJson's releases.
3.22.4
Fixes for the 3.x line. The public API gains one property, and there is no schema change. These are ports of fixes found while building Quartz.NET 4.4.
Fixed
A trigger whose fire fails every time is stored
ERRORinstead of being acquired again forever. A trigger whose fire failed on each attempt was released and acquired again in a tight loop, and starved its[DisallowConcurrentExecution]job's other triggers. Five consecutive failed fires of the same occurrence now store itERROR;ResetTriggerFromErrorStatebrings it back. (#3963)A calendar that throws fails only its own trigger. An
ICalendarthat threw used to strand everything around it:BLOCKEDand the worker thread never returned (#4006). The misfire handler also logged the same trigger on every scan.Now the trigger whose calendar threw is left as it was and counted as a failure. The rest of the batch, pass or completion carries on, and a database error is still retried as before.
New
JobStoreSupport.MaxConsecutiveFireFailuresandRAMJobStore.MaxConsecutiveFireFailures(flat keyquartz.jobStore.maxConsecutiveFireFailures), default 5;0turns parking off.Behaviour changes
ERRORafter 5 consecutive failed fires. A calendar that keeps throwing while a misfire is handled parks its trigger after 5 failures that are at least a misfire threshold apart, not after 5 quick passes. SetMaxConsecutiveFireFailures = 0to keep the old behaviour.ResumeTrigger,ResumeTriggers,ResumeJob,ResumeJobsandResumeAllno longer throw a calendar's exception. They log it and resume the trigger, and its misfire is handled again later.JobStoreSupport.UpdateMisfiredTriggerreturnsfalseinstead of throwing when a misfire policy throws. It returnstruewhen that failure stored the triggerERROR.The same fixes ship in Quartz.NET 4.4.
Full Changelog: quartznet/quartznet@v3.22.3...v3.22.4
Commits viewable in compare view.
Updated Swashbuckle.AspNetCore from 10.2.3 to 10.3.0.
Release notes
Sourced from Swashbuckle.AspNetCore's releases.
10.3.0
What's Changed
anyOf,allOf,oneOfortype = nullby @ldeluigi in Change nullability handling for schemas with anyOf, allOf, oneOf or type = null domaindrivendev/Swashbuckle.AspNetCore#3976AddServeracross multiple documents by @RaphaelFakhri in Add coverage for AddServer across multiple documents domaindrivendev/Swashbuckle.AspNetCore#4115[EnumMember]by @RaphaelFakhri in Document that System.Text.Json ignores [EnumMember] domaindrivendev/Swashbuckle.AspNetCore#4127ConfigObject.AdditionalItemsby @RaphaelFakhri in Fix #3153: serialize custom values in the UI ConfigObject AdditionalItems domaindrivendev/Swashbuckle.AspNetCore#4132New Contributors
Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.2.3...v10.3.0
Commits viewable in compare view.
Updated Swashbuckle.AspNetCore.Annotations from 10.2.3 to 10.3.0.
Release notes
Sourced from Swashbuckle.AspNetCore.Annotations's releases.
10.3.0
What's Changed
anyOf,allOf,oneOfortype = nullby @ldeluigi in Change nullability handling for schemas with anyOf, allOf, oneOf or type = null domaindrivendev/Swashbuckle.AspNetCore#3976AddServeracross multiple documents by @RaphaelFakhri in Add coverage for AddServer across multiple documents domaindrivendev/Swashbuckle.AspNetCore#4115[EnumMember]by @RaphaelFakhri in Document that System.Text.Json ignores [EnumMember] domaindrivendev/Swashbuckle.AspNetCore#4127ConfigObject.AdditionalItemsby @RaphaelFakhri in Fix #3153: serialize custom values in the UI ConfigObject AdditionalItems domaindrivendev/Swashbuckle.AspNetCore#4132New Contributors
Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.2.3...v10.3.0
Commits viewable in compare view.
Updated xunit.runner.visualstudio from 4.0.0 to 4.0.1.
Release notes
Sourced from xunit.runner.visualstudio's releases.
4.0.1
Release notes: https://xunit.net/releases/visualstudio/4.0.1
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions