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

Support for publishing/importing pre-release packages of Protocol Buffer files #250

Open
heatonmatthew opened this issue Jun 24, 2024 · 2 comments
Labels
complexity::high Issues or ideas that are highly complex. require discussion and may affect backwards compatibility component::cli Everything related to the buffrs cli datamodel Changes related to the Datamodel priority::critical This should have been done yesterday type::epic An epic change. This is going to make a big difference to buffrs as a product. type::idea Rough idea or proposal for buffrs

Comments

@heatonmatthew
Copy link

I'm wondering if you have any thoughts or desires to support pre-release versions in the Protocol Buffer packages?

In our code workflows, we tend to align many of our Protocol Buffer packages with the source for the server software implementing a the defined service. As such, we routinely publish pre-release versions of the software for testing in the ecosystem before a given release of that version.

For example, when NuGet versioning a feature to release:

  • 4.1.7-alphamatthew-pro0004
  • 4.1.7-rc0002
  • 4.1.7

I don't think that buffrs currently supports pre-release suffixes like this but it might be helpful. Presumably, #205 would be a precursor to this also? Do you see any benefit in this?

Thanks.

@mara-schulke
Copy link
Contributor

Hi, there are currently plans to implement proper version resolution which would likely contain the support for this! I unfortunately don't have a ETA on this as of right now!

@mara-schulke mara-schulke added datamodel Changes related to the Datamodel component::cli Everything related to the buffrs cli priority::critical This should have been done yesterday complexity::high Issues or ideas that are highly complex. require discussion and may affect backwards compatibility type::epic An epic change. This is going to make a big difference to buffrs as a product. type::idea Rough idea or proposal for buffrs labels Jul 5, 2024
@heatonmatthew
Copy link
Author

I checked out the code this afternoon and it looks like this one has been implemented (i.e semver crate supports it and it looks integrated everywhere). I ran a few tests and it seemed to behave as I'd expect using a build of the main branch.

Does this sound right to you? Would it help if I looked at updating the documentation?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity::high Issues or ideas that are highly complex. require discussion and may affect backwards compatibility component::cli Everything related to the buffrs cli datamodel Changes related to the Datamodel priority::critical This should have been done yesterday type::epic An epic change. This is going to make a big difference to buffrs as a product. type::idea Rough idea or proposal for buffrs
Projects
None yet
Development

No branches or pull requests

2 participants