История

Iain Sproat 9a28e467ba refactor(preview-service): conforms to design patterns, adds tests, and is typed (#2429 ) Co-authored-by: Kristaps Fabians Geikins <fabis94@live.com>		2024-09-04 13:06:23 +01:00
..
deployment	chore(CI): temporarily disable docker compose deployment test & other fixes for race condition in docker compose deployment test (#2553 )	2024-08-01 12:15:35 +01:00
README.md	build: Images should be built on every branch & commit with a PR (#856 )	2022-08-09 11:23:12 +01:00
build.sh	Circleci manual holds (#1152 )	2022-11-01 08:52:51 +00:00
check_version.py	chore(circleci): adds a note to common.sh regarding tags (#1991 )	2024-01-25 00:32:38 +00:00
common.sh	chore(circleci): remove python from common.sh and remove python dependency (#2102 )	2024-03-01 16:42:30 +00:00
config.yml	refactor(preview-service): conforms to design patterns, adds tests, and is typed (#2429 )	2024-09-04 13:06:23 +01:00
get_version.sh	chore(circleci): remove python from common.sh and remove python dependency (#2102 )	2024-03-01 16:42:30 +00:00
is_draft.sh	ci(frontend-2): docker image should not be built if github token is not set (#1687 )	2023-07-12 00:40:41 +01:00
publish.sh	feat: Frontend 2.0 MVP	2023-05-08 10:47:01 +03:00
publish_cloudflare_pages.sh	fix(circleci): fix whitespace in shell script (#2222 )	2024-04-19 17:12:38 +01:00
publish_fe2_sourcemaps.sh	fix: sourcemap upload command adjustment	2024-06-13 18:17:39 +03:00
publish_helm_chart.sh	fix help publish script, it shouldnt override local git configs (#1599 )	2023-06-13 11:48:08 +01:00
update_helm_documentation.sh	fix(circleci): documentation should only be committed if there are no changes (#1578 )	2023-05-16 13:42:49 +01:00

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.*, or alpha.*
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.