Skip to content

Bump Quartz.Serialization.Json from 3.3.3 to 3.4.0

Created by: dependabot[bot]

Bumps Quartz.Serialization.Json from 3.3.3 to 3.4.0.

Release notes

Sourced from Quartz.Serialization.Json's releases.

Quartz.NET 3.4

This release has Quartz jobs start executing only after application startup completes successfully, unless QuartzHostedServiceOptions are used to specify otherwise. By default, this prevents jobs from running while the application is still starting, and it alleviates the need to use arbitrary start delays to achieve the effect manually.

Quartz.OpenTelemetry.Instrumentation has been marked obsolete as there's official contrib project on OpenTelemetry project side.

FIXES

  • Fix for job type loading after version change (#1286)
  • Fix StartDelayed delaying the start of other hosted services (#1314)
  • Set NextFireTime of the replaced trigger relative to the old trigger's StartTime if the old trigger's PreviousFireTime is null (#1519)
  • Include InvertTimeRange property in DailyCalendar.Clone (#1522)
  • QuartzHealthCheck never recovers after detecting failure (#1496)
  • Microsoft DI integration does not working with Microsoft.Extensions.Hosting v7 preview (#1544)

IMPROVEMENTS

  • Jobs now start executing after application startup completes successfully (#1432)
  • Support strongly-typed configuration of IDbProvider (#1312)
  • Add MSSQL Script compatible with SQL 2014 and 2012 (#1337)
  • Added usage of DisallowConcurrentExecutionAttribute for interfaces (#1345)
  • Multiple performance improvements (#1351, #1355, #1354, #1353, #1356, #1358)
  • Increase precision of SimpleTriggerImpl to ticks. (#1360)
  • Switch from FAKE to NUKE (#1413)
  • QuartzHostedService now has jobs start after application startup (#1449)
  • QuartzHostedServiceOptions can let jobs be started as part of application startup, as before this version (#1432)
  • Add helper methods to setup Microsoft.Data.Sqlite (#1275)
  • Quartz will scan job and trigger listeners from MS DI container automatically (#1561)

BREAKING CHANGES

NEW CONTRIBUTORS

... (truncated)

Changelog

Sourced from Quartz.Serialization.Json's changelog.

Release 3.4.0, Mar 27 2022

This release has Quartz jobs start executing only after application startup completes successfully, unless QuartzHostedServiceOptions are used to specify otherwise. By default, this prevents jobs from running while the application is still starting, and it alleviates the need to use arbitrary start delays to achieve the effect manually. Quartz.OpenTelemetry.Instrumentation has been marked obsolete as there's official contrib project on OpenTelemetry project side.

  • FIXES

    • Fix for job type loading after version change (#1286)
    • Fix StartDelayed delaying the start of other hosted services (#1314)
    • Set NextFireTime of the replaced trigger relative to the old trigger's StartTime if the old trigger's PreviousFireTime is null (#1519)
    • Include InvertTimeRange property in DailyCalendar.Clone (#1522)
    • QuartzHealthCheck never recovers after detecting failure (#1496)
    • Microsoft DI integration does not working with Microsoft.Extensions.Hosting v7 preview (#1544)
  • IMPROVEMENTS

    • Jobs now start executing after application startup completes successfully (#1432)
    • Support strongly-typed configuration of IDbProvider (#1312)
    • Add MSSQL Script compatible with SQL 2014 and 2012 (#1337)
    • Added usage of DisallowConcurrentExecutionAttribute for interfaces (#1345)
    • Multiple performance improvements (#1351, #1355, #1354, #1353, #1356, #1358)
    • Increase precision of SimpleTriggerImpl to ticks. (#1360)
    • Switch from FAKE to NUKE (#1413)
    • QuartzHostedService now has jobs start after application startup (#1449)
    • QuartzHostedServiceOptions can let jobs be started as part of application startup, as before this version (#1432)
    • Add helper methods to setup Microsoft.Data.Sqlite (#1275)
    • Quartz will scan job and trigger listeners from MS DI container automatically (#1561)
  • BREAKING CHANGES

Commits

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

合并请求报告

加载中