Bump Hangfire from 1.6.21 to 1.7.1

[dependabot-preview]

Bumps Hangfire from 1.6.21 to 1.7.1.

Release notes

Sourced from Hangfire's releases.

1.7.1

Release Notes

Please see https://docs.hangfire.io/en/latest/upgrade-guides/upgrading-to-hangfire-1.7.html to learn how to upgrade to 1.7.X.

This is a patch release that adds some nice features for Dashboard UI, knows how to deal with recurring jobs with invalid Cron expressions, and contains some minor improvements for SQL Server storage. Also, Hangfire.NetCore package was added to support new .NET Core Worker Service applications without referencing any ASP.NET Core packages.

Hangfire.Core

• Added – DashboardOptions.IgnoreAntiforgeryToken property to disable token validation in Dashboard UI.
• Added – Display hints regarding server status on Servers page in Dashboard UI.
• Added – Highlight recurring jobs with no next execution in Dashboard UI.
• Added – Show actual error in Dashboard UI when recurring job has an invalid Cron expression.
• Fixed – InvalidOperationException when AllowSynchronousIO option isn't set in ASP.NET Core 3.0.
• Fixed – Set NextExecution value to null when existing recurring job has an invalid Cron expression.
• Fixed – Make dashboard charts to be more culture-specific to use correct time format.
• Fixed – Obsolete UseSerializationSettings comment now contains correct method name (by @​PaitoAnderson).
• Project – resx files now re-generated automatically when building a project.

Hangfire.NetCore

• Added – Worker Service host support for .NET Core without unnecessary dependencies to ASP.NET Core.

Hangfire.SqlServer

• Changed – Use blocking fetch implementation only for sub-second polling intervals.
• Fixed – Don't fail with an exception when can't connect to MS SQL instance during start-up.
• Fixed – Don't access the JobQueue table when using blocking query and don't have results.

1.7.0

Release Notes

Please see the Upgrading to Hangfire 1.7 article to learn more about the upgrade steps.

Hangfire.Core

• Added – Full .NET Core 2.0 support by explicitly targeting .NET Standard 2.0.
• Added – IGlobalConfiguration.SetDataCompatibilityLevel to enable rolling upgrades from version 1.6.
• Added – IGlobalConfiguration.UseRecommendedSerializerSettings method for new installations.
• Added – Assemblies now loaded automatically when resolving a type when using default type resolver.
• Added – Custom TaskScheduler can now be specified in BackgroundJobServerOptions for workers.
• Added – IdempotentCompletionAttribute filter to enforce strict order for continuations.
• Added – IBackgroundJobClient.ContinueJobWith methods to replace ContinueWith ones in future for clarity.
• Added – JobStorage.LinearizableReads virtual property to avoid unnecessary waits in state changer.
• Added – Allow async methods to run their continuations on worker thread by disabling TaskScheduler.
• Added – Multi-stage shutdown to wait for graceful completion before starting to abort jobs.
• Added – Asynchronous checks for job cancellation, IJobCancellationToken can be replaced with CancellationToken (by @​pieceofsummer).
• Added – Possibility to create millions of recurring jobs without stressing the scheduler.
• Added – Second-based recurring jobs are fully supported now with 6-part cron expressions.
• Added – Support for custom TimeZoneInfo resolvers in recurring jobs for interoperability purposes.

... (truncated)

Commits

• 8bbb32d Add release notes for version 1.7.1
• da5cfe8 Bump version to 1.7.1
• b72a8d4 Add DashboardOptions.IgnoreAntiforgeryToken property
• c1b4743 Reduce the PollingQuantum to 1 second
• 3089dbe Don't use waitfor statements when waiting for a lock as it consume CPU
• 242090f Change long polling implementation when using SQL Server
• fef3fb5 Don't calculate pollInterval on each iteration when using transactional fetch
• 9cd337b Don't access the JobQueue table when using blocking query and don't have results
• 9cd7992 Update SqlServerTimeoutJobFacts.cs
• 7158170 Update SqlServerTimeoutJobFacts.cs
• 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 ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major 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)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• 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)

Finally, you can contact us by mentioning @dependabot.

[dependabot-preview]

Superseded by #32.