This page is out of date - check out the TinaCMS GitHub for the latest contribution information
Tina has three main branches:
The flow of changes therefore looks like:
fix-some-bug
=>master
=>next
=>latest
The process happens over a week:
next
is merged into latest
; then latest
is published to npmmaster
is merged into next
; then next
is published to npmnext
and latest
and the published accordingly.master
automatically triggers a
canary
release.With this process:
canary
releases for early testingThe general release process looks like this:
lerna
to generate CHANGELOG files automatically from our commit messages.react-tinacms
is changed
then tinacms
will get get a patch update with only the dependency updated. Make sure to install lerna-clean-changelog-cli
:npm i -g lerna-clean-changelogs-cli
@tinacms
organizationThe exact commands vary slightly depending on the type of release being made.
npm run build
lerna version \ --conventional-commits \ --conventional-prerelease \ --no-push \ --allow-branch next \
-m "chore(publish): prerelease"
lcc ** && git commit -am "chore: clean changelogs"
lerna publish from-package --dist-tag next
git push && git push --tags
npm run build
lerna version \ --conventional-commits \ --conventional-graduate \ --no-push \ --allow-branch next \
-m "chore(publish): graduation"
lcc ** && git commit -am "chore: clean changelogs"
lerna publish from-package
git push && git push --tags
npm run build
lerna version \ --conventional-commits \ --no-push \ --allow-branch master \
-m "chore(publish): release"
lcc ** && git commit -am "chore: clean changelogs"
lerna publish from-package
git push && git push --tags
© TinaCMS 2019–2024