Release Notes > 5.41.0
Upgrade From 5.40.x to 5.41.0
Learn how to upgrade Webiny from 5.40.x to 5.41.0.
- how to upgrade Webiny from 5.40.x to 5.41.x
Make sure to check out the 5.41.0 changelog to get familiar with the changes introduced in this release.
Step-by-Step Guide
1. Upgrade Webiny Packages
Upgrade all Webiny NPM packages by running the following command:
Once the upgrade has finished, running the yarn webiny --version
command in your terminal should return 5.41.0.
2. Run the Upgrade Command
The next step is to run the project upgrade:
3. Breaking Changes❗
This release contains a couple of breaking changes that might affect your project.
3.1 Updated Node.js to the Version 20
We have updated the Node.js
version, which runs the code which gets deployed, to v20
.
Users should update their development machines and CI deployments to use Node.js
v20
.
Node.js
v22
is not supported as AWS Lambda runtime, so we did not go that far yet. As soon as AWS Lambda supports Node.js
v22
, we will update the runtime to that version, and users will get notified about it in the upgrade docs.
We have also updated the engines
field in the package.json
file to reflect this change.
3.2 Updated Typescript to the Version 4.9.5
We have updated the Typescript
version to v4.9.5
.
We also removed the typescript
package from the package.json
resolutions
, so we are not forcing all the packages to use the same version.
If you notice any issues with your project because of that, feel free to add version 4.9.5
into the resolutions
field in your package.json
file.
Unfortunately, updating the Typescript to the v5+
is a bit problematic because we need to change our build process. It will probably be done for Webiny v5.42.0
release.
3.3 Multiple Roles and Teams Assignments - Changes on theIdentity
Interface
With the introduction of the Multiple Roles and Teams Assignments (#4198), we’ve done the following changes to the Identity
interface:
group
property was deprecated, users should usegroups
insteadteam
property was deprecated, users should useteams
instead
These changes were done because a Webiny user can now be assigned to multiple roles and teams. Which is also why the new properties accept an array of strings (instead of a single string, as it was before).
Note that the outlined changes are essentially only relevant for users who are using custom IdP implementations, like Okta or Auth0. This is because the Identity
interface and its group
and team
properties are only utilized in the context of custom IdP implementations. So, in case you’re using a custom IdP implementation, make sure to update your code accordingly. For updated code examples, revisit the Okta or Auth0 integration articles.
Note that if you continue using the old group
and team
properties, your code will still work. However, we recommend updating your code to use the new groups
and teams
properties, as the old properties will be removed in a future release.
4. Deploy Your Project
Proceed by redeploying your Webiny project:
dev
or staging
.