Replies: 3 comments 2 replies
-
|
I am working on some proxy/remote/cache stuff right now. I will make a ticket to work on this right after that! |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
We've created tracking issues for this feature. Here's the full breakdown: Tracking Epic
Backend (artifact-keeper)
Web Frontend
Documentation
Dependency OrderThis will be prioritized after the current proxy/remote/cache work lands. Thanks for the suggestion @ddymko! |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
@ddymko if you want to do some testing for me you can pull the dev tags for the containers. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hey there 👋
Really digging this project super clean approach to artifact consolidation.
I’m currently using Buf Schema Registry to manage protobuf modules, but I’d love to consolidate everything (containers, Go modules, and protobuf schemas) into a single artifact system if possible.
Is there any interest or roadmap around supporting protobuf modules?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions