« Changelog History


CAP v2.4.0 Release Notes

Release Date: 2018-12-08 // over 5 years ago

  • 🔋 Features :

    • 👌 Supported version options. (#220)
    • ⬆️ Upgrade nuget package to .net core 2.2.

    💥 Breaking Changes

    👍 In order to support the "version isolation" feature, we introduced a new version field in version 2.4.0 to isolate different versions of the message, so this requires some adjustments to the database table structure. You can use the following SQL to add a version field to your database CAP related table.

    MySQL

    ALTER TABLE `cap.published` ADD Version VARCHAR(20) NULL;ALTER TABLE `cap.received` ADD Version VARCHAR(20) NULL;

    SQL Server

    ALTER TABLE Cap.[Published] ADD Version VARCHAR(20) NULL;ALTER TABLE Cap.[Received] ADD Version VARCHAR(20) NULL;

    PostgreSQL

    ALTER TABLE cap.published ADD "Version" VARCHAR(20) NULL;ALTER TABLE cap.received ADD "Version" VARCHAR(20) NULL;

    MongoDb

    db.CapPublishedMessage.update({},{"$set" : {"Version" : "1"}});
db.CapReceivedMessage.update({},{"$set" : {"Version" : "1"}});

    🐛 Bug Fixed:

    • 🛠 Fixed different groups of the same topic name in one instance will cause routing bug. (#235)
    • 🛠 Fixed message presistence bug. (#240)
    • 🛠 Fixed RabbitMQ topic name contains numbers will cause exception bug. (#181)