- what does it mean to upgrade Webiny
- how to upgrade Webiny to a specific version
Whenever you’re doing an upgrade, we recommended that you first deploy your changes into one of your pre-production environments, like
staging. Once you’ve confirmed everything works as expected, then you can start planning moving into the production.
If you have any additional questions or concerns, please don’t hesitate to send us a message via our community Slack channel.
When planning an upgrade, always check if there’s a dedicated guide for your specific Webiny version. All the guides are located in the menu on the left, for example: 5.9.0 → 5.10.0. If you see the guide that matches your versions, follow it. It may contain additional steps to upgrade your Webiny project, as sometimes there are changes in project file organization, project configs, etc.
If there’s no dedicated article, upgrades are as easy as upgrading all the
@webiny/* packages to the desired version.
yarn up command updates all your
package.json files in all workspaces across the project. Learn more about it in the official documentation.
Once that’s done, you can deploy your project.
You should never skip versions (major or minor) as each upgrade can contain additional manual steps that need to be taken. The steps will always be listed in upgrade guides.
Please note that it’s possible to skip only patch versions. For example, if you are currently on version
5.30.0 and wish to upgrade to version
5.32.0. You can upgrade from
5.31.0 and then from
5.32.0 by skiping the patch versions within the
5.31.0 series, such as
Yes, once you’ve completed the upgrade steps, in order to actually see the new features and fixes online, you need to re-deploy you project. Which project applications you need to re-deploy? It depends on the released fixes and features, but the easiest approach would be just to deploy the entire project, using the
yarn webiny deploy command.
Additionally, before you re-deploy the changes into the production environment, it’s recommended that you re-deploy the changes into one of your test or preview environments first.
Differences between these two versions are so vast that it’s simply impossible to do the upgrade. If you’re interested in migrating your existing project to v5, unfortunately, you will have to recreate your existing content in a new v5 project, either manually, or by writing your own custom migration scripts.
In your terminal of choice and in your project root, run the following command:
Additionally, the version is also shown in the deployed Admin Area React application, at the bottom of the main menu: