v2.50.0
14 days ago by Craig Adam
Retroactive fix for 2.45.0–2.49.0 migrations
This release corrects a migration issue introduced in v2.45.0 affecting environments that had existing records in the DataContextItem table (used only when Skip is configured). A unique constraint on the new CodeName column caused migration failures due to SQL Server’s handling of NULL values.
You may not be affected
This fix (and the manual recovery steps mentioned) only apply to licensed subscribers of the Skip product. Instances using only open-source components are not affected.
If you have existing DataContextItem records:
Before upgrading to v2.50.0, temporarily copy your DataContextItem records to another table and delete them. After migration, restore them to the DataContextItem table. This ensures compatibility with the updated filtered unique index introduced in this release.