yujunjun/strapi
1
0
Fork 0
mirror of https://github.com/strapi/strapi.git synced 2025-11-01 18:33:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add 3.2 migration guide and improve migration guides homepage

Browse Source 
Signed-off-by: Alexandre Bodin <bodin.alex@gmail.com>
This commit is contained in:
Alexandre Bodin 2020-10-06 15:15:12 +02:00
parent 7a8d820376
commit 698dbc6c99
2 changed files with 39 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
docs/v3.x/migration-guide/README.md
View File

@ -1,15 +1,25 @@
# Migrations guides
Please also refer to the following [documentation](../guides/update-version.md) for a better understanding of how to update your project
Please also refer to the following [documentation](../guides/update-version.md) for a better understanding of how to update your project.
## Guides
## Instructions
When upgrading you will need to follow every migration guide between your current version and the one you are upgrading to.
**Example**
If you were upgrading from the `3.0.0-beta.19.5` to `3.2.0`, here are the following guides you would have to follow:
- Migration guide from beta.19.4+ to beta.20.
- Migration guide from beta.20+ to 3.0.0.
- Migration guide from 3.0.x to 3.1.x.
- Migration guide from 3.1.x to 3.2.x.
## V3 guides
- [Migration guide from 3.1.x to 3.2.x](migration-guide-3.1.x-to-3.2.x.md)
- [Migration guide from 3.0.x to 3.1.x](migration-guide-3.0.x-to-3.1.x.md)
## Migrating from Beta ?
Read the [Migration guide from beta.20+ to stable](migration-guide-beta.20-to-3.0.0.md).
## Beta guides
- [Migration guide from beta.15 to beta.16](migration-guide-beta.15-to-beta.16.md)

23
docs/v3.x/migration-guide/migration-guide-3.1.x-to-3.2.x.md Normal file
View File

@ -0,0 +1,23 @@
# Migration guide from 3.1.x to 3.2.x
**Make sure your server is not running until the end of the migration**
:::warning
If you are using **extensions** to create custom code or modifying existing code, you will need to update your code and compare your version to the new changes on the repository.
<br>
Not updating your **extensions** can break your app in unexpected ways that we cannot predict.
:::
## Disclaimer
This version requires some migration in the following cases:
- You are using a `published_at` field in some of your models.
- You followed the [Scheduled publication guide](../guides/scheduled-publication.md) and used a `published_at` field.
Otherwise you can follow the basic [version update guide](../guides/update-version.md).
## Migration
The new **Draft & Publish** feature will add a `published_at` field to your **content types** if you enable the feature.
If you have been using this field name on your **content types** you will need to first rename or delete it before being able to use the feature on those **content types**.