Releasing

Jump to bottom

Piper edited this page Oct 13, 2021 · 2 revisions

We aim to release a new version of Climate Connect weekly.

Currently, we use a two branching method (develop and master).

We have a weekly reminder to merge develop into master, which should automatically deploy changes to prod.

Release steps

Review changes from develop into master
Push a tag commit, updating relevant version files (e.g. package.json) and git tag the new release
Merge to master

Join the Slack for the most up to date discussion on Climate Connect work.