chore: fix swagger generation - #97
Merged
Merged
Conversation
giunatale
requested review from
giuliostramondo,
julienrbrt and
tbruyelle
as code owners
May 15, 2026 18:09
tbruyelle
approved these changes
May 15, 2026
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.
Restores
make proto-swagger-gen, which had been silently broken on this fork since the cosmosproto-builderimage droppedprotoc-gen-swaggerin favor ofprotoc-gen-openapiv2. The buf config still referenced the now-missing legacyplugin, so any invocation failed with:
Same migration cosmos-sdk did in cosmos#20448, adapted for this codebase.
Also cleanup non-existent modules and add modules that are included here instead.
This is an artifacts-related fix so intentionally not adding a CL entry.