Alex McKinney

@timostamm is this still relevant / do we have any plans for this? I noticed the docs outline the steps manually ([link](https://docs.buf.build/bsr/remote-generation/js#private)).

Using a major semantic version prefix isn't supported right now, but you can omit the `v1` component entirely to always get the latest version. It's technically possible that we would...

Keep an eye out for the new `plugin` key introduced [here](https://github.com/bufbuild/buf/pull/1277). We don't plan to support the semantic version upgrade experience you're suggesting yet (i.e. behavior like `^v1` or `^v1.1`...

The reason we don't have a stdin input type is because there isn't an obvious answer for the default stdin input type in `buf`'s case. In most cases, `buf` operates...

If we add this to `buf.yaml`, I imagine we'd be limited to supporting standard license types like `MIT` and `Apache-v2.0`. However, if we want users to be flexible with what...

As discussed offline / for posterity, we'll want to wait to merge this one until we're totally prepared for this to go out in the next release.

> @amckinney Afaics there are no breaking changes, any reason we don't want to merge this as a "hidden" feature, instead of having to build from this branch (for our...

Don't forget to add an entry to the `CHANGELOG.md`!

Thanks for the report - I'd actually argue that the formatter should respond with a non-zero exit code here so that it matches the behavior of `buf lint`. We generally...

It's been several days, so I'll close this one out (we don't plan to make any changes here).