# Migration guide from alpha.13.1 to alpha.14

Here are the major changes:

  • New configuration of the content manager
  • GraphQL Aggregation Feature
  • Email confirmation and block user feature

Useful links:


💡 TIP

Feel free to join us on Slack (opens new window) and ask questions about the migration process.


# Getting started

Install Strapi alpha.14 globally on your computer. To do so run npm install strapi@3.0.0-alpha.14 -g.

When it's done, generate a new empty project strapi new myNewProject (don't pay attention to the database configuration).


# Update node modules

Update the Strapi's dependencies version (move Strapi's dependencies to 3.0.0-alpha.14 version) of your project.

Run npm install strapi@3.0.0-alpha.14 --save to update your strapi version.


# Update the Admin

💡 TIP

If you performed updates in the Admin, you will have to manually migrate your changes.

Delete your old admin folder and replace it with the new one.


# Update the Plugins

💡 TIP

If you did a custom update on one of the plugins, you will have to manually migrate your update.

Copy the fields and relations you had in your /plugins/users-permissions/models/User.settings.json and /plugins/users-permissions/config/jwt.json file in the new one.

Then, delete your old plugins folder and replace it with the new one.


# Reset your content manager settings

We added a new section in the content manager configurations. You are now able to customize the inputs displayed in the contribution view.

The stored data format has been changed. That is why you will have to delete in the core_store collection/table the entry with the key plugin_content-manager_schema.

Then take a ☕️ and take few minutes to reconfigure your stuffs.

Hope you will enjoy this new feature.


# Heroku setups

It's necessary to add DATABASE_NAME into your environment variable otherwise your app doesn't start.


That's all, you have now upgraded to Strapi alpha.14.