Ghost Release: 5.53.1

TL;DR

Ghost v5.53.1 - Collections Migration Fix

This patch release fixes a critical bug in the database migrations for Collections where tables were being created in the wrong order, causing migration failures. The fix ensures that the collections_posts table is created after the collections table by adjusting migration timestamps.

Highlight of the Release

• Fixed critical database migration issue that prevented successful upgrades
• Ensured proper ordering of Collections table creation in database migrations
• Resolved GitHub issue #17125

Migration Guide

No special migration steps are required for this patch release. Users experiencing issues with Collections migrations in v5.53.0 should upgrade to v5.53.1 to resolve the problem.

If you've already encountered the migration error and have a broken database state, you may need to:

1. Restore from a backup taken before the failed migration
2. Upgrade directly to v5.53.1
3. If restoration isn't possible, you may need to manually create the missing tables in the correct order

For most users, a simple upgrade to v5.53.1 will prevent the issue from occurring.

Upgrade Recommendations

Immediate Upgrade Recommended

This patch release fixes a critical database migration issue that can prevent successful upgrades to v5.53.x.

• If you haven't upgraded to v5.53.0 yet: Skip directly to v5.53.1 to avoid the migration issue entirely.
• If you're currently on v5.53.0 and experiencing migration failures: Upgrade to v5.53.1 immediately.
• If you're on v5.53.0 and not experiencing issues: It's still recommended to upgrade to ensure database integrity.

This is a small, focused patch with minimal risk that resolves a significant upgrade blocker.

Bug Fixes

Database Migration Fix

Fixed a critical issue with Collections migrations where both migrations had the same timestamp, causing them to be ordered alphabetically by their slug names. This resulted in the collections_posts table being created before the collections table, causing the migration to fail with a "table does not exist" error.

The fix adjusts the timestamp of the collections_posts migration to ensure it runs after the collections table is created, allowing for proper database setup during upgrades.

This resolves GitHub issue #17125.

New Features

No new features were introduced in this patch release. This is strictly a bug fix release focused on resolving a database migration issue.

Security Updates

No security fixes were included in this patch release.

Performance Improvements

No specific performance improvements were included in this patch release.

Impact Summary

This patch release addresses a critical bug in the database migration process for Ghost's Collections feature. The issue occurred because two migrations had identical timestamps, causing them to be ordered alphabetically by their slug names rather than in the intended sequence. As a result, the system attempted to create the collections_posts table before the collections table existed, leading to migration failures.

The fix is straightforward but essential - it adjusts the timestamp of the collections_posts migration to ensure it runs after the collections table is created. This simple change prevents database errors during upgrades and ensures a smooth migration process.

While this release contains only a single bug fix, it's important for maintaining upgrade paths and preventing database corruption, particularly for self-hosted Ghost installations upgrading from versions prior to v5.53.0.

Full Release Notes