This is a maintenance release that increases reliability after failovers when using older Redis version with asynchronous replication enabled.
Continue Reading →This is a maintenance release that increases reliability after failovers when using older Redis version with asynchronous replication enabled.
Continue Reading →Hangfire 1.8.0-beta2 and beta1 recently released. The new versions bring a lot of improvements to create more complex workflows with new continuation options, improve role of the DeletedState
that now has its own exception information and displayed on graphs when supported by an underlying storage, bring more methods for underlying abstractions to reduce the number of round-trips to a storage and other features as well. Also this version has better defaults for Hangfire.SqlServer package, and sliding invisibility timeout option will now be used by default.
In June 2021 we will remove support for TLS 1.0 and 1.1 from our private NuGet feed and remove non-HTTPS endpoint that serves Hangfire Pro and Ace packages. The same steps happened with the official NuGet Gallery (where the most packages for .NET are stored) in April, 2020 so it’s highly likely your NuGet client already supports TLS 1.2 or higher and you don’t need to upgrade it. To support all the latest features and have the fastest install/update experience, please ensure you are using the following NuGet V3 API endpoints (V2 will still be supported):
Continue Reading →On Apr 15, 2021 Codecov (code coverage tool) team reported Bash Uploader Security Update post where they describe their recent security breach, a yet another attack on supply chain. Since we have used this software for Hangfire in the past, and since it’s still used by one of our projects, Cronos, we began to understand what’s happened. And in short – we’ve used Codecov tool from PyPI (Python Package Index) that’s different from the Bash Uploader one and is unaffected by the recent breach, according to Codecov team.
Continue Reading →This release fixes problems with missing performance counter instances in Performance Monitor due to changed instance naming rules in Microsoft.Owin.*
packages of version 3.X and the absence of instance name sanitization.