Updating fuselage packages

We maintain @rocket.chat/fuselage-* packages within the @next version. This means that a PR in the fuselage monorepo will get a new release version after it's merged for a while. This new version release can be assured in the Actions tab in the repository. There you will find an action with the PR's number that handles the release. Additionaly you can check the latest next version in the NPM Website.

To make sure your just-merged fuselage PR is installed, run the following:

• yarn up @rocket.chat/<PACKAGE_NAME>@next -- <PACKAGE_NAME> being substituted by the name of the package you just updated.

You must do this to every package you want to update to the next version. Once this command finishes running, if everything goes accordingly, you might notice your yarn.lock file has updated. This update should be commited, so next time someone else runs yarn, the correct, updated package will be installed.

This is specially true if your PR needs QA. The QA environment won't update packages properly if the yarn.lock changes aren't commited