Strapi Release: 1.5.1

TL;DR

Strapi v1.5.1 is a minor patch release that fixes a critical issue with the server restart functionality used by the Strapi Studio. The update replaces the use of context with a global strapi variable to ensure proper server restart operations.

Highlight of the Release

• Fixed server restart functionality used by Strapi Studio
• Replaced context-based restart mechanism with global strapi variable for improved reliability

Migration Guide

No migration steps are required for this patch release. Simply update your Strapi version to v1.5.1 to benefit from the fixed server restart functionality.

Upgrade Recommendations

This patch is recommended for all Strapi users who utilize Strapi Studio, as it fixes an important functionality issue with server restarts. The update is small in scope (only 54 changes across 2 files) and poses minimal risk.

To upgrade:

npm install [email protected]
# or
yarn upgrade [email protected]

Bug Fixes

Server Restart Fix

Fixed an issue with the restart function used by Strapi Studio. The previous implementation was using a context variable to restart the server, which was causing reliability issues. This has been replaced with the global strapi variable, ensuring that server restarts triggered by Studio operations work correctly and consistently.

New Features

No new features were introduced in this patch release. This update focuses solely on fixing the server restart functionality.

Security Updates

No security fixes were included in this patch release.

Performance Improvements

No specific performance improvements were included in this patch release. The focus was on fixing the server restart functionality.

Impact Summary

This patch release addresses a specific bug in the server restart functionality used by Strapi Studio. By replacing the context-based approach with a global strapi variable, the restart operation now works more reliably. This change improves the developer and content manager experience when working with Strapi Studio, as operations that require server restarts will now function as expected. The impact is focused on reliability rather than introducing new capabilities or changing existing workflows.

Full Release Notes