Bump Quartz.Serialization.Json from 3.3.1 to 3.3.2

Created by: dependabot-preview[bot]

Bumps Quartz.Serialization.Json from 3.3.1 to 3.3.2.

Release notes

Sourced from Quartz.Serialization.Json's releases.

Quartz.NET 3.3.2

This release returns the possibility to resolve jobs from Microsoft DI container. Now container is checked first and if not found then ActivatorUtilities is used to construct the type with constructor injection support. Now both AllowDefaultConstructor and CreateScope have been obsoleted as behavior is now either via DI construction or ActivatorUtilities and scope is always created to prevent resource leaks / double disposal.

Also a problem with host name resolution under WSL2 scenario was fixed.

FIXES

• Try resolving jobs from service provider before resorting to ActivatorUtilities (#1159)
• Can't get hostname on WSL2+docker host network (#1158)

Changelog

Sourced from Quartz.Serialization.Json's changelog.

Release 3.3.2, Apr 9 2021

This release returns the possibility to resolve jobs from Microsoft DI container. Now container is checked first and if not found then ActivatorUtilities is used to construct the type with constructor injection support. Now both AllowDefaultConstructor and CreateScope have been obsoleted as behavior is now either via DI construction or ActivatorUtilities and scope is always created to prevent resource leaks / double disposal.

Also a problem with host name resolution under WSL2 scenario was fixed.

• FIXES

  • Try resolving jobs from service provider before resorting to ActivatorUtilities (#1159)
  • Can't get hostname on WSL2+docker host network (#1158)

Commits

• 8dbadbc release preparations
• d4aa977 Simplify DNS name resolution in HostNameBasedIdGenerator (#1160)
• d26d41e Try resolving jobs from service provider before resorting to ActivatorUtiliti...
• 682aa1a Create 2021-04-08-quartznet-3.3.1-released.md
• See full diff 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 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)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)