A reference guide on how to do releases of the VF monorepo's tools and components.
- We publish to npm with Lerna
- Versions in
vf-core - Updating component versions
- select the
developbranch- reminder: we don't use
master
- reminder: we don't use
- see a list of changed packages
lerna changed
- test publish
yarn run lerna:test
- publish to npm
yarn run lerna:publish
- update the expected new tag version to
/tools/vf-component-library/src/site/_data/siteConfig.js- see last tag
git describe --abbrev=0 --tags
- see last tag
- generate an update
yarn run releasenotes- format and review the newly made file at
tools/vf-component-library/src/site/updates
- commit and push changes to the
developbranch- commit message in a format of:
Component release 20200330-01
- commit message in a format of:
- add a tag"
- see last tag
git describe --abbrev=0 --tags - add a semantic versioned tag
git tag -a v2.4.10 -m 'Release of precompiled CSS, JS, assets' - Why like this?
- We do not add tags per individual component version, Lerna needs a named tag to see what has changed. This way we get one tag per release "bundle" avoiding tag spamming in the release history.
- Trigger a deploy to the CDN (i.e.
v2.4.5-rc.1) https://assets.emblstatic.net/vf/v2.4.10/css/styles.css
- see last tag
- push the tag
git push origin --tags
- add release notes to the tag and link to the new blog post
lerna lslist all packages known to lernalerna ls --since af04cb2alist all changed packages since a commit (sadly not combinable with lerna publish)lerna diffall changes since last publishlerna changedall packages changed