Skip to content

Question about the beta status and plans for stable release #325

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

Open
DersuSaakyan opened this issue Mar 4, 2025 · 2 comments
Open

Question about the beta status and plans for stable release #325

DersuSaakyan opened this issue Mar 4, 2025 · 2 comments
Labels
Question Questions about the project or libraries

Comments

@DersuSaakyan
Copy link

First of all, thank you for your work on Protovalidate!
I noticed that the current version is still marked as beta. Could you share any insights on why it's still in beta and if there are any plans for a stable release? Are there specific features or issues that need to be resolved before reaching stable status?

Looking forward to your response. Thanks in advance!

Best regards,
Derenik Sahakyan

@rodaine
Copy link
Member

rodaine commented Mar 4, 2025

Hi, @DersuSaakyan!

The protovalidate project and the implementations we've created are all considered pre-v1.0, that is to say still beta. We have not come out of beta into a stable release as we wanted to test and use protovalidate extensively first to make sure its API is as helpful and ergonomic as possible. This means we may need to introduce breaking changes to its API surface both in the proto options as well as the libraries' API surfaces that would normally never be permitted in a post-v1.0 release.

All that said, we are currently and actively working on reaching a v1.0 state. Some things that we'd like to have ready for the v1.0:

  • protovalidate-es complete and open sourced. Probably our most requested feature in this space. The current dev work is moving along nicely and it's also catching bugs in our other implementations. You can see the additions to our conformance tests in the protovalidate repo that have come out it.

  • standardized CEL library. Right now, we're somewhat trusting of the CEL implementations standard functions, and for the custom functions we've added their implementations vary, particularly in edge cases. We want to make sure that every implementation of these functions is consistent across the board.

  • cmake/bzlmod support. To accommodate the widest breadth of build systems used by the community and our customers.

I don't have a more formal roadmap for you at this time, but the end is in sight! 😅

[moving to main protovalidate repo, as this question is more general]

@rodaine rodaine transferred this issue from bufbuild/protovalidate-java Mar 4, 2025
@rodaine rodaine pinned this issue Mar 4, 2025
@rodaine rodaine added the Question Questions about the project or libraries label Mar 4, 2025
@DersuSaakyan
Copy link
Author

Hi @rodaine

Thank you for the update!
I'm eagerly looking forward to the stable release, as I’d love to integrate protovalidate into my projects once it's ready. Keep up the great work, and I’ll be keeping an eye on the progress!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Question Questions about the project or libraries
Projects
None yet
Development

No branches or pull requests

2 participants