Allow pq-experimental for v4 back-compat

Author: kornelski

Cargo.toml

@@ -8,7 +8,7 @@ members = [
 resolver = "2"
 
 [workspace.package]
-version = "5.0.0-alpha.2"
+version = "5.0.0-alpha.3"
 repository = "https://github.com/cloudflare/boring"
 edition = "2021"
 
@@ -19,9 +19,9 @@ tag-prefix = ""
 publish = false
 
 [workspace.dependencies]
-boring-sys = { version = "5.0.0-alpha.2", path = "./boring-sys" }
-boring = { version = "5.0.0-alpha.2", path = "./boring" }
-tokio-boring = { version = "5.0.0-alpha.2", path = "./tokio-boring" }
+boring-sys = { version = "5.0.0-alpha.3", path = "./boring-sys" }
+boring = { version = "5.0.0-alpha.3", path = "./boring" }
+tokio-boring = { version = "5.0.0-alpha.3", path = "./tokio-boring" }
 
 bindgen = { version = "0.72.0", default-features = false, features = ["runtime"] }
 bitflags = "2.9"

boring/Cargo.toml

@@ -25,6 +25,10 @@ fips = ["boring-sys/fips"]
 # **DO NOT USE** This will be removed without warning in future releases.
 legacy-compat-deprecated = []
 
+# **DO NOT USE** This will be removed without warning in future releases.
+# PQ is always enabled. This feature is a no-op, only for backwards compatibility.
+pq-experimental = []
+
 # Enables Raw public key API (https://datatracker.ietf.org/doc/html/rfc7250)
 # This feature is necessary in order to compile the bindings for the
 # default branch of boringSSL. Alternatively, a version of boringSSL that