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

update to tfhe-rs 1.0.0 #164

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

update to tfhe-rs 1.0.0 #164

wants to merge 2 commits into from

Conversation

rudy-6-4
Copy link

No description provided.

@cla-bot cla-bot bot added the cla-signed label Feb 19, 2025
@rudy-6-4 rudy-6-4 force-pushed the rudy/chore/bump-tfhers branch from c208dbe to 9c2fdf9 Compare February 19, 2025 16:00
@rudy-6-4 rudy-6-4 force-pushed the rudy/chore/bump-tfhers branch from 9c2fdf9 to c0e688d Compare February 19, 2025 16:12
@rudy-6-4 rudy-6-4 requested a review from kc1212 February 19, 2025 16:12
Copy link
Contributor

@kc1212 kc1212 left a comment

Choose a reason for hiding this comment

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

LGTM!

@@ -0,0 +1,14 @@
# Dependency update

Choose a reason for hiding this comment

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

Thx for doing it! To be reviewed by @immortal-tofu please, later, even if the PR is merged

Copy link
Author

Choose a reason for hiding this comment

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

Yes there is also tkms to update to be fully tfhers 1.0.0.
And I can prerelease without merging.

Choose a reason for hiding this comment

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

And I can prerelease without merging.

Awesome, but at the same time, it means our release / prerelease are not done on "real commits"?

Copy link
Author

Choose a reason for hiding this comment

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

There are real commit but not on main branch (they will be when Clement is back). There's even a prerelease tag to be sure we track them. Is this an issue for you ? A release is often done on release branch BTW not on main, so if you have rc/fix etc it happens outside of main.

Choose a reason for hiding this comment

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

Eg, what happens if we squash commits? To me, we should do release on things which are merged, not on commits which are still in a PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants