chore: comply with updated client requirements (v0.4.1) - #9
Merged
Conversation
Requirements-compliance pass against the updated orchestration client requirements (no OpenAPI spec change; still v2-2026-06-25T142310Z). - Publishing: the crates.io publish workflow now authenticates via Trusted Publishing (OIDC) using rust-lang/crates-io-auth-action@v1 and id-token: write, removing the stored CARGO_REGISTRY_TOKEN secret. GITHUB_TOKEN is still used only for the release tag and GitHub release. - Documentation: the disclaimer now states the client is "official, but experimental" (and AI-generated/maintained) consistently across src/lib.rs, README.md, docs/README.md, and the Cargo.toml description. - Version bumped 0.4.0 -> 0.4.1 (patch; no public API change) with a CHANGELOG entry.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Requirements-compliance pass against the updated orchestration client requirements. No OpenAPI spec change — the client remains based on
v2-2026-06-25T142310Z. The requirements were updated after the previous Rust client PR, so this brings the client back into full compliance. No public API surface changes, so this is a patch release (0.4.0→0.4.1).Changes
.github/workflows/rust-publish.yml) now authenticates via Trusted Publishing (OIDC) usingrust-lang/crates-io-auth-action@v1withid-token: write, instead of a storedCARGO_REGISTRY_TOKENsecret. The short-lived token is read into the publish step fromsteps.auth.outputs.tokenand auto-revoked at job end.cargo publish --dry-runneeds no credentials; the built-inGITHUB_TOKENis still used only for the release tag and GitHub release. (Requires a Trusted Publisher to be configured for the crate on crates.io: this repository + workflow file.)src/lib.rs,README.md,docs/README.md, and theCargo.tomldescription.0.4.0→0.4.1(patch — no public API change) with aCHANGELOG.mdentry.Verification
cargo fmt --all -- --check,cargo clippy --all-targets -- -D warnings,cargo build— all clean.review-clientprocess; all review items resolved.Generated by Claude Code