Every artifact releases the same way: bump its version, merge, and CI (or one manual step) publishes it. You can never re-release an existing version — always bump to a new one.
New feature → minor. Bug fix → patch. Breaking change → major.
A wire-protocol change (ahnlich/types or protos/) is lockstep: bump types, client-rs, db, ai, and python together, plus node if its generated code changed. types and client-rs publish together to crates.io, so both must bump.
- Bump the version file.
- Open a PR and merge to
main. - CI tags and publishes automatically. Confirm the new version on the registry.
- Bump
ahnlich/<name>/Cargo.toml, then merge. This keeps the binary's self-reported--versioncorrect; it does not create a tag. - Create a GitHub Release with tag
bin/<name>/<version>and hand-written notes. release.ymlbuilds the binaries and pushes Docker images (db and ai only; cli has no image).
- Bump
charts/<name>/Chart.yamlversion, then merge. charts-release.ymlpackages and pushes the changed charts tooci://ghcr.io/deven96/charts.- ArtifactHub reindexes automatically.
First-time setup only: run the Publish Helm charts workflow manually, set the three ghcr packages to Public, and register oci://ghcr.io/deven96/charts on artifacthub.io.
- Clients publish only when the watched version line changes in a merged PR.
- Binaries publish only from a GitHub Release, never a bare tag.
- ghcr package pages always show the repo README — per-image READMEs are a GitHub limitation, not a bug.
types / client-rs / client-py / client-node 0.4.0 · db 0.3.0 · ai 0.4.0 · cli 0.3.0 · charts 0.1.0
