This maintenance release adds more logging only, but now almost every exception that occurs inside StackExchange.Redis package is logged with the DEBUG log level. So internal errors can be tracked now much faster than before.
rss feed Blog
Hangfire.Pro.Redis 2.8.9
-
by
@odinserj
- release, hangfire-pro
- 0 Comments
- Edit on GitHub
Hangfire 1.6.30
-
by
@odinserj
- release, hangfire-core
- 0 Comments
- Edit on GitHub
Maintenance release for 1.6.X branch with some fixes backported from recent 1.7.X versions, including a fix for possible connection leak in Hangfire.SqlServer when an exception is thrown while releasing a distributed lock.
Continue Reading →Hangfire.Pro.Redis 2.8.8
-
by
@odinserj
- release, hangfire-pro
- 0 Comments
- Edit on GitHub
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 Betas
-
by
@odinserj
- release, hangfire-core
- 0 Comments
- Edit on GitHub
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.
Dropping TLS 1.0 and 1.1 support
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 →