Serene v6.2.6 Release Notes

Release Date: 2022-10-17 // over 1 year ago
  • ๐Ÿ”‹ Features:

    • published @serenity-is/tsbuild npm package which will be used from tsbuild.js
    • added NodeScriptRunner for running tsbuild in watch mode (imported from .NET SpaServices)
    • added startnodescripts settings in appsettings.Development to npm run tsbuild:watch in development at startup (StartSharp)
    • try to import dialog types used by inplace add editors to Form.ts so that modular dialogs can be registered from the dialogs that these editors are used from
    • include full name of class in registerClass calls for code generated by sergen
    • removed maximizable dialog from sergen scriban templates as it is not a part of core and not used anymore
    • send an empty source map with 202 status, instead of 403, to avoid seeing warnings when SourceMapSecurityMiddleware is enabled
    • handling for root namespace in client types source generator (StartSharp)
    • made add button functional in dashboard task list (StartSharp)
    • reverted back to Microsoft.Data.SqlClient to 3.1.1 from 4.1.0 in sergen, as Encrypt=true became the default in 4.x+ (https://techcommunity.microsoft.com/t5/sql-server-blog/released-general-availability-of-microsoft-data-sqlclient-4-0/ba-p/2983346) which is a [BREAKING CHANGE] causing connections to fail. As Serenity.Data used 2.1.0 of Microsoft.Data.SqlClient, only sergen was affected by this issue, not StartSharp or Serene apps. Please see the linked doc, and either install a trusted certificate in your SQL server, or set TrustServerCertificate=true or Encrypt=false in your connection string, as we'll be updating Microsoft.Data.SqlClient to newer versions in the future, that may bring back this error.

    ๐Ÿ›  Bugfixes:

    • fix invalid relative module paths generated in source generator
    • fix cache is reset for previously reset groups after update, even if they are not reset in current transaction