Skip to content

Commit

Permalink
fix: Try fixing the Buf publish step.
Browse files Browse the repository at this point in the history
  • Loading branch information
@stephenh
stephenh committed May 2, 2023
1 parent 007d12f commit 47ef176
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions .github/workflows/build.yml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -90,8 +90,8 @@ jobs:
- name: Build Plugin image
run: docker build
--file ts-proto.Dockerfile
--tag plugins.buf.build/${{ secrets.BUF_USERNAME }}/ts-proto:v${{ needs.release.outputs.release_version }}-0
--tag plugins.buf.build/community/stephenh-ts-proto:v${{ needs.release.outputs.release_version }}-0

This comment has been minimized.

Sign in to view

Copy link
@mfridman

mfridman May 2, 2023 •
edited
Loading

Contributor

Hey @stephenh, we've made some changes to Buf plugins. Given how popular your plugin was, we added it as a "Buf-managed" plugin 🎉 . It's available here (the community organization is managed by Buf, that's why you couldn't push to it):

https://github.com/bufbuild/plugins/tree/main/plugins/community/stephenh-ts-proto

Every time you tag a semver version in this repository, it'll get synced within a few hours to buf.build automatically with no further action from you. Buf-managed plugins are available at buf.build/plugins

And your plugins is available at: buf.build/community/stephenh-ts-proto

Let me know if you have any questions and if you want to chat directly hop over to our Buf Slack workspace.

For some background, there's a Blog post that outlines these changes:

And a migration guide is available here:
"."

- name: Push to Buf Registry
run: docker push plugins.buf.build/${{ secrets.BUF_USERNAME }}/ts-proto:v${{ needs.release.outputs.release_version }}-0
run: docker push plugins.buf.build/community/stephenh-ts-proto:v${{ needs.release.outputs.release_version }}-0

0 comments on commit 47ef176

Please sign in to comment.