Skip to content
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

feat(proto): bump v1alpha1 -> v1 throughout #3751

Merged
merged 2 commits into from
Feb 7, 2024
Merged

Conversation

conorsch
Copy link
Contributor

@conorsch conorsch commented Feb 6, 2024

It's happening~~. We're marking the current suite of protobuf definitions as "v1", implying they're stable enough. Going forward, breaking changes must be made in a v2 directory.

We originally added the golang codegen to provide first-class support to
downstream integrators. This is no longer necessary, as those same
integrators, e.g. Strangelove, are performing their own codegen in the
respective repos. These codepaths in the Penumbra monorepo are unused
and largely unmaintained, so I'm culling them.

Refs #2184. Moots and therefore closes #2731.
It's happening~~. We're marking the current suite of protobuf
definitions as "v1", implying they're stable enough. Going forward,
breaking changes must be made in a v2 directory.

We're merging this change ahead of Testnet 65 (#3554).
@conorsch
Copy link
Contributor Author

conorsch commented Feb 7, 2024

CI is most definitely failing on the buf lint job:

proto-breaking-changes-v1

Yes, that's to be expected. Technically we could opt to preserve the v1alpha1 directories. In fact, that'd be the proper, blessed way to manage the proto defs, and we intend to do just that going forward. For now, though, we're making an intentionally Big Breaking Change to telegraph approaching v1 stability.

@conorsch conorsch merged commit 839f978 into main Feb 7, 2024
6 of 7 checks passed
@conorsch conorsch deleted the bump-protos-to-v1 branch February 7, 2024 01:08
conorsch added a commit to penumbra-zone/galileo that referenced this pull request Feb 7, 2024
conorsch added a commit that referenced this pull request Feb 7, 2024
conorsch added a commit that referenced this pull request Feb 7, 2024
TalDerei pushed a commit that referenced this pull request Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant