In order to release one should:
- pre-publishing steps
- login to the npm registry
- publish packages
- commit updated versions
- tag the published version
Before publishing it's important to make sure that theia-apps builds against 'next'. Else we will have problems with "latest" after publishing
-
Make sure that there is no pending build on Theia master, otherwise a new "next" version might be published while we validate the current "next".
-
Go in the theia-apps repo here and identify the latest commit. There should be an icon next to it; either a red X or a green checkmark. Click on it to go the Travis page. There re-trigger the build. We need to make sure that at least the various "next" builds pass. If it doesn't, it needs to be fixed before continuing.
Follow this instruction to login to the npm registry with a user account.
If you don't have an account contact Theia organization to request one.
yarn run publish
This command will rebuild all packages, test them, publish to npm and bump versions.
If publishing of an individual package failed then publish it with npm publish from its root after resolving outstanding issues.
git add *
git commit -m "publish v${published.version}" -s
git push origin HEAD
The version picked during package publishing should be used as ${published.version}.
For example, if you picked 0.1.0 as a version then you should run:
git add *
git commit -m "publish v0.1.0" -s
git push origin HEAD
Warning: Continue only if all packages have been published successfully. Otherwise work on resolving issues and publishing failed packages.
git tag v${published.version}
git push origin v${published.version}
The version picked during package publishing should be used as ${published.version}.
For example, if you picked 0.1.0 as a version then you should run:
git tag v0.1.0
git push origin v0.1.0