> To us, the CLI isn't an ancillary tool or a sideshow; we treat it like a full-fledged product. Our policy is to never make breaking changes within a version o

> To us, the CLI isn't an ancillary tool or a sideshow; we treat it like a full-fledged product. Our policy is to never make breaking changes within a version of the CLI. Now that buf has reached a stable 1.0, you can expect no breaking changes until v2.0—and we have no plans to ever release a v2.0. While we do intend to release new features in the buf CLI, you can expect total stability for all of the functionality that you rely on. > Reference: https://buf.build/blog/buf-cli-v1#meaning https://buf.build/blog/buf-cli-v1#meaning That is an interesting promise, a bit similar to Go’s v1 compatibility — https://go.dev/doc/go1compat https://go.dev/doc/go1compat However, I think using the word “[n]ever” is too strong here. No one can predict the future, so the chances of this being a false statement are high. They could have removed that paragraph and the general message would have been okay. Do not over-promise, instead, over-deliver. If they want to make backward compatible changes to the code, they can do so without promising to never release a v2.0, that is just silly.