[CI/Build][Rust Frontend] Retire Buf schema publishing (#57046)
Co-authored-by: OpenAI Codex <noreply@openai.com> Co-authored-by: Bugen Zhao <i@bugenzhao.com> Signed-off-by: Julien Darve <jdarve@NVIDIA.com>
This commit is contained in:
co-authored by
OpenAI Codex
Bugen Zhao
parent
22bb158c21
commit
fdfcbbcac7
+5
-10
@@ -2,14 +2,10 @@
|
||||
|
||||
This directory is the canonical source for vLLM's gRPC schema.
|
||||
|
||||
The schema is published to `buf.build/vllm-project/vllm`:
|
||||
|
||||
- A daily workflow publishes the latest Git `main` schema to the `nightly` label.
|
||||
- The workflow can be run manually to retry nightly publication.
|
||||
- Tags matching `v*` update the Buf `main` label and publish the corresponding release label.
|
||||
- Buf commits and generated SDK versions are immutable and can be pinned by consumers.
|
||||
|
||||
Repository setup requires a `BUF_TOKEN` GitHub Actions secret with permission to create and push the public Buf module. Register the Prost and Tonic generated SDKs for the `main` and `nightly` labels once so subsequent pushes generate them automatically.
|
||||
Schema updates are no longer published to the Buf Schema Registry. Rust consumers
|
||||
should use `vllm-proto` from crates.io; consumers in other languages can generate
|
||||
bindings from the `.proto` files in this directory. Buf still builds and lints
|
||||
the schemas on pull requests, including on forks.
|
||||
|
||||
## Rust crate
|
||||
|
||||
@@ -47,8 +43,7 @@ change PR. This check becomes available after the first manual publication.
|
||||
The `proto-crate.yml` workflow checks that the tag matches the crate version,
|
||||
verifies the package, and publishes it to crates.io.
|
||||
|
||||
Use `proto-v*` tags so they do not trigger Buf's `v*` release workflow. There is
|
||||
no scheduled crate publication. Pull requests and manual workflow runs only
|
||||
There is no scheduled crate publication. Pull requests and manual workflow runs only
|
||||
verify packaging, including on forks. Retry a failed release by rerunning its
|
||||
tag workflow; crates.io versions cannot be overwritten.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user