Skip to content

Updating fuselage packages

Jump to bottom
Hugo Costa edited this page Sep 15, 2022 · 4 revisions

Update yarn.lock

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 action with the PR's number that handles the release.

Additionally, you can check the latest next version on the NPM Website.

To make sure your just-merged fuselage PR is being used at your local branch or in your Pull Request from the project RocketChat/Rocket.Chat, 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.

If you want to updated them all, just run this command:

yarn up @rocket.chat/emitter@next @rocket.chat/fuselage-polyfills@next @rocket.chat/fuselage-toastbar@next @rocket.chat/fuselage-tokens@next @rocket.chat/fuselage-ui-kit@next @rocket.chat/css-in-js@next @rocket.chat/styled@next @rocket.chat/fuselage@next @rocket.chat/fuselage-hooks@next @rocket.chat/icons@next @rocket.chat/logo@next @rocket.chat/memo@next @rocket.chat/message-parser@next @rocket.chat/onboarding-ui@next @rocket.chat/string-helpers@next @rocket.chat/ui-kit@next @rocket.chat/layout@next

⚠️ After running the yarn up command, discard the changes made on package/livechat because this package it's is not prepared yet to receive libraries updates

Once this command finishes running, if everything goes accordingly, you might notice your yarn.lock file has been updated. This update should be committed, so next time someone else runs yarn, the correct, updated package will be installed.

⚠️ This is especially true if your PR needs QA. The QA environment won't update packages properly if the yarn.lock changes aren't committed For every RocketChat/fuselage change that needs a QA, it's necessary to create a Pull Request in RocketChat/Rocket.Chat running the yarn up commands presented.

Clone this wiki locally