Releases: dotnetcore/CAP
Releases · dotnetcore/CAP
2.3.1
2.3.0
In this version, we made some breaking changes for the publisher API, you can see this blog to understand the story behind.
If you have any migration question, please comment in issue #190.
Breaking Changes:
- Removed
app.UseCap()
from Startup.cs - Message table primary key data type has been modified to
Bigint
and non auto-Increment. (#180) - New publisher Api. (#188)
Features:
Bug Fixed:
2.2.5
Features:
- Performance improvement
Bug Fixed:
- Fixed message enqueue exception.
- Fixed Retry processor bugs.
- Fixed Kafka producer exception log without logging when publish message.
- Fixed Incorrect local IP address judgment of IPv6. (#140)
- Fixed DateTime localization format conversion error to sql. (#139)
- Fixed dashboard message page re-requeue and re-executed operate bug. #158
- Fixed SendAsync or ExecuteAsync recursion retries bug. (#160)
- Fixed configuration options of FailedThresholdCallback could not be invoke when the value less then three. (#161)
2.2.4
Because version 2.2.3 was not released to nuget, so released 2.2.4.
2.2.3
2.2.2
Features:
- Improved log output. #114
- Add default timeout configuration for kafka client.
- Rename configuration options FailedCallback to FailedThresholdCallback.
Bug Fixed:
- Fixed message enqueue exception.
- Fixed retry processor bugs.
- Fixed kafka producer exception log without logging when publish message.
2.2.1
Bug Fixed:
- Fixed message enqueue bug in v2.2
2.2.0
2.1.4
Features:
- Remove
TableNamePrefix
option fromMySqlOptions
toEFOptions
. - Upgrade nuget package
Bug Fixed:
2.1.3
Features:
- Upgrade dependent nuget packages version.
- NuGet package include xml doc now.
- NuGet now contains the CAP symbol files.