New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publish new tag #17
Comments
@mitchellh, I am excited about the upcoming release of the new tag. |
bumping this thread if a new tag could be created 🙏 @mitchellh |
Would be great to get a new release since this is published as an official Buf remote plugin and their policy is to only publish stable releases. |
I'd be happy to lend a hand in maintaining this repository. Indeed we package and publish this plugin to the Buf Schema Registry as a community plugin given its popularity. https://buf.build/community/mitchellh-go-json |
@mfridman Given the lack of response and the popularity of the project, any chance Buf would fork and maintain this plugin? |
Bump. Bump. @mfridman Can we get a new tag of this with the optional fields please? |
I'm afraid I cannot create tags within this repository and I'm also a bit wary of forking to avoid fragmentation. It'd be useful to understand @mitchellh's direction for this project. Although we package and publish popular plugins on the BSR (https://buf.build/plugins), we don't have the cycles to maintain all of them. The best I can do is offer to help lightly maintain this repository. |
We got the answer we were looking for, https://gist.github.com/mitchellh/90029601268e59a29e64e55bab1c5bdc Kudos to Mitchell for his work. I'll be forking this project to https://github.com/mfridman/protoc-gen-go-json and pick up maintenance there, I'll file an issue with next steps. |
This PR adds a new community plugin which supersedes the existing one mitchellh/protoc-gen-go-json. I've disabled further updates of that plugin, and will mark it deprecated shortly. This should also resolve the upstream issue folks have been asking about. mitchellh/protoc-gen-go-json#17
Any chance we could get a new tag, maybe
v1.2.0
?There's been a few notable changes, 2263edb...4990573
The text was updated successfully, but these errors were encountered: