Bump the nuget-minor-patch group with 8 updates - #160
Conversation
Bumps Microsoft.OpenApi from 2.9.0 to 2.11.0 Bumps Quartz from 3.19.0 to 3.19.1 Bumps Quartz.Extensions.Hosting from 3.19.0 to 3.19.1 Bumps Spectre.Console from 0.55.0 to 0.56.0 Bumps Spectre.Console.Json from 0.55.0 to 0.56.0 Bumps Spectre.Console.Testing from 0.55.0 to 0.57.2 Bumps SQLitePCLRaw.bundle_e_sqlite3 from 3.0.4 to 3.0.5 Bumps WireMock.Net from 2.13.0 to 2.14.0 --- updated-dependencies: - dependency-name: Microsoft.OpenApi dependency-version: 2.11.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-patch - dependency-name: Quartz dependency-version: 3.19.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-minor-patch - dependency-name: Quartz.Extensions.Hosting dependency-version: 3.19.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-minor-patch - dependency-name: Spectre.Console dependency-version: 0.56.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-patch - dependency-name: Spectre.Console.Json dependency-version: 0.56.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-patch - dependency-name: Spectre.Console.Testing dependency-version: 0.57.2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-patch - dependency-name: SQLitePCLRaw.bundle_e_sqlite3 dependency-version: 3.0.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-minor-patch - dependency-name: WireMock.Net dependency-version: 2.14.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-patch ... Signed-off-by: dependabot[bot] <support@github.com>
…ule gap The grouped run bumped Spectre.Console to 0.56.0 and Spectre.Console.Testing to 0.57.2 while Spectre.Console.Cli stayed on 0.55.0 - exactly the split the comment in Directory.Packages.props rules out. The CLI's stable line stops at 0.55.0 (everything after is a 1.0.0-alpha prerelease) and it pins Spectre.Console to its own version, so a newer core paired with a CLI built against 0.55 is a real risk on a 0.x library. Green CI does not refute that: the failure mode is behavioural drift, not a build break. Two gaps let this through, both fixed here: - Spectre.Console.Testing was never in the ignore list, so nothing capped it. - The floor was >=0.57.0, which still permits 0.56.0 and splits the family just the same. Now a single wildcard rule holds every Spectre.Console* package below 0.56.0, to be lifted when Spectre.Console.Cli 1.0 ships. The other six bumps in this PR are untouched.
|
Pushed a commit that reverts the Spectre bumps and closes the ignore-rule gap that produced them. The group had moved Two config gaps allowed it: The other five bumps (SQLitePCLRaw 3.0.5, Quartz + Quartz.Extensions.Hosting 3.19.1, Microsoft.OpenApi 2.11.0, WireMock.Net 2.14.0) are unchanged. |
Updated Microsoft.OpenApi from 2.9.0 to 2.11.0.
Release notes
Sourced from Microsoft.OpenApi's releases.
2.11.0
2.11.0 (2026-07-15)
Features
Bug Fixes
2.10.0
2.10.0 (2026-07-03)
Features
Bug Fixes
Commits viewable in compare view.
Updated Quartz from 3.19.0 to 3.19.1.
Release notes
Sourced from Quartz's releases.
3.19.1
Quartz.NET 3.19.1 is a small bug fix release with two targeted fixes:
DailyTimeIntervalTriggerno longer gets stuck in an infinite fire loop on DST spring-forward days, andStdSchedulerFactory.GetScheduler(schedName)now creates the scheduler when the name asked for is its own. There are no API or schema changes, so it is a drop-in upgrade from 3.19.0.Highlights
DailyTimeIntervalTriggerno longer spins on DST transition days —GetFireTimeAftercould return a time at or before the one it was given, which makesQuartzSchedulerThreadfire the trigger, compute the same next fire time, and fire again — pinning a CPU core and flooding the log. Two independent causes, both on a spring-forward day: the DST correction added for #1114 was applied to every interval size and in either direction (so every interval of an hour or less was affected, in every DST time zone), and the daily rollover toStartTimeOfDayreused whatever UTC offset the previous fire time carried (so in time zones that move the clock at midnight, such as Chile,StartTimeOfDay00:00 resolved to an instant before the transition — the same instant that was passed in). Verified across 3024 combinations of 12 time zones, both transitions, 21 intervals and 6 start times: 468 combinations produced non-advancing fire times before, none do now. (#3190, fixes #332)StdSchedulerFactory.GetScheduler(schedName)creates its own scheduler — asking a factory for the scheduler it is configured to produce returnednulluntil somebody had calledGetScheduler()first. It now creates it. Any other name stays a pure lookup, so probing for a scheduler somebody else owns still has no side effects, and the name comparison is case-insensitive to match howSchedulerRepositoryindexes names. The DI factory has behaved this way since #2845; this brings the property-configured factory in line. (#3188, reported in #2786, originally proposed in #360)What's Changed
Full Changelog: quartznet/quartznet@v3.19.0...v3.19.1
Commits viewable in compare view.
Updated Quartz.Extensions.Hosting from 3.19.0 to 3.19.1.
Release notes
Sourced from Quartz.Extensions.Hosting's releases.
3.19.1
Quartz.NET 3.19.1 is a small bug fix release with two targeted fixes:
DailyTimeIntervalTriggerno longer gets stuck in an infinite fire loop on DST spring-forward days, andStdSchedulerFactory.GetScheduler(schedName)now creates the scheduler when the name asked for is its own. There are no API or schema changes, so it is a drop-in upgrade from 3.19.0.Highlights
DailyTimeIntervalTriggerno longer spins on DST transition days —GetFireTimeAftercould return a time at or before the one it was given, which makesQuartzSchedulerThreadfire the trigger, compute the same next fire time, and fire again — pinning a CPU core and flooding the log. Two independent causes, both on a spring-forward day: the DST correction added for #1114 was applied to every interval size and in either direction (so every interval of an hour or less was affected, in every DST time zone), and the daily rollover toStartTimeOfDayreused whatever UTC offset the previous fire time carried (so in time zones that move the clock at midnight, such as Chile,StartTimeOfDay00:00 resolved to an instant before the transition — the same instant that was passed in). Verified across 3024 combinations of 12 time zones, both transitions, 21 intervals and 6 start times: 468 combinations produced non-advancing fire times before, none do now. (#3190, fixes #332)StdSchedulerFactory.GetScheduler(schedName)creates its own scheduler — asking a factory for the scheduler it is configured to produce returnednulluntil somebody had calledGetScheduler()first. It now creates it. Any other name stays a pure lookup, so probing for a scheduler somebody else owns still has no side effects, and the name comparison is case-insensitive to match howSchedulerRepositoryindexes names. The DI factory has behaved this way since #2845; this brings the property-configured factory in line. (#3188, reported in #2786, originally proposed in #360)What's Changed
Full Changelog: quartznet/quartznet@v3.19.0...v3.19.1
Commits viewable in compare view.
Updated Spectre.Console from 0.55.0 to 0.56.0.
Release notes
Sourced from Spectre.Console's releases.
0.56.0
What's Changed
New Contributors
Full Changelog: spectreconsole/spectre.console@0.55.2...0.56.0
0.55.2
What's Changed
New Contributors
Full Changelog: spectreconsole/spectre.console@0.55.1...0.55.2
0.55.1
What's Changed
New Contributors
Full Changelog: spectreconsole/spectre.console@0.55.0...0.55.1
Commits viewable in compare view.
Updated Spectre.Console.Json from 0.55.0 to 0.56.0.
Release notes
Sourced from Spectre.Console.Json's releases.
0.56.0
What's Changed
New Contributors
Full Changelog: spectreconsole/spectre.console@0.55.2...0.56.0
0.55.2
What's Changed
New Contributors
Full Changelog: spectreconsole/spectre.console@0.55.1...0.55.2
0.55.1
What's Changed
New Contributors
Full Changelog: spectreconsole/spectre.console@0.55.0...0.55.1
Commits viewable in compare view.
Updated Spectre.Console.Testing from 0.55.0 to 0.57.2.
Release notes
Sourced from Spectre.Console.Testing's releases.
0.57.2
What's Change
Full Changelog: spectreconsole/spectre.console@0.57.1...0.57.2
0.57.1
What's Changed
Full Changelog: spectreconsole/spectre.console@0.57.0...0.57.1
0.57.0
What's Changed
Full Changelog: spectreconsole/spectre.console@0.56.0...0.57.0
0.56.0
What's Changed
New Contributors
Full Changelog: spectreconsole/spectre.console@0.55.2...0.56.0
0.55.2
What's Changed
New Contributors
Full Changelog: spectreconsole/spectre.console@0.55.1...0.55.2
0.55.1
What's Changed
New Contributors
Full Changelog: spectreconsole/spectre.console@0.55.0...0.55.1
Commits viewable in compare view.
Updated SQLitePCLRaw.bundle_e_sqlite3 from 3.0.4 to 3.0.5.
Release notes
Sourced from SQLitePCLRaw.bundle_e_sqlite3's releases.
3.0.5
Update the lib dependency for
SQLitePCLRaw.bundle_e_sqlite3to package IDSQLiteversion 3.53.4.Commits viewable in compare view.
Updated WireMock.Net from 2.13.0 to 2.14.0.
Release notes
Sourced from WireMock.Net's releases.
2.14.0
What's Changed
New Contributors
Full Changelog: wiremock/WireMock.Net@2.13.0...2.14.0
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