Merged
Conversation
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
| option.WithHeader("X-Stainless-Lang", "cli"), | ||
| option.WithHeader("X-Stainless-Package-Version", Version), | ||
| option.WithHeader("X-Stainless-Runtime", "cli"), | ||
| option.WithHeader("X-Stainless-CLI-Command", cmd.FullName()), |
There was a problem hiding this comment.
rgarcia
approved these changes
Feb 11, 2026
| "github.com/urfave/cli/v3" | ||
| ) | ||
|
|
||
| var imagesCreate = cli.Command{ |
Contributor
There was a problem hiding this comment.
i assume this and others will be reborn in a follow up?
also random but i'd really like an "images rm"
Contributor
Author
There was a problem hiding this comment.
Yes, and I'm curious what will happen with the from-sdk generator PR after this
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
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.


Moving away from using Stainless for CLI gen
Note
Medium Risk
Moderate risk because it removes large chunks of command surface area and request/flag encoding code, which can break existing CLI workflows and integrations even though the remaining changes are mostly build/metadata related.
Overview
Removes the Stainless-generated CLI surface area (e.g.
health,images,instances,volumes,ingresses) and the supporting request plumbing (internal/apiform,internal/apiquery,internal/requestflag, plusflagOptionsand other generated helpers), leaving only the hand-written command set.Updates version handling to be build-time overridable via GoReleaser ldflags (now targeting
pkg/cmd.version), with a runtime fallback that derives a dev-friendly version from module semver tags or VCS revision, and customizes--versionoutput formatting. Also drops Stainless-specific request headers and removes the.stats.ymlgeneration artifact andgo-yamldependency.Written by Cursor Bugbot for commit 5ba4a32. This will update automatically on new commits. Configure here.