Channels

CodeCharter publishes all releases through a single distribution channel: Stable.

Stable

Verified releases approved for production use.

• Version format: SemVer (currently in the 1.0.x line, e.g. 1.0.12).
• Contractual guarantee: no breaking changes within a major version, see Versioning.

Recommendation for your CI: pin to a specific Stable version and plan updates deliberately.

Pinning a version

Manual pull: the download endpoint requires your portal API key as a bearer token. If your subscription has expired, the endpoint responds with HTTP 402.

# Latest version
curl -L -H "Authorization: Bearer $CODECHARTER_API_KEY" \
    -o codecharter.tar.gz \
    https://codecharter.tools/api/v1/cli/linux-x64/latest

# Specific version
curl -L -H "Authorization: Bearer $CODECHARTER_API_KEY" \
    -o codecharter.tar.gz \
    https://codecharter.tools/api/v1/cli/linux-x64/1.0.12

The version selector accepts latest, an exact version such as 1.0.12, or a prefix such as 1 or 1.0 — with or without a leading v. The newest release matching the selector is served.

GitHub Action: the version input takes a published image tag such as latest, v1, or v1.0.12 (or local to run a binary already present on the runner). The default is latest, which follows the newest published build; pin a version tag when you want reproducible CI runs.

- uses: bochmann-software/codeguard@v1
  with:
    version: v1.0.12
    api-key: ${{ secrets.CODECHARTER_API_KEY }}

Channel by use case

Release history

New Stable releases are documented in the full Changelog in the wiki.