f210d9b749
* feat(projects): add project regions, default to null * feat(multiregion): add projectRegion Db client lookup logic * feat(multiregion): add project region repositories and caching * feat(multiRegion): db initialization and get project db client * feat(docker-compose): add second db for regions testing * feat(multiRegion): initialize region with pubs and subs working * fix(multiRegion): get region client even if it was registered in another pod * feat(workspaces): create workspace resolver split * feat: update server region metadata * feat(projects): rewrite project creation * feat(multiRegion): getRegionDb * fix(workspaces): get projects now can retur null * feat(multiRegion): make local multi region DB-s work * feat: set d efault workspace region * CR changes * tests * feat(multiRegion): bind region properly * fe update * test fixes * feat(multiRegion): automatically create aiven extras plugin * ci(postgres): use published postgres with aiven extras * fix(multiRegion): roll back the aiven extras migration, there is a better way * tests fix * fix(billing): we do not need to add a seat, if the workspace is on a plan, but has no sub --------- Co-authored-by: Kristaps Fabians Geikins <fabis94@live.com> |
||
|---|---|---|
| .. | ||
| deployment | ||
| README.md | ||
| build.sh | ||
| check_version.py | ||
| common.sh | ||
| config.yml | ||
| get_version.sh | ||
| is_draft.sh | ||
| 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.