Buf(1)

πŸ“¦
version 1.75.0 Β· 3 versions
, in arch rolling

πŸ’… Buf(1) β€” the manual, but make it group chat

ok so real talk: this is a page from the Buf manual (that's the (1) bit, bestie β€” section 1, general commands, iykyk ✨). And the specific page is all about buf-registry-sdk-version. Buckle up, it's a short one and honestly kinda iconic πŸŽ€


✨ NAME ✨

buf-registry-sdk-version β€” literally resolves a module and plugin reference into one very specific Generated SDK version. That's the whole job. She's focused πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

buf registry sdk version --module= --plugin= [flags]

ok so that's the shape of it β€” you give her a module, you give her a plugin, and [flags] is where the extra options live πŸ‘‘


🌸 DESCRIPTION 🌸

This command returns the version of the Generated SDK for the module and plugin you hand it. That's it. That's the whole personality. ✨

Here are the examples, no cap, exactly as they were given to me:

Get the version of the eliza module and the go plugin for use with the Go module proxy. (yes bestie, the Go module proxy β€” it's giving practical πŸ’€πŸ’–)

$ buf registry sdk version --module=buf.build/connectrpc/eliza --plugin=buf.build/protocolbuffers/go
v1.33.0-20230913231627-233fca715f49.1

Use a specific module version and plugin version. (pinning BOTH sides, highkey meticulous of you 🫢)

$ buf registry sdk version --module=buf.build/connectrpc/eliza:233fca715f49425581ec0a1b660be886 --plugin=buf.build/protocolbuffers/go:v1.32.0
v1.32.0-20230913231627-233fca715f49.1

see how the output version picks up the plugin version you pinned? the vibes are immaculate, the facts are untouched 🌈


πŸ’œ OPTIONS πŸ’œ

  • -h, --help[=false] β€” help for version. the classic. the icon. she explains herself πŸŽ€
  • --module="" β€” The module reference to resolve. default is the empty string, so actually pass it, bestie 😭
  • --plugin="" β€” The plugin reference to resolve. also defaults to empty string. also actually pass it πŸ™ˆ
fr fr, both of those default to "" β€” these flags want real values from you, they're not gonna guess 🫢

πŸ‘‘ OPTIONS INHERITED FROM PARENT COMMANDS πŸ‘‘

these ones are hand-me-downs from the parent command, and they still absolutely slay:

  • --debug[=false] β€” Turn on debug logging (env BUF_DEBUG). defaults to false, flips on when you're in your detective era πŸ”
  • --log-format="color" β€” The log format text, color, json ⟨env BUF_LOG_FORMAT⟩. default is "color" because aesthetics matter πŸ’…
  • --timeout=0s β€” The duration until timing out, setting it to 0 means no timeout (env BUF_TIMEOUT). default is 0s, i.e. she will wait for you forever, main character energy β³πŸ’€

🌈 SEE ALSO 🌈

  • buf-registry-sdk(1) β€” the parent, the source, the one who raised her 🫢 go read that one too

⭐ HISTORY ⭐

2026-10-22 β€” Auto generated by spf13/cobra. no human wrote this history entry, a machine did it, and honestly? respect πŸ€–βœ¨


k that's the page bestie!! mwah πŸ’–

sign-off szn: this whole thing was Auto generated by spf13/cobra, dated 2026-10-22, and it lives in the Buf(1) manual β€” so when you cite it, that's the source, the version date, and the manual name all accounted for πŸŽ€βœ¨ no cap, go resolve some SDK versions, ily πŸ¦‹

πŸ“¦ where this page comes from