Kristaps Fabians Geikins
bde148f286
* wip * some extra fixes * stuff kinda works? * need to figure out mocks * need to figure out mocks * fix db listener * gqlgen fix * minor gqlgen watch adjustment * lint fixes * delete old codegen file * converting migrations to ESM * getModuleDIrectory * vitest sort of works * added back ts-vitest * resolve gql double load * fixing test timeout configs * TSC lint fix * fix automate tests * moar debugging * debugging * more debugging * codegen update * server works * yargs migrated * chore(server): getting rid of global mocks for Server ESM (#5046) * got rid of email mock * got rid of comment mocks * got rid of multi region mocks * got rid of stripe mock * admin override mock updated * removed final mock * fixing import.meta.resolve calls * another import.meta.resolve fix * added requested test * nyc ESM fix * removed unneeded deps + linting * yarn lock forgot to commit * tryna fix flakyness * email capture util fix * sendEmail fix * fix TSX check * sender transporter fix + CR comments * merge main fix * test fixx * circleci fix * gqlgen bigint fix * error formatter fix * more error formatting improvements * esmloader added to Dockerfile * more dockerfile fixes * bg jobs fix
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.