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

Remove "fips-no-compat", decouple "fips-compat" from "fips" #333

Merged
merged 1 commit into from
Mar 16, 2025

Conversation

cjpatton
Copy link
Collaborator

@cjpatton cjpatton commented Mar 14, 2025

Based on #332 (merge that first).
Partially addresses #196.

NOTE: This is an API breaking change.

Modify the "fips" feature so that it no longer implies "fips-compat".
The latter is no longer needed for recent builds of boringSSL; users who
need older builds will need to enable "fips-compat" explicitly.

Also, remove the "fipps-no-compat" feature, as it's now equivalent to
"fips".

@cjpatton cjpatton mentioned this pull request Mar 14, 2025
@cjpatton cjpatton force-pushed the cjpatton/fips-compat-decouple branch 2 times, most recently from 17b0986 to 9469c61 Compare March 14, 2025 18:24
@cjpatton cjpatton changed the title Decouple "fips-compat" from "fips" Remove "fips-no-compat", decouple "fips-compat" from "fips" Mar 14, 2025
@cjpatton cjpatton force-pushed the cjpatton/fips-compat-decouple branch from 9469c61 to 61303e3 Compare March 14, 2025 18:26
@cjpatton cjpatton force-pushed the cjpatton/update-bindings-for-latest-bssl branch from f73439d to b6708f8 Compare March 14, 2025 18:48
@cjpatton cjpatton force-pushed the cjpatton/fips-compat-decouple branch from 61303e3 to 1c90cfe Compare March 14, 2025 18:48
@cjpatton cjpatton marked this pull request as ready for review March 14, 2025 21:17
Base automatically changed from cjpatton/update-bindings-for-latest-bssl to master March 14, 2025 22:22
Modify the "fips" feature so that it no longer implies "fips-compat".
The latter is no longer needed for recent builds of boringSSL; users who
need older builds will need to enable "fips-compat" explicitly.

Also, remove the "fipps-no-compat" feature, as it's now equivalent to
"fips".
@cjpatton cjpatton force-pushed the cjpatton/fips-compat-decouple branch from 1c90cfe to 6f83572 Compare March 14, 2025 22:43
@cjpatton
Copy link
Collaborator Author

Rebased.

@kornelski kornelski merged commit 57307d7 into master Mar 16, 2025
23 checks passed
@cjpatton
Copy link
Collaborator Author

HI @kornelski, this shouldn't have been merged, at least not yet until we're ready to cut a release with API breaking changes. cc @rushilmehra

@kornelski
Copy link
Collaborator

Sorry I thought we're already on the way to 5.0

@cjpatton
Copy link
Collaborator Author

Sorry I thought we're already on the way to 5.0

I hope we are close, but Rushil asked to hold off.

I'm resubmitting this PR as a draft and will tag you both.

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.

2 participants