search

hard-rox / kathanika

A Library Management System for cataloging personal book collection
MIT License
1 stars 1 forks source link

build(deps): bump Quartz.Extensions.Hosting and Quartz #1284

Closed dependabot[bot] closed 1 month ago

dependabot[bot] commented 1 month ago

Bumps Quartz.Extensions.Hosting and Quartz. These dependencies needed to be updated together. Updates Quartz.Extensions.Hosting from 3.11.0 to 3.12.0

Release notes

Sourced from Quartz.Extensions.Hosting's releases.

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

Full Changelog: https://github.com/quartznet/quartznet/compare/v3.11.0...v3.12.0

Changelog

Sourced from Quartz.Extensions.Hosting's changelog.

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)
Commits
  • 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...
  • e26bb5d Make scheduler registration cleanup more robust during shutdown (#2498)
  • 405dddb Add custom trigger serializer support for Newtonsoft integration (#2480)
  • c8bba86 Improve API documentation
  • 722b75d Upgrade System.Text.Json to 8.0.4 (#2466)
  • Additional commits viewable in compare view


Updates Quartz from 3.11.0 to 3.12.0

Release notes

Sourced from Quartz's releases.

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

Full Changelog: https://github.com/quartznet/quartznet/compare/v3.11.0...v3.12.0

Changelog

Sourced from Quartz's changelog.

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)
Commits
  • 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...
  • e26bb5d Make scheduler registration cleanup more robust during shutdown (#2498)
  • 405dddb Add custom trigger serializer support for Newtonsoft integration (#2480)
  • c8bba86 Improve API documentation
  • 722b75d Upgrade System.Text.Json to 8.0.4 (#2466)
  • 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 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)