diff --git a/docs/releasing.md b/docs/releasing.md
index 6c2bda7..dbdc7c2 100644
--- a/docs/releasing.md
+++ b/docs/releasing.md
@@ -2,17 +2,17 @@
 
 Pushing a `v*` tag triggers the release workflow, which builds and publishes all artifacts: Rust binaries, VSIX, npm tarballs, LSP and tree-sitter outputs. Everything ships from a single tag.
 
-After CI finishes, two steps need manual action: publishing to crates.io and updating the Homebrew formula. The release script handles the full sequence.
+Publishing is fully automated: CI publishes the GitHub release, pushes the crates to crates.io (`publish-crates` job, via the `CARGO_REGISTRY_TOKEN` secret) and updates the Homebrew formula (`update-homebrew` job, via the `HOMEBREW_TAP_TOKEN` secret). No local crates.io login or tap checkout is needed.
 
 ## What goes where
 
 | Artifact | Destination | Automated? |
 |---|---|---|
-| Rust CLI binaries (4 platforms) | GitHub release | CI |
-| Rust crates (allium-parser, allium-cli) | crates.io | Release script |
+| Rust CLI binaries (5 targets) | GitHub release | CI |
+| Rust crates (allium-parser, allium-cli) | crates.io | CI |
 | VSIX | GitHub release | CI |
 | npm tarballs (allium-cli, allium-lsp, tree-sitter) | GitHub release | CI |
-| Homebrew formula | homebrew-allium tap | Release script |
+| Homebrew formula | homebrew-allium tap | CI |
 
 ## Running a release
 
@@ -20,23 +20,22 @@ After CI finishes, two steps need manual action: publishing to crates.io and upd
 ./scripts/release.sh 3.1.0
 ```
 
-This bumps versions, commits, tags, pushes, waits for CI, publishes to crates.io and updates the Homebrew tap. Pass `--dry-run` to preview each step without making changes.
+This bumps versions, commits, tags, pushes, and watches CI through to completion; CI publishes everything, including crates.io and the Homebrew tap. Pass `--dry-run` to preview each step without making changes.
 
 For major language version bumps, also follow the checklist in `docs/versioning.md`.
 
-Requires `gh` (GitHub CLI), `cargo` logged in to crates.io, and the `homebrew-allium` tap repo as a sibling directory.
+Requires `gh` (GitHub CLI) and `cargo` on the PATH.
 
 ## Manual steps (if not using the script)
 
 1. Bump versions: `./scripts/version-bump.sh <version>`
 2. Commit, tag and push: `git add -A && git commit -m "v<version>" && git tag v<version> && git push origin main --tags`
-3. Wait for CI to build and attach release artifacts
-4. Publish to crates.io: `cargo publish -p allium-parser && cargo publish -p allium-cli`
-5. Update Homebrew formula: `./scripts/update-homebrew-formula.sh <version>`
-6. Push the tap repo
+3. Watch CI build, attach and publish everything
+
+If the CI publish jobs fail, the fallbacks are `cargo publish -p allium-parser && cargo publish -p allium-cli` (needs a crates.io login) and `./scripts/update-homebrew-formula.sh <version>` plus a push of the `homebrew-allium` tap repo.
 
 ## When to release
 
 All core-tier packages share a major.minor version (see `docs/versioning.md`). Right now, every release cuts a single tag and publishes everything. This means a tree-sitter bugfix produces new Rust binaries even if nothing changed in the Rust crates, and vice versa.
 
-This is fine while the project is small. If the coupling becomes a problem, the natural split is separate tags per artifact group (e.g. `cli-v1.0.1`, `vscode-v0.3.0`), each triggering only its own CI job. That would also let the Homebrew update script run automatically as a post-release workflow step rather than requiring a manual invocation.
+This is fine while the project is small. If the coupling becomes a problem, the natural split is separate tags per artifact group (e.g. `cli-v1.0.1`, `vscode-v0.3.0`), each triggering only its own CI job.
diff --git a/docs/versioning.md b/docs/versioning.md
index f862a81..d3eb676 100644
--- a/docs/versioning.md
+++ b/docs/versioning.md
@@ -47,7 +47,7 @@ When the Allium language version changes (e.g. v2 → v3):
 1. Run `scripts/version-bump.sh <new-version>` to update all manifests.
 2. Update the language version statement at the top of this file.
 3. Update the "Compatibility" line in each external editor plugin README.
-4. After CI publishes the release, run `scripts/update-homebrew-formula.sh <version>` and push the tap repo. See `docs/releasing.md` for the full steps.
+4. CI publishes the release, the crates and the Homebrew formula automatically. See `docs/releasing.md` for the full steps.
 
 ## Rules