Skip to content

OpenAPI generation fails on cosmos-sdk v0.53.4: can't resolve OpenAPI name for .cosmos.autocli.v1.ModuleOptions #4873

@chenrui333

Description

@chenrui333

Environment

  • Ignite CLI: 29.6.0 (Homebrew formula)
  • OS: Linux
  • Command under test: ignite s chain mars

What happened

In Homebrew CI, ignite scaffold chain fails during OpenAPI generation with:

failed to generate openapi spec /home/linuxbrew/.cache/Homebrew/go_mod_cache/pkg/mod/github.com/cosmos/cosmos-sdk@v0.53.4/proto, probably you need to exclude some proto files: error while running command go tool github.com/bufbuild/buf/cmd/buf generate /home/linuxbrew/.cache/Homebrew/go_mod_cache/pkg/mod/github.com/cosmos/cosmos-sdk@v0.53.4/proto/cosmos/autocli/v1/query.proto --template=/var/tmp/ignite-test-20260210-166350-8tr8mi/mars/proto/buf.gen.swagger.yaml --output=/var/tmp/gen-openapi-module-spec3599396910 --error-format=json --log-format=json: Failure: plugin go tool github.com/grpc-ecosystem/grpc-gateway/v2/protoc-gen-openapiv2: can't resolve OpenAPI name from ".cosmos.autocli.v1.ModuleOptions"
: exit status 1

Reproduction

ignite s chain mars

CI reference

Expected

ignite s chain mars should complete scaffolding without failing OpenAPI generation for cosmos/autocli/v1/query.proto.

If this is a known upstream breakage, guidance on the recommended workaround for downstream packagers would help (e.g. exclude list, pinned dependency/tooling version, or CLI flag).

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions