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

Bump crate version to 0.16.0 #899

Merged
merged 2 commits into from
Jan 12, 2024
Merged

Bump crate version to 0.16.0 #899

merged 2 commits into from
Jan 12, 2024

Conversation

tgeoghegan
Copy link
Collaborator

And while we're at it, update the version table in the README, as there are no remaining known blockers for VDAF-08 support.

And while we're at it, update the version table in the README, as there
are no remaining known blockers for VDAF-08 support.
@tgeoghegan tgeoghegan requested a review from a team as a code owner January 10, 2024 22:48
@tgeoghegan
Copy link
Collaborator Author

#839 is closed, so I think we have all of VDAF-08 done. Are there any other blockers to releasing prio 0.16.0 to crates.io? @cjpatton, @divergentdave: Any other API compatibility breaks we want to get in?

@cjpatton
Copy link
Collaborator

I have two changes to make:

  1. Add flp_validity_test to test-utils #898
  2. Upstream XofHmacSha256Aes128 from Daphne

I'll prepare these changes tomorrow.

README.md Outdated

[Build Status]: https://github.com/divviup/libprio-rs/workflows/ci-build/badge.svg
[actions]: https://github.com/divviup/libprio-rs/actions?query=branch%3Amain
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This URL is unused now.

@tgeoghegan
Copy link
Collaborator Author

I have two changes to make:

1. [Add `flp_validity_test` to test-utils #898](https://github.com/divviup/libprio-rs/issues/898)

2. Upstream XofHmacSha256Aes128 from Daphne

I'll prepare these changes tomorrow.

IIUC these two changes would add items to prio, which doesn't constitute an API break, right? But in any case, I'm not blocked on releasing 0.16.0 because I can make progress up in Janus by pulling in prio via git, so I'm happy to wait for those changes to come along before we do a release. Thanks, Chris!

@cjpatton
Copy link
Collaborator

I have two changes to make:

1. [Add `flp_validity_test` to test-utils #898](https://github.com/divviup/libprio-rs/issues/898)

2. Upstream XofHmacSha256Aes128 from Daphne

I'll prepare these changes tomorrow.

IIUC these two changes would add items to prio, which doesn't constitute an API break, right? But in any case, I'm not blocked on releasing 0.16.0 because I can make progress up in Janus by pulling in prio via git, so I'm happy to wait for those changes to come along before we do a release. Thanks, Chris!

I think the "test-util" change in #898 ended up being API breaking.

Copy link
Collaborator

@cjpatton cjpatton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Once we land #903 I think 0.16 is good to ship.

@tgeoghegan tgeoghegan merged commit df94db4 into main Jan 12, 2024
6 checks passed
@tgeoghegan tgeoghegan deleted the timg/release-0.16 branch January 12, 2024 17:34
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.

None yet

4 participants