stack-orchestrator/docs/release-process.md
A. F. Dudley 5a1399f2b2 Apply pre-commit linting fixes
Fix trailing whitespace and end-of-file issues across codebase.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-20 23:16:44 -05:00

746 B

Release Process

Manually publish to github releases

In order to build, the shiv and wheel packages must be installed:

$ pip install shiv
$ pip install wheel

Then:

  1. Define CERC_GH_RELEASE_SCRIPTS_DIR
  2. Define CERC_PACKAGE_RELEASE_GITHUB_TOKEN
  3. Run ./scripts/tag_new_release.sh <major> <minor> <patch>
  4. Run ./scripts/build_shiv_package.sh
  5. Run ./scripts/publish_shiv_package_github.sh <major> <minor> <patch>
  6. Commit the new version file.

e.g.

$ export CERC_GH_RELEASE_SCRIPTS_DIR=~/projects/cerc/github-release-api/
$ export CERC_PACKAGE_RELEASE_GITHUB_TOKEN=github_pat_xxxxxx
$ ./scripts/tag_new_release.sh 1 0 17
$ ./scripts/build_shiv_package.sh
$ ./scripts/publish_shiv_package_github.sh 1 0 17