ci: publish reviewed endpoint-libs version bumps

.github/workflows/rust.yml

@@ -104,3 +104,19 @@ jobs:
       - uses: rustsec/audit-check@69366f33c96575abad1ee0dba8212993eecbe998 # v2.0.0
         with:
           token: ${{ secrets.GITHUB_TOKEN }}
+
+  publish:
+    if: >-
+      github.event_name == 'push' &&
+      github.ref == 'refs/heads/master' &&
+      contains(github.event.head_commit.modified, 'Cargo.toml')
+    needs: [test, clippy_check, format_check, security_audit]
+    runs-on: ubicloud-standard-2
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4
+      - uses: dtolnay/rust-toolchain@4360b52568e2003a75bf9bc1d59f33a8e3fc893c # stable
+      - name: Publish a reviewed version bump
+        env:
+          CARGO_REGISTRY_TOKEN: ${{ secrets.CARGO_REGISTRY_TOKEN }}
+        run: cargo publish --registry crates-io

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "endpoint-libs"
-version = "3.0.1"
+version = "3.0.2"
 edition = "2024"
 authors = ["Veon <dveonloch@protonmail.com>"]
 description = "Launch MCP services fast: describe endpoints once in RON, and endpoint-gen generates the Rust models, docs and MCP tool schemas that this crate serves over WebSocket RPC, with roles and typed errors built in."

README.md

@@ -513,27 +513,13 @@ A `load_config` utility parses a JSON config file, defaulting to `etc/config.jso
 
 ## Releasing
 
-Releases are managed with [`cargo-release`](https://github.com/crate-ci/cargo-release) and [`git-cliff`](https://github.com/orhun/git-cliff). Both must be installed:
+Put the `Cargo.toml` version bump in a pull request. After merge, the Rust
+workflow waits for tests, clippy, formatting, and the security audit, then runs
+`cargo publish` when the package version changed in that `master` update. The
+workflow uses the repository's `CARGO_REGISTRY_TOKEN` secret.
 
-```sh
-cargo install cargo-release git-cliff
-```
-
-To cut a release:
-
-```sh
-./scripts/release.sh [--skip-bump] <patch|minor|major>
-```
-
-The script will:
-1. Run `cargo release --execute <level>` — bumps the version in `Cargo.toml`, updates the deps.rs badge in this README, regenerates `CHANGELOG.md`, and commits everything as `chore(release): vX.Y.Z`.
-2. Open your `$EDITOR` with the auto-generated tag notes (from `git-cliff`) for review.
-3. Create an annotated tag using the edited notes as the tag body (shown as GitHub Release notes).
-4. Push the commit and tag.
-5. Prompt whether to publish to crates.io.
-
-To preview what `cargo-release` would do without making changes:
+To verify the package locally without publishing:
 
 ```sh
-cargo release patch  # omit --execute for a dry run
+cargo publish --dry-run
 ```