Bump the nuget-remaining group with 20 updates - #13
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps Meziantou.Analyzer from 3.0.151 to 3.0.159 Bumps Microsoft.AspNetCore.Identity.EntityFrameworkCore from 10.0.9 to 10.0.11 Bumps Microsoft.AspNetCore.Mvc.Testing from 10.0.9 to 10.0.11 Bumps Microsoft.AspNetCore.SignalR.Client from 10.0.9 to 10.0.11 Bumps Microsoft.AspNetCore.TestHost from 10.0.9 to 10.0.11 Bumps Microsoft.EntityFrameworkCore.Design from 10.0.9 to 10.0.11 Bumps Microsoft.EntityFrameworkCore.Sqlite from 10.0.9 to 10.0.11 Bumps Microsoft.EntityFrameworkCore.Tools from 10.0.9 to 10.0.11 Bumps Microsoft.Identity.Client from 4.85.2 to 4.87.0 Bumps Microsoft.Identity.Client.Extensions.Msal from 4.85.2 to 4.87.0 Bumps Microsoft.IdentityModel.JsonWebTokens from 8.19.2 to 8.22.0 Bumps Microsoft.Playwright from 1.61.0 to 1.62.0 Bumps ModelContextProtocol from 2.0.0 to 2.2.0 Bumps Quartz from 3.18.2 to 3.19.1 Bumps Quartz.Extensions.Hosting from 3.18.2 to 3.19.1 Bumps Quartz.Plugins from 3.18.2 to 3.19.1 Bumps Quartz.Plugins.TimeZoneConverter from 3.18.2 to 3.19.1 Bumps Quartz.Serialization.SystemTextJson from 3.18.2 to 3.19.1 Bumps Serilog from 4.3.1 to 4.4.0 Bumps System.Numerics.Tensors from 10.0.10 to 10.0.11 --- updated-dependencies: - dependency-name: Meziantou.Analyzer dependency-version: 3.0.159 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-remaining - dependency-name: Microsoft.AspNetCore.Identity.EntityFrameworkCore dependency-version: 10.0.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-remaining - dependency-name: Microsoft.AspNetCore.Mvc.Testing dependency-version: 10.0.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-remaining - dependency-name: Microsoft.AspNetCore.TestHost dependency-version: 10.0.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-remaining - dependency-name: Microsoft.AspNetCore.SignalR.Client dependency-version: 10.0.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-remaining - dependency-name: Microsoft.EntityFrameworkCore.Design dependency-version: 10.0.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-remaining - dependency-name: Microsoft.EntityFrameworkCore.Sqlite dependency-version: 10.0.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-remaining - dependency-name: Microsoft.EntityFrameworkCore.Tools dependency-version: 10.0.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-remaining - dependency-name: Microsoft.Identity.Client dependency-version: 4.87.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-remaining - dependency-name: Microsoft.Identity.Client.Extensions.Msal dependency-version: 4.87.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-remaining - dependency-name: Microsoft.IdentityModel.JsonWebTokens dependency-version: 8.22.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-remaining - dependency-name: Microsoft.Playwright dependency-version: 1.62.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-remaining - dependency-name: ModelContextProtocol dependency-version: 2.2.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-remaining - dependency-name: Quartz dependency-version: 3.19.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-remaining - dependency-name: Quartz.Extensions.Hosting dependency-version: 3.19.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-remaining - dependency-name: Quartz.Plugins dependency-version: 3.19.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-remaining - dependency-name: Quartz.Plugins.TimeZoneConverter dependency-version: 3.19.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-remaining - dependency-name: Quartz.Serialization.SystemTextJson dependency-version: 3.19.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-remaining - dependency-name: Serilog dependency-version: 4.4.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-remaining - dependency-name: System.Numerics.Tensors dependency-version: 10.0.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-remaining ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
|
Looks like these dependencies are updatable in another way, so this is no longer needed. |
dependabot
Bot
deleted the
dependabot/nuget/develop/nuget-remaining-8c9796270e
branch
August 19, 2026 17:56
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 Meziantou.Analyzer from 3.0.151 to 3.0.159.
Release notes
Sourced from Meziantou.Analyzer's releases.
3.0.159
NuGet package: https://www.nuget.org/packages/Meziantou.Analyzer/3.0.159
What's Changed
Full Changelog: meziantou/Meziantou.Analyzer@3.0.158...3.0.159
3.0.158
NuGet package: https://www.nuget.org/packages/Meziantou.Analyzer/3.0.158
What's Changed
Full Changelog: meziantou/Meziantou.Analyzer@3.0.157...3.0.158
3.0.157
NuGet package: https://www.nuget.org/packages/Meziantou.Analyzer/3.0.157
What's Changed
Full Changelog: meziantou/Meziantou.Analyzer@3.0.156...3.0.157
3.0.156
NuGet package: https://www.nuget.org/packages/Meziantou.Analyzer/3.0.156
What's Changed
Full Changelog: meziantou/Meziantou.Analyzer@3.0.155...3.0.156
3.0.155
NuGet package: https://www.nuget.org/packages/Meziantou.Analyzer/3.0.155
What's Changed
Full Changelog: meziantou/Meziantou.Analyzer@3.0.154...3.0.155
3.0.154
NuGet package: https://www.nuget.org/packages/Meziantou.Analyzer/3.0.154
What's Changed
Full Changelog: meziantou/Meziantou.Analyzer@3.0.153...3.0.154
3.0.153
NuGet package: https://www.nuget.org/packages/Meziantou.Analyzer/3.0.153
What's Changed
Full Changelog: meziantou/Meziantou.Analyzer@3.0.152...3.0.153
3.0.152
NuGet package: https://www.nuget.org/packages/Meziantou.Analyzer/3.0.152
What's Changed
Full Changelog: meziantou/Meziantou.Analyzer@3.0.151...3.0.152
Commits viewable in compare view.
Updated Microsoft.AspNetCore.Identity.EntityFrameworkCore from 10.0.9 to 10.0.11.
Release notes
Sourced from Microsoft.AspNetCore.Identity.EntityFrameworkCore's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.AspNetCore.Mvc.Testing from 10.0.9 to 10.0.11.
Release notes
Sourced from Microsoft.AspNetCore.Mvc.Testing's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.AspNetCore.SignalR.Client from 10.0.9 to 10.0.11.
Release notes
Sourced from Microsoft.AspNetCore.SignalR.Client's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.AspNetCore.TestHost from 10.0.9 to 10.0.11.
Release notes
Sourced from Microsoft.AspNetCore.TestHost's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.EntityFrameworkCore.Design from 10.0.9 to 10.0.11.
Release notes
Sourced from Microsoft.EntityFrameworkCore.Design's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.EntityFrameworkCore.Sqlite from 10.0.9 to 10.0.11.
Release notes
Sourced from Microsoft.EntityFrameworkCore.Sqlite's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.EntityFrameworkCore.Tools from 10.0.9 to 10.0.11.
Release notes
Sourced from Microsoft.EntityFrameworkCore.Tools's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.Identity.Client from 4.85.2 to 4.87.0.
Release notes
Sourced from Microsoft.Identity.Client's releases.
4.87.0
What's Changed
MsalServiceException.ErrorCodesForLoggingfor diagnostics in #6138WithOtelTagsEnricherfor managed identity requests in #6144ExecutionResult.Exceptionfor non-MSAL failures in #6139WithClaimsFromClient(confidential-client only) in #6113Full Changelog: AzureAD/microsoft-authentication-library-for-dotnet@4.86.1...4.87.0
4.86.1
Bug Fixes
x5t#S256) instead of only the public key, preventing a stale token (andAADSTS500181) after a same-key certificate renewal. #6123RSACryptoServiceProvider, rebuilding the client assertion so authentication can proceed. #6126O_NOFOLLOW), closing a TOCTOU window. #61154.86.0
What's Changed
Full Changelog: AzureAD/microsoft-authentication-library-for-dotnet@4.85.2...4.86.0
Commits viewable in compare view.
Updated Microsoft.Identity.Client.Extensions.Msal from 4.85.2 to 4.87.0.
Release notes
Sourced from Microsoft.Identity.Client.Extensions.Msal's releases.
4.87.0
What's Changed
MsalServiceException.ErrorCodesForLoggingfor diagnostics in #6138WithOtelTagsEnricherfor managed identity requests in #6144ExecutionResult.Exceptionfor non-MSAL failures in #6139WithClaimsFromClient(confidential-client only) in #6113Full Changelog: AzureAD/microsoft-authentication-library-for-dotnet@4.86.1...4.87.0
4.86.1
Bug Fixes
x5t#S256) instead of only the public key, preventing a stale token (andAADSTS500181) after a same-key certificate renewal. #6123RSACryptoServiceProvider, rebuilding the client assertion so authentication can proceed. #6126O_NOFOLLOW), closing a TOCTOU window. #61154.86.0
What's Changed
Full Changelog: AzureAD/microsoft-authentication-library-for-dotnet@4.85.2...4.86.0
Commits viewable in compare view.
Updated Microsoft.IdentityModel.JsonWebTokens from 8.19.2 to 8.22.0.
Release notes
Sourced from Microsoft.IdentityModel.JsonWebTokens's releases.
8.22.0
What's Changed
Full Changelog: AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet@8.21.0...8.22.0
8.21.0
Performance Improvements
Bug Fixes
Commits viewable in compare view.
Updated Microsoft.Playwright from 1.61.0 to 1.62.0.
Release notes
Sourced from Microsoft.Playwright's releases.
1.62.0
🖼️ WebP screenshots
page.screenshot() and locator.screenshot() can now capture screenshots in the WebP format — Playwright infers the format from a
.webpfile extension, or you can set thetypeexplicitly. Quality100(the default) is lossless, while lower values use lossy compression:New APIs
Scrolloption (Auto|None) on actions to opt out of Playwright's automatic scroll-into-view.Announcements
navigator.clipboardno longer read or overwrite the clipboard of the machine running them.Browser Versions
This version was also tested against the following stable channels:
Commits viewable in compare view.
Updated ModelContextProtocol from 2.0.0 to 2.2.0.
Release notes
Sourced from ModelContextProtocol's releases.
2.2.0
This release adds hybrid stateful/stateless HTTP serving so clients using the 2025-11-25 and 2026-07-28 protocol revisions can share an endpoint, and fixes a malformed header-decoding edge case.
What's Changed
Test Improvements
Repository Infrastructure Updates
Acknowledgements
Full Changelog: modelcontextprotocol/csharp-sdk@v2.1.0...v2.2.0
2.1.0
This release adds an opt-in
subscriptions/listenhandler for custom server-side notification streams, improves HTTP transport fallback reliability, and expands guidance and samples for telemetry and binary resources.What's Changed
Documentation Updates
Test Improvements
Repository Infrastructure Updates
> [!NOTE]alert example #1771 by @PranavSenthilnathan (co-authored by @Copilot)Acknowledgements
Full Changelog: modelcontextprotocol/csharp-sdk@v2.0.0...v2.1.0
Commits viewable in compare view.
Updated Quartz from 3.18.2 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
3.19.0
Quartz.NET 3.19.0 is a feature release: it adds node affinity for clustered scheduling, a fluent cron-expression builder, and richer
L/LWday-of-month expressions, plus clock-jump resilience and a modernized build and publishing pipeline. The public API is unchanged (all additions are additive), so it is a drop-in upgrade — with two things to note: the new node-affinity columns are an optional schema migration (the feature degrades gracefully without them), and a handful of previously-brokenL/LW/Wcron expressions now fire correctly (see below).Highlights
TriggerBuilder.WithPreferredNode(...); the node is preferred for acquisition but the trigger is still stolen on failover so it is never stranded if that node goes down. Adds optionalPREFERRED_NODE/PREFERRED_NODE_AUTOcolumns for ADO.NET job stores (database/schema_30_add_preferred_node.sql); when the columns are absent the scheduler logs a warning and behaves exactly as before. (#3013, #3144)CronExpressionBuilder— compose cron expressions programmatically, one field at a time, instead of hand-writing the string — handy when a schedule is assembled from user input such as a scheduling UI. (#3139)LandLWcombinable with other day-of-month values — the day-of-month field now accepts expressions such as1,15,Land the newLW-n/L-nWgrammar. This also corrects several previously-buggy edge cases:29W/31Wno longer silently skip short months,L-30Wno longer throws mid-schedule, and1,15Wnow appliesWto each day rather than only the first. These corrections change the fire times of a few expressions that were previously broken — review any storedL/LW/Wday-of-month expressions. (#2759)Note for
CronScheduleBuilderusers:AtHourAndMinuteOnGivenDaysOfWeek/WeeklyOnDayAndHourAndMinutenow emit textual day-of-week names (e.g.MON,WEDrather than2,4). The schedules are identical, but the generatedCRON_EXPRESSIONstring differs — relevant only if you compare stored cron strings byte-for-byte.What's Changed
Full Changelog: quartznet/quartznet@v3.18.2...v3.19.0
Commits viewable in compare view.
Updated Quartz.Extensions.Hosting from 3.18.2 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
3.19.0
Quartz.NET 3.19.0 is a feature release: it adds node affinity for clustered scheduling, a fluent cron-expression builder, and richer
L/LWday-of-month expressions, plus clock-jump resilience and a modernized build and publishing pipeline. The public API is unchanged (all additions are additive), so it is a drop-in upgrade — with two things to note: the new node-affinity columns are an optional schema migration (the feature degrades gracefully without them), and a handful of previously-brokenL/LW/Wcron expressions now fire correctly (see below).Highlights
TriggerBuilder.WithPreferredNode(...); the node is preferred for acquisition but the trigger is still stolen on failover so it is never stranded if that node goes down. Adds optionalPREFERRED_NODE/PREFERRED_NODE_AUTOcolumns for ADO.NET job stores (database/schema_30_add_preferred_node.sql); when the columns are absent the scheduler logs a warning and behaves exactly as before. (#3013, #3144)CronExpressionBuilder— compose cron expressions programmatically, one field at a time, instead of hand-writing the string — handy when a schedule is assembled from user input such as a scheduling UI. (#3139)LandLWcombinable with other day-of-month values — the day-of-month field now accepts expressions such as1,15,Land the newLW-n/L-nWgrammar. This also corrects several previously-buggy edge cases:29W/31Wno longer silently skip short months,L-30Wno longer throws mid-schedule, and1,15Wnow appliesWto each day rather than only the first. These corrections change the fire times of a few expressions that were previously broken — review any storedL/LW/Wday-of-month expressions. (#2759)Note for
CronScheduleBuilderusers:AtHourAndMinuteOnGivenDaysOfWeek/WeeklyOnDayAndHourAndMinutenow emit textual day-of-week names (e.g.MON,WEDrather than2,4). The schedules are identical, but the generatedCRON_EXPRESSIONstring differs — relevant only if you compare stored cron strings byte-for-byte.What's Changed
Full Changelog: quartznet/quartznet@v3.18.2...v3.19.0
Commits viewable in compare view.
Updated Quartz.Plugins from 3.18.2 to 3.19.1.
Release notes
Sourced from Quartz.Plugins'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
3.19.0
Quartz.NET 3.19.0 is a feature release: it adds node affinity for clustered scheduling, a fluent cron-expression builder, and richer
L/LWday-of-month expressions, plus clock-jump resilience and a modernized build and publishing pipeline. The public API is unchanged (all additions are additive), so it is a drop-in upgrade — with two things to note: the new node-affinity columns are an optional schema migration (the feature degrades gracefully without them), and a handful of previously-brokenL/LW/Wcron expressions now fire correctly (see below).Highlights
TriggerBuilder.WithPreferredNode(...); the node is preferred for acquisition but the trigger is still stolen on failover so it is never stranded if that node goes down. Adds optionalPREFERRED_NODE/PREFERRED_NODE_AUTOcolumns for ADO.NET job stores (database/schema_30_add_preferred_node.sql); when the columns are absent the scheduler logs a warning and behaves exactly as before. (#3013, #3144)CronExpressionBuilder— compose cron expressions programmatically, one field at a time, instead of hand-writing the string — handy when a schedule is assembled from user input such as a scheduling UI. (#3139)LandLWcombinable with other day-of-month values — the day-of-month field now accepts expressions such as1,15,Land the newLW-n/L-nWgrammar. This also corrects several previously-buggy edge cases:29W/31Wno longer silently skip short months,L-30Wno longer throws mid-schedule, and1,15Wnow appliesWto each day rather than only the first. These corrections change the fire times of a few expressions that were previously broken — review any storedL/LW/Wday-of-month expressions. (#2759)Note for
CronScheduleBuilderusers:AtHourAndMinuteOnGivenDaysOfWeek/WeeklyOnDayAndHourAndMinutenow emit textual day-of-week names (e.g.MON,WEDrather than2,4). The schedules are identical, but the generatedCRON_EXPRESSIONstring differs — relevant only if you compare stored cron strings byte-for-byte.What's Changed
Full Changelog: quartznet/quartznet@v3.18.2...v3.19.0
Commits viewable in compare view.
Updated Quartz.Plugins.TimeZoneConverter from 3.18.2 to 3.19.1.
Release notes
Sourced from Quartz.Plugins.TimeZoneConverter'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
3.19.0
Quartz.NET 3.19.0 is a feature release: it adds node affinity for clustered scheduling, a fluent cron-expression builder, and richer
L/LWday-of-month expressions, plus clock-jump resilience and a modernized build and publishing pipeline. The public API is unchanged (all additions are additive), so it is a drop-in upgrade — with two things to note: the new node-affinity columns are an optional schema migration (the feature degrades gracefully without them), and a handful of previously-brokenL/LW/Wcron expressions now fire correctly (see below).Highlights
TriggerBuilder.WithPreferredNode(...); the node is preferred for acquisition but the trigger is still stolen on failover so it is never stranded if that node goes down. Adds optionalPREFERRED_NODE/PREFERRED_NODE_AUTOcolumns for ADO.NET job stores (database/schema_30_add_preferred_node.sql); when the columns are absent the scheduler logs a warning and behaves exactly as before. (#3013, #3144)CronExpressionBuilder— compose cron expressions programmatically, one field at a time, instead of hand-writing the string — handy when a schedule is assembled from user input such as a scheduling UI. (#3139)LandLWcombinable with other day-of-month values — the day-of-month field now accepts expressions such as1,15,Land the newLW-n/L-nWgrammar. This also corrects several previously-buggy edge cases:29W/31Wno longer silently skip short months,L-30Wno longer throws mid-schedule, and1,15Wnow appliesWto each day rather than only the first. These corrections change the fire times of a few expressions that were previously broken — review any storedL/LW/Wday-of-month expressions. (#2759)Note for
CronScheduleBuilderusers:AtHourAndMinuteOnGivenDaysOfWeek/WeeklyOnDayAndHourAndMinutenow emit textual day-of-week names (e.g.MON,WEDrather than2,4). The schedules are identical, but the generatedCRON_EXPRESSIONstring differs — relevant only if you compare stored cron strings byte-for-byte.What's Changed
Full Changelog: quartznet/quartznet@v3.18.2...v3.19.0
Commits viewable in compare view.
Updated Quartz.Serialization.SystemTextJson from 3.18.2 to 3.19.1.
Release notes
Sourced from Quartz.Serialization.SystemTextJson'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
3.19.0
Quartz.NET 3.19.0 is a feature release: it adds node affinity for clustered scheduling, a fluent cron-expression builder, and richer
L/LWday-of-month expressions, plus clock-jump resilience and a modernized build and publishing pipeline. The public API is unchanged (all additions are additive), so it is a drop-in upgrade — with two things to note: the new node-affinity columns are an optional schema migration (the feature degrades gracefully without them), and a handful of previously-brokenL/LW/Wcron expressions now fire correctly (see below).Highlights
TriggerBuilder.WithPreferredNode(...); the node is preferred for acquisition but the trigger is still stolen on failover so it is never stranded if that node goes down. Adds optionalPREFERRED_NODE/PREFERRED_NODE_AUTOcolumns for ADO.NET job stores (database/schema_30_add_preferred_node.sql); when the columns are absent the scheduler logs a warning and behaves exactly as before. (#3013, #3144)CronExpressionBuilder— compose cron expressions programmatically, one field at a time, instead of hand-writing the string — handy when a schedule is assembled from user input such as a scheduling UI. (#3139)LandLWcombinable with other day-of-month values — the day-of-month field now accepts expressions such as1,15,Land the newLW-n/L-nWgrammar. This also corrects several previously-buggy edge cases:29W/31Wno longer silently skip short months,L-30Wno longer throws mid-schedule, and1,15Wnow appliesWto each day rather than only the first. These corrections change the fire times of a few expressions that were previously broken — review any storedL/LW/Wday-of-month expressions. (#2759)Note for
CronScheduleBuilderusers:AtHourAndMinuteOnGivenDaysOfWeek/WeeklyOnDayAndHourAndMinutenow emit textual day-of-week names (e.g.MON,WEDrather than2,4). The schedules are identical, but the generatedCRON_EXPRESSIONstring differs — relevant only if you compare stored cron strings byte-for-byte.What's Changed
Full Changelog: quartznet/quartznet@v3.18.2...v3.19.0
Commits viewable in compare view.
Updated Serilog from 4.3.1 to 4.4.0.
Release notes
Sourced from Serilog's releases.
4.4.0
What's Changed
SelfMetricsby @nblumhardt inSelfMetricsserilog/serilog#2237New Contributors
Full Changelog: serilog/serilog@v4.3.1...v4.4.0
Commits viewable in compare view.
Updated System.Numerics.Tensors from 10.0.10 to 10.0.11.
Release notes
Sourced from System.Numerics.Tensors's releases.
No release notes found for this version range.
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