Skip to content

Publishing

Jump to bottom
Alex LaFroscia edited this page Apr 4, 2018 · 5 revisions

Publishing the packages should be done with lerna. Both packages should maintain the same version number at all times1. I think that this makes it easier for people to ensure they're using the right version when the Ember add-on wrapper and underlying library have the same version.

To make a "beta" publish, the command looks something like:

yarn lerna publish --repo-version 2.0.0-beta.0 --npm-tag=next

For a "latest" publish, the command would leave off npm-tag

yarn lerna publish --repo-version 2.0.0
  1. This is actually not exactly right now, while the 2.0.0 release is still a WIP. The latest of the Ember add-on is the beta, since there is no other version, while the latest of testdouble-qunit is the last non-pre-release version. However, the version numbers of next are the same.
Clone this wiki locally