Ghost Release: 5.125.0

TL;DR

Ghost v5.125.0 introduces a new site_uuid setting that provides a unique identifier for each Ghost instance. This feature is designed to improve integration with multi-tenant services like Tinybird. The update includes a migration to add this setting and ensures it remains persistent even during content imports. The site_uuid is designed to be immutable once set, creating a reliable identifier for each Ghost installation.

Highlight of the Release

• Introduction of site_uuid as a unique identifier for Ghost instances
• Improved integration capabilities with multi-tenant services like Tinybird
• Automatic generation of UUID for existing sites during migration
• Persistence of site_uuid during content imports

Migration Guide

Migration Notes

This release includes a database migration that automatically adds the site_uuid setting to your Ghost installation. The migration will:

1. Check if a site_uuid is specified in your Ghost configuration
2. Use that value if it exists and is valid
3. Generate a new UUID if no valid configuration value is found

No manual action is required for this migration. The site_uuid will be automatically set during the update process.

Note that future releases will include additional validation of the site_uuid on boot and expose this value through the /site endpoint.

Upgrade Recommendations

This is a minor feature release that adds infrastructure for future improvements. It's recommended to upgrade at your convenience, especially if you're planning to integrate with multi-tenant services or need a unique identifier for your Ghost instance.

The update is non-disruptive and includes an automatic migration that requires no manual intervention.

Bug Fixes

No specific bug fixes were mentioned in this release.

New Features

Site UUID Implementation

Ghost now includes a site_uuid setting that serves as a unique identifier for each Ghost installation. This feature:

• Generates a unique UUID for each Ghost instance during migration
• Uses the value from config.get('site_uuid') if it's already set and valid
• Ensures the identifier remains persistent even during JSON content imports
• Is designed to be immutable once set during site creation or first boot after update

This implementation lays the groundwork for improved integration with multi-tenant services like Tinybird, allowing for better tracking and management of multiple Ghost instances.

Security Updates

No security fixes were mentioned in this release.

Performance Improvements

No specific performance improvements were mentioned in this release.

Impact Summary

This release introduces a foundational feature with the site_uuid implementation, which will enable better integration capabilities for Ghost instances. The impact is minimal for most users as the change happens behind the scenes with an automatic migration.

For developers and integration partners, this release provides a new capability to uniquely identify Ghost instances, which will be particularly valuable when working with multi-tenant services like Tinybird.

The site_uuid is designed to be set once and remain immutable, providing a reliable identifier throughout the lifecycle of a Ghost installation. This release includes only the initial implementation with the migration, with additional functionality planned for future releases.

Full Release Notes