Strapi Release: 3.0.0-beta.18.1

TL;DR

Strapi v3.0.0-beta.18.1 is a minor update that adds API token documentation and fixes a database testing issue during project creation. This release improves the developer experience by providing better guidance on API token usage and ensuring smoother project initialization.

Highlight of the Release

• Added comprehensive guide for API token usage
• Fixed database testing issue when creating new projects with strapi new
• Enhanced migration guide from beta.17 to beta.18 with database migration instructions for components
• Added instructions for copying index.html and production.html files during migration

Migration Guide

Migrating from v3.0.0-beta.18 to v3.0.0-beta.18.1

This is a minor patch release that doesn't require any specific migration steps. You can update your Strapi version in your package.json file:

{
  "dependencies": {
    "strapi": "3.0.0-beta.18.1",
    "strapi-admin": "3.0.0-beta.18.1",
    "strapi-connector-bookshelf": "3.0.0-beta.18.1",
    "strapi-plugin-content-manager": "3.0.0-beta.18.1",
    "strapi-plugin-content-type-builder": "3.0.0-beta.18.1",
    "strapi-plugin-email": "3.0.0-beta.18.1",
    "strapi-plugin-upload": "3.0.0-beta.18.1",
    "strapi-plugin-users-permissions": "3.0.0-beta.18.1",
    "strapi-utils": "3.0.0-beta.18.1"
  }
}

Then run:

npm install
# or
yarn install

Note on Migration from beta.17 to beta.18

If you're migrating from beta.17 to beta.18.1, please refer to the updated migration guide that now includes:

• Database migration instructions for components
• Steps for copying index.html and production.html files

Upgrade Recommendations

This is a minor patch release that fixes a database testing issue and improves documentation. We recommend all Strapi beta users to upgrade to this version, especially if you:

1. Are creating new Strapi projects frequently with the strapi new command
2. Need guidance on API token usage
3. Are planning to migrate from beta.17 to beta.18

The upgrade process is straightforward and doesn't require any database migrations or configuration changes.

Bug Fixes

Framework Fixes

• Database Testing Fix: Resolved an issue with database testing when creating new Strapi projects using the strapi new command. This ensures that database connectivity is properly verified during project initialization, preventing potential setup problems.

New Features

Documentation Improvements

• API Token Guide: Added comprehensive documentation on how to use API tokens in Strapi, making it easier for developers to implement token-based authentication.

• Enhanced Migration Guide: The migration guide from beta.17 to beta.18 has been expanded to include:

  • Database migration instructions specifically for components
  • Instructions for copying index.html and production.html files during the migration process

Security Updates

No security fixes were included in this release.

Performance Improvements

No specific performance improvements were included in this release.

Impact Summary

This release has a low impact on existing Strapi installations as it primarily focuses on documentation improvements and fixing a specific issue with the project creation process. The API token guide enhances developer understanding of authentication mechanisms in Strapi, while the database testing fix ensures more reliable project initialization. The expanded migration guide provides clearer instructions for users upgrading between beta versions, particularly regarding component database migrations. Overall, this release improves the developer experience without introducing breaking changes or requiring significant adaptation.

Full Release Notes