Skip to content

releasing.md

Latest commit

 

History

History
52 lines (38 loc) · 1.5 KB

releasing.md

File metadata and controls

52 lines (38 loc) · 1.5 KB
Raw

Release Process

This project publishes source through Git and downloadable binaries through GitHub Releases.

First GitHub Push

Create an empty public repository named code-context-engine, then connect this local repository:

git remote add origin https://github.com/acc-c/code-context-engine.git
git push -u origin main

Do not initialize the GitHub repository with another README, license, or .gitignore; those files already exist locally.

Publish a Version

  1. Update the workspace version and CHANGELOG.md.
  2. Run the full quality gates.
  3. Commit the release preparation.
  4. Create and push an annotated tag.
git tag -a v0.1.0 -m "Code Context Engine v0.1.0"
git push origin main
git push origin v0.1.0

The Release GitHub Actions workflow builds context on Windows, Linux, and macOS. It publishes a .zip archive for Windows and a .tar.gz archive for Linux and macOS, plus one matching .sha256 checksum file per runner operating system and architecture.

Verify the GitHub Release

After the workflow completes:

  1. Confirm all operating-system archives are attached to the release.
  2. Verify one checksum.
  3. Extract one archive on a clean machine or temporary directory.
  4. Run context --help.
  5. Run the MCP initialize and tools/list smoke test from MCP setup.

Failed Releases

If a release workflow fails, do not overwrite the tag. Fix the problem, update the version, and publish a new tag unless the failed tag and release were never made public.