Skip to content

Regenerate from the latest API - #41

Merged
mrcrgl merged 3 commits into
mainfrom
regenerate
Nov 4, 2026
Merged

mrcrgl merged 3 commits into
mainfrom
regenerate

Conversation

@origincloud-regenerate

@origincloud-regenerate origincloud-regenerate Bot commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor

Generated from origincloudhq/api@53fd91d51e3f (changes) by scripts/update.sh.

The MCP tools are moved to their newest commit, the Rust SDK to the commit they are built on, and API_REVISION to the API revision that commit was generated from.

If CI fails, the API uses something the generator (generator/) doesn't support yet, such as a method it can't make a command for; extend it on this branch.

…ming a resource

The help of every message's JSON flag said a resource name in it is
completed with --project and --zone, also for a message with no resource
name in it, on commands that have neither flag, such as billing's
organization-scoped create-billing-account. The sentence is now written
only when the message has a resource name of its own to complete.
Their SDK crates join the others at the same revision. Billing and
support get their group's help, as packages of several services, and the
README lists the groups and the hosts they call: observability the
region's front door, billing and support their regionless host.
@mrcrgl
mrcrgl merged commit 2eb38b3 into main Nov 4, 2026
6 checks passed
@mrcrgl mrcrgl mentioned this pull request Nov 4, 2026
@origincloud-regenerate
origincloud-regenerate Bot deleted the regenerate branch November 4, 2026 12:36
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