release-kit 0.1.0

A canonical release workflow: a technology-agnostic method, per-technology bindings, and the rk CLI that lands and serves them.
Documentation 
1
2
3
4
5
6
7
8
9
10
11

# Bindings

One document per technology: the four [diff-surface](../method/05-diff-surface.md) answers, the concrete commands, and the registry facts the spine cannot state. Each binding assumes the whole [method](../method/README.md); nothing here repeats it.

| Binding               | Version file     | Bot            | Registry            | Artifacts           |
| --------------------- | ---------------- | -------------- | ------------------- | ------------------- |
| [Rust](./rust.md)     | `Cargo.toml`     | release-plz    | crates.io over OIDC | cargo-dist          |
| [Python](./python.md) | `pyproject.toml` | release-please | PyPI over OIDC      | wheels and sdist    |
| [Bash](./bash.md)     | `VERSION`        | git-cliff      | none                | `make dist` tarball |

The deterministic files each binding lands live under `snippets/<technology>/` in this repository and reach a project through `rk init --tech <technology>`. The tool versions they assume are pinned once, in the versions registry at the repository root, readable with `rk versions`.