Strapi Release: 3.0.0-alpha.26.1

TL;DR

Strapi v3.0.0-alpha.26.1 is a maintenance release that addresses several critical bugs in the framework's database handling and GraphQL functionality. It fixes issues with one-to-many updates, GraphQL queries, relation column naming, and multi-database joins. The release also improves default fetch limits and adds documentation for Heroku deployment workflows.

Highlight of the Release

• Fixed one-to-many relation updates that were causing data integrity issues
• Resolved missing populate functionality in GraphQL queries
• Fixed column naming for many-to-many relations
• Improved multi-database join support
• Set default fetch limit to 100 for better performance
• Added documentation for Heroku deployment workflows

Migration Guide

No specific migration steps are required for this patch release. This is a bug fix release that addresses issues in the alpha version and should be a straightforward upgrade from v3.0.0-alpha.26.

If you're using:

1. One-to-many or many-to-many relations: These should now work correctly after upgrading
2. GraphQL queries with populated relations: These will now properly return related data
3. Multiple databases: Join operations across databases should now function as expected

No schema changes or configuration updates are required to benefit from these fixes.

Upgrade Recommendations

This release contains important fixes for database relations and GraphQL functionality. We strongly recommend upgrading if you're using Strapi v3.0.0-alpha.26, especially if you:

• Work with one-to-many or many-to-many relations
• Use GraphQL for querying data with relations
• Connect to multiple databases
• Need consistent fetch limits for performance

The upgrade process should be straightforward as this is a patch release focused on bug fixes without introducing breaking changes. Simply update your Strapi dependencies to the latest version.

Bug Fixes

Database Relation Fixes

• One-to-many Update Fix: Resolved an issue where one-to-many relation updates were not being properly processed, causing data integrity problems (#3158)
• Many-to-many Column Naming: Fixed incorrect column naming for many-to-many relations that was causing relation lookups to fail (#3152)
• Multi-database Join Support: Fixed join functionality when working with multiple databases, improving cross-database relation queries (#3148)
• Different Database Name Standards: Added support for handling different database naming conventions across various database systems

GraphQL Improvements

• Missing Populate in Queries: Fixed an issue where GraphQL queries were not properly populating related data (#3157)
• GraphQL Loaders: Resolved problems with GraphQL data loaders that were causing inconsistent query results (#3151)

New Features

This release doesn't introduce new features as it's primarily focused on bug fixes and enhancements to existing functionality. The main enhancement is the addition of documentation for developing with Strapi on Heroku, providing guidance on the workflow from development to production environments.

Security Updates

No specific security fixes were included in this release. The changes were primarily focused on bug fixes related to database relations, GraphQL functionality, and documentation improvements.

Performance Improvements

Query Performance Enhancements

• Default Fetch Limit: Set the default fetch limit to 100 items, providing a better balance between performance and usability (#3141)
• Default Parameter Addition: Added a default parameter for fetch limits to ensure consistent query performance across the application

These changes help prevent performance issues that could occur with large datasets when no limit was specified, while still providing enough data for most use cases.

Impact Summary

This release addresses several critical bugs in Strapi's core functionality, particularly around database relations and GraphQL queries. The fixes resolve issues that could cause data integrity problems, missing related data in queries, and failures when working with multiple databases.

The performance improvement of setting a default fetch limit to 100 items helps prevent potential performance issues with large datasets while maintaining a reasonable amount of data for most use cases.

For developers working with Heroku, the added documentation provides valuable guidance on the development-to-production workflow, making deployment more straightforward.

Overall, this is an important maintenance release that improves stability and reliability for Strapi projects, especially those with complex data relationships or GraphQL API requirements.

Full Release Notes