f961a6da81
* chore(server): various useful multiregion changes from comments pr * hopefully fixing CI? * test fix * more test fixes?? * more test fixes.. * plz work ;(((( * revert multiregion on by default |
||
---|---|---|
.. | ||
deployment | ||
README.md | ||
build.sh | ||
check_version.py | ||
common.sh | ||
config.yml | ||
get_version.sh | ||
is_draft.sh | ||
multiregion.test-ci.json | ||
publish.sh | ||
publish_cloudflare_pages.sh | ||
publish_fe2_sourcemaps.sh | ||
publish_helm_chart.sh | ||
update_helm_documentation.sh |
README.md
Publishing and Releasing
Publishing Images
Images are published based on the logic in should_publish.sh, and the regex provided in PUBLISHABLE_TAGS
and PUBLISHABLE_BRANCHES
environment variables in the CircleCI config.
Currently images are published in the following conditions:
- any commit to branches named
main
,hotfix.*
, oralpha.*
- any branch tagged with semver
major.minor.patch
(regex:^[0-9]+\.[0-9]+\.[0-9]+$
)
Creating a release
The easiest way to create a new release is to Create a New Release on Github, and in the 'Select A Tag' dropdown create a new tag with the appropriate semver increment.
Ideally the target branch should be main
.