Bump Quartz.Extensions.Hosting from 3.9.0 to 3.13.0

[dependabot]

Bumps Quartz.Extensions.Hosting from 3.9.0 to 3.13.0.

Release notes

Sourced from Quartz.Extensions.Hosting's releases.

Quartz.NET 3.13.0

This release aims to modernize targeted platforms and used dependencies.

The System.Configuration.ConfigurationManager reference has been removed from non-framework builds. This means using App.config's <quartz> section as Quartz configuration source is only supported on .NET Framework builds. This change was made to reduce legacy dependencies and to make Quartz more compatible with modern .NET.

The netcoreapp3.1 target has been removed from DI and hosting integration packages which makes NET 6 the lowest supported modern runtime version for those packages.

What's Changed

• Remove netcoreapp3.1 support and trim dependencies by @​lahma in quartznet/quartznet#2507
• Remove System.Configuration.ConfigurationManager package reference by @​lahma in quartznet/quartznet#2513

Full Changelog: quartznet/quartznet@v3.12.0...v3.13.0

Quartz.NET 3.12.0

This release aims to alleviate some problems that have been present then Quartz's own global singletons clash with DI containers singleton concept when DI container is being torn down during testing. Now both scheduler repository and DB connection manager are scoped inside DI container and share container's lifetime.

If you want to have multiple service collections sharing same global state, you should manually register IDbConnectionManager and ISchedulerRepository to DI as singletons pointing to global object instances.

// add globals before AddQuartz to get old behavior
services.AddSingleton<IDbConnectionManager>(DBConnectionManager.Instance);
services.AddSingleton<ISchedulerRepository>(SchedulerRepository.Instance);
services.AddQuartz(...)

What's Changed

• Upgrade System.Text.Json to 8.0.4 by @​lahma in quartznet/quartznet#2466
• Add trigger serializers for Newtonsoft based serializer by @​lahma in quartznet/quartznet#2480
• Make scheduler registration cleanup more robust during shutdown by @​lahma in quartznet/quartznet#2498
• Change scheduler repository to be singleton scoped under MS DI integration by @​lahma in quartznet/quartznet#2502
• Change DB connection manager to be singleton scoped under MS DI integration by @​lahma in quartznet/quartznet#2504

Full Changelog: quartznet/quartznet@v3.11.0...v3.12.0

Quartz.NET 3.11.0

What's Changed

• Don't create intermediate MemoryStream in SystemTextJsonObjectSerializer by @​lahma in quartznet/quartznet#2418
• Fix postgres testing and STJ dictionary serialization by @​lahma in quartznet/quartznet#2437
• Add support for DbDataSource by @​Hawxy in quartznet/quartznet#2439
• Fix issues with STJ serializer by @​VilleHakli in quartznet/quartznet#2434
• Fix DirtyFlagMap enumerator behaviors by @​lahma in quartznet/quartznet#2445

... (truncated)

Changelog

Sourced from Quartz.Extensions.Hosting's changelog.

Release 3.13.0, Aug 10 2024

This release removes aims to modernise targeted platforms and used dependencies.

The System.Configuration.ConfigurationManager reference from non-framework builds. This means using App.config's <quartz> section as Quartz configuration source is only supported on .NET Framework builds. This change was made to reduce legacy dependencies and to make Quartz more compatible with modern .NET.

The netcoreapp3.1 target has been removed from DI and hosting integration package which makes NET 6 the lowest supported modern runtime version for those packages.

• CHANGES
  • Remove System.Configuration.ConfigurationManager package reference (#2513)
  • Remove netcoreapp3.1 support and trim dependencies (#2507)

Release 3.12.0, Aug 3 2024

This release aims to alleviate some problems that have been present then Quartz's own global singletons clash with DI containers singleton concept when DI container is being torn down during testing. Now both scheduler repository and DB connection manager are scoped inside DI container and share container's lifetime.

If you want to have multiple service collections sharing same global state, you should manually register IDbConnectionManager and ISchedulerRepository to DI as singletons pointing to global object instances.

• NEW FEATURES

  • Add custom trigger serializer support for Newtonsoft integration (#2480)

• CHANGES

  • Change scheduler repository to be singleton scoped to DI under MS DI integration (#2502)
  • Change DB connection manager to be singleton scoped under MS DI integration (#2504)

• FIXES

  • Make scheduler registration cleanup more robust during shutdown (#2498)

Release 3.11.0, Jul 7 2024

• NEW FEATURES

  • Add support for DbDataSource (#2439)
  • Allow MSSQL Init Database script to be configured to not delete existing tables (#2449)

• CHANGES

  • Update build actions to use checkout/@v4 for Docs and Qodana (#2451)
  • Change NativeJob to use RuntimeInformation.IsOSPlatform instead of env var (#2411)

• FIXES

  • Fix issues with STJ serializer (#2434)
  • Fix DirtyFlagMap enumerator behaviors (#2445)
  • Improve binary to JSON migration support and documentation (#2458)
  • Don't create intermediate MemoryStream in SystemTextJsonObjectSerializer (#2418)

... (truncated)

Commits

• b30443e Release preparations
• 6a79cf6 Remove System.Configuration.ConfigurationManager package reference (#2513)
• 06545bc Remove netcoreapp3.1 support and trim dependencies (#2507)
• 66eeb41 Update version number for next preview
• 00fb3db Release preparations
• 39a6383 Change DB connection manager to be singleton scoped under MS DI integration (...
• 8778b0b Cleanup
• ac35f77 Make ISchedulerRepository and SchedulerRepository public
• 2a57ccc Fix scheduler repository lookup in QuartzScheduler
• 5a63e2d Change scheduler repository to be singleton scoped to DI under MS DI integrat...
• Additional 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 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)