v2.43.0
Retroactive fix to 2.42.x migration
We discovered an issue in the migrations caused by an unresolvable conflict and have updated a previously released migration file. Installations not migrated since 2.41.x, as well as those using migrations from 2.43.0 and on are unaffected by this retroactive fix, but some installations will require a small manual update to the schema history table.
If your installation requires the fix
For installations that applied the original migration files for 2.42.x, please update the checksums in your flyway_schema_table
to match the new (revised) checksums. The exact command will depend on your MemberJunction admin schema name, for example, with the __mj
schema name
UPDATE __mj.flyway_schema_history SET checksum=1904692914 WHERE installed_rank=92 AND version='202505211302';
UPDATE __mj.flyway_schema_history SET checksum=-360180880 WHERE installed_rank=93 AND version='202505211718';
UPDATE __mj.flyway_schema_history SET checksum=-72772630 WHERE installed_rank=98 AND version='202505240629';
After this one-time fix to update the checksum, you can continue to run future migrations as usual.
New Features
Recursive Template Embedding
Introduced a recursive template embedding extension, allowing templates to include other templates recursively. This enhancement is accompanied by comprehensive documentation to guide developers in utilizing this feature effectively.
Field Deprecation Support
Added a Status
column to the EntityField
table, enabling individual fields to be marked as deprecated or disabled. The BaseEntity
infrastructure now includes assertions on the Status
, and the CodeGen tool emits a @deprecated
decorator in the generated JSDoc, providing clear indications of deprecated fields.
Improvements
Dynamic SQL for Constraint Management
Implemented dynamic SQL to drop constraints for columns slated for removal. This approach enhances the flexibility and robustness of schema modifications by ensuring that constraints are appropriately handled during column deletions.