Skip to content

[Protocol] generate Rust crate and publish to crates.io#3488

Draft
Herklos wants to merge 1 commit into
devfrom
feature/add-protocol-rs-publish
Draft

[Protocol] generate Rust crate and publish to crates.io#3488
Herklos wants to merge 1 commit into
devfrom
feature/add-protocol-rs-publish

Conversation

@Herklos

@Herklos Herklos commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

Generate the octobot-protocol Rust crate from the shared openapi.json and publish it to crates.io on push to dev/master, mirroring the npm flavor.

Generate the octobot-protocol Rust crate from the shared openapi.json and
publish it to crates.io on push to dev/master, mirroring the npm flavor.

- generate:rust now outputs to crates/octobot_protocol_rs (root Cargo.toml
  workspace globs packages/*/crates/*), suppresses docs, and runs a new
  postprocess step that regenerates lib.rs + models/mod.rs and repairs an
  openapi-generator invalid enum variant.
- hand-maintained Cargo.toml (octobot-protocol / lib octobot_protocol) +
  README, kept across regeneration by the clean script.
- generic matrix-driven publish-crate CI job using crates.io OIDC trusted
  publishing with an idempotent version check; wired into notify.
- tests job: split has_rust_backend (maturin) from has_rust so the pure-Rust
  crate is not run through pytest --backend=rust.
- gitignore the root Cargo.lock.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@Herklos Herklos self-assigned this Jun 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant