Open
Conversation
10222e1 to
2847db6
Compare
f3f6983 to
99805fa
Compare
99805fa to
6b59e7e
Compare
7e93ecd to
379baa4
Compare
7d2aaff to
60fe895
Compare
fce21c3 to
1e7fda3
Compare
6d150bf to
0acc6a0
Compare
f2e1fec to
7f3e574
Compare
5102213 to
dc24af3
Compare
ffc43b6 to
3208b54
Compare
8806ff6 to
5232738
Compare
3c33435 to
de76e9a
Compare
de76e9a to
c9ccb5a
Compare
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.
This PR contains the following updates:
4.0.18.7→4.0.20.34.0.21(+1)8.0.1→8.1.08.0.1→8.1.08.0.1→8.1.08.0.1→8.1.08.0.1→8.1.010.0.3→10.0.510.0.3→10.0.510.0.3→10.0.510.0.3→10.0.510.0.3→10.0.510.0.3→10.0.510.3.0→10.4.010.0.3→10.0.510.3.0→10.4.010.3.0→10.4.010.0.1→10.0.210.0.0→10.0.11.15.0→1.15.11.15.20.14.1→0.14.43.16.1→3.17.110.0.1→10.1.610.0.1→10.1.62.13.1→2.13.202.11.8→2.12.1410.1.4→10.1.710.1.4→10.1.710.0.3→10.0.54.10.0→4.11.08.0.0→8.0.110.0.1→10.0.510.0.0→10.0.201v3.5.0→v3.11.0v3.11.10.13.0-glibc→0.14.4-glibc8.4-alpine→8.6-alpineRelease Notes
aws/aws-sdk-net (AWSSDK.S3)
v4.0.20v4.0.19dotnet/dotnet (Microsoft.AspNetCore.Authentication.JwtBearer)
v10.0.5v10.0.4dotnet/extensions (Microsoft.Extensions.Caching.Hybrid)
v10.4.0This release advances the AI abstractions with new hosted file, web search, and reasoning content types, stabilizes MCP and tool approval APIs, adds streaming latency metrics to OpenTelemetry instrumentation, and delivers bug fixes across caching, data ingestion, and resource monitoring.
Experimental API Changes
Now Stable
MEAI001) #7299FakeLogCollector.GetLogsAsync(CancellationToken)is now stable (previouslyEXTEXP0003) #7332New Experimental APIs
AddExtendedHttpClientLoggingoverloads withwrapHandlersPipelineparameter (EXTEXP0013) #7231Removed Experimental APIs
MEAI001) #7353What's Changed
AI
Telemetry and Observability
HTTP Resilience and Diagnostics
Diagnostics, Health Checks, and Resource Monitoring
Data Ingestion
Caching
Test Improvements
Repository Infrastructure Updates
Acknowledgements
Full Changelog: dotnet/extensions@v10.3.0...v10.4.0
npgsql/npgsql (Npgsql)
v10.0.2v10.0.2 contains several minor bug fixes.
Milestone issues
Full Changelog: npgsql/npgsql@v10.0.1...v10.0.2
open-telemetry/opentelemetry-dotnet (OpenTelemetry.Extensions.Hosting)
v1.15.1Release details: 1.15.1
treats baggage names and values as case sensitive, aligning with the latest
Baggage API specification.
OpenTelemetry.ApiandOpenTelemetrySDK,including fixes for thread-safety, sampler edge cases, metrics precision,
and observable instrument lifecycle handling.
quartznet/quartznet (Quartz.Extensions.Hosting)
v3.17.1Highlights
Jenkins-style H (hash) token for cron expressions
Quartz.NET now supports the
H(hash) token in cron expressions, inspired by Jenkins. TheHtoken resolves to a deterministic value based on the trigger's identity, spreading job execution times to avoid the thundering herd problem when many triggers share the same schedule.Supported forms:
H,H(min-max),H/step,H(min-max)/stepThe hash seed is automatically derived from the trigger's identity (name + group) when using
TriggerBuilder, or can be provided explicitly. See the cron trigger documentation for full details.Structured logging history plugins
New
StructuredLoggingJobHistoryPluginandStructuredLoggingTriggerHistoryPluginprovide first-class support for structured logging frameworks like Serilog and NLog. Unlike the existing logging plugins that use index-based format placeholders ({0},{1}), these use named MEL-style message template parameters ({JobName},{TriggerGroup}, etc.), making log output queryable in structured logging sinks and avoiding template cache memory leaks.Message templates are fully configurable via standard Quartz property configuration.
Bug Fixes
updateTriggers: trueno longer resets paused triggers back to normal state. (#2968)/_blazorendpoint conflict — The Quartz Dashboard no longer conflicts with host applications that also use Blazor. (#2975)Full Changelog: quartznet/quartznet@v3.17.0...v3.17.1
v3.17.0This is a major bug-fix release with 40+ fixes spanning trigger state management, clustering reliability, DST handling, misfire accuracy, and scheduler lifecycle. An optional database schema migration improves misfire handling.
Highlights
Optional database migration:
MISFIRE_ORIG_FIRE_TIMEcolumnA new optional column
MISFIRE_ORIG_FIRE_TIMEonQRTZ_TRIGGERSenables correctScheduledFireTimeUtcfor misfired triggers when using "fire now" misfire policies. Without it,ScheduledFireTimeUtcequalsFireTimeUtcfor misfired triggers (the pre-existing behavior). RAMJobStore does not require this migration.Migration script:
database/schema_30_add_misfire_orig_fire_time.sql(covers SQL Server, PostgreSQL, MySQL, SQLite, Oracle, Firebird)Clustering and concurrency fixes
DisallowConcurrentExecutionjobs running simultaneously in cluster (#2697)DisallowConcurrentExecutionviolation (#2915)DisallowConcurrentExecutionjobs (#2822)FIRED_TRIGGERSnot cleaned up on job deletion mid-execution (#1696)Trigger state and fire time accuracy
GetTriggerStatereturning Complete instead of Blocked for executing triggers (#2255)RAMJobStore.TriggersFiredskipping triggers causing wrong trigger/job execution (#1386)ScheduledFireTimeUtcreturning wrong value after misfire (#2899)PreviousFireTimeUtcreset to null on restart withOverWriteExistingData=true(#1834)SimpleTriggerfirst fire time wrong when created long before scheduling (#2455)CronTriggerdouble-firing when rescheduled with oldStartTimeUtc(#2909)JobData(#2083)DoNothingmisfire policy skipping fire times within threshold (#2912)DST and time handling
DailyTimeIntervalTriggerextra fire during DST fall-back (#2917)DailyTimeIntervalTriggermutatingStartTimeUtcduring fire time computation (#2906)DailyTimeIntervalTriggerRepeatCountto apply per day (#1633)ComputeFireTimesBetweenmodifying trigger StartTimeUtc (#2722)Scheduler lifecycle and threading
Monitor.Waitwith asyncSemaphoreSlim(#2877)DedicatedThreadPoolthreads leaking on scheduler shutdown (#1357)Job execution
RefireImmediatelywithJobChainingJobListenerfiring chain prematurely (#663)AsyncLocalflow fromIJobFactory.NewJobtoIJob.Execute(#1528)IJobDetailproperty toJobExecutionException(#1442)API and configuration
idleWaitTimeof zero silently ignored instead of throwing (#1394)AddJob/AddTriggerambiguous references without removing overloads (#2795)PauseJobs/ResumeJobinteraction bug in RAMJobStore (#761)RemoteSchedulerignoring localquartz.scheduler.instanceName(#313)Dashboard
What's Changed
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, 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.