native-tls 0.2.17: compile error - Protocol::Tlsv13 not covered in openssl backend

[Iwijn]

Summary

native-tls v0.2.17 fails to compile with a non-exhaustive patterns error in src/imp/openssl.rs. The Protocol::Tlsv13 variant exists in the Protocol enum but is not handled in the openssl backend's match arms.

Error

error[E0004]: non-exhaustive patterns: `Some(Protocol::Tlsv13)` not covered
   --> native-tls-0.2.17/src/imp/openssl.rs:61:22
    |
 61 |     options |= match min {
    |                      ^^^ pattern `Some(Protocol::Tlsv13)` not covered

error[E0004]: non-exhaustive patterns: `Some(Protocol::Tlsv13)` not covered
   --> native-tls-0.2.17/src/imp/openssl.rs:75:22
    |
 75 |     options |= match max {
    |                      ^^^ pattern `Some(Protocol::Tlsv13)` not covered

Reproduction

cargo install cargo-tarpaulin   # or any crate that depends on native-tls ^0.2

Fails because cargo resolves native-tls to 0.2.17 (the latest), which has this bug.

Environment

• native-tls: 0.2.17
• rustc: 1.93.0-nightly (c23ed3ef2 2025-11-23)
• OS: Linux (x86_64)

Workaround

Pin to native-tls ≤ 0.2.16, or use --locked when installing crates that depend on it (so their published Cargo.lock resolves to an older version).

Fix

The Protocol::Tlsv13 arm needs to be added to the min/max match blocks in src/imp/openssl.rs.

[SamW94]

If you're desperate, running cargo install <package> --locked will get around this (as long as the package has native-tls pinned to <0.2.16 in Cargo.lock of course).

[ctron]

Just ran into the same issue.

[pboft]

Urgent - please revert that breaking change.

   Compiling native-tls v0.2.17
...
error[E0004]: non-exhaustive patterns: `Some(Protocol::Tlsv13)` not covered
   --> /home/<name>/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/native-tls-0.2.17/src/imp/openssl.rs:61:22
    |
 61 |     options |= match min {
    |                      ^^^ pattern `Some(Protocol::Tlsv13)` not covered
    |
note: `Option<Protocol>` defined here
   --> /home/<name>/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/option.rs:600:1
    |
600 | pub enum Option<T> {
    | ^^^^^^^^^^^^^^^^^^
...
608 |     Some(#[stable(feature = "rust1", since = "1.0.0")] T),
    |     ---- not covered
    = note: the matched value is of type `Option<Protocol>`
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown
    |
 73 ~         },
 74 +         Some(Protocol::Tlsv13) => todo!()
    |

error[E0004]: non-exhaustive patterns: `Some(Protocol::Tlsv13)` not covered
   --> /home/pbower/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/native-tls-0.2.17/src/imp/openssl.rs:75:22
    |
 75 |     options |= match max {
    |                      ^^^ pattern `Some(Protocol::Tlsv13)` not covered
    |
note: `Option<Protocol>` defined here
   --> /home/pbower/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/option.rs:600:1
    |
600 | pub enum Option<T> {
    | ^^^^^^^^^^^^^^^^^^
...
608 |     Some(#[stable(feature = "rust1", since = "1.0.0")] T),
    |     ---- not covered
    = note: the matched value is of type `Option<Protocol>`
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown
    |
 81 ~         },
 82 +         Some(Protocol::Tlsv13) => todo!()
    |

For more information about this error, try `rustc --explain E0004`.
error: could not compile `native-tls` (lib) due to 2 previous errors
warning: build failed, waiting for other jobs to finish...

Breaks production pipelines for downstream native-tls users of common libraries like : hyper-tls, redis, reqwest, sentry, tokio-native-tls, tokio-tungstenite, and tungstenite.

[Kolzodev712]

Addressed here if not solved already by someone else => #371
If anyone is free to review, would be great.

[davidgomesdev]

@pboft afaik you can override it in your Cargo.toml

native-tls = { version = "0.2.16" }

[pboft]

@pboft afaik you can override it in your Cargo.toml

native-tls = { version = "0.2.16" }

Is breaking pipelines upstream that are using latest semver compatible version.

Was this a Claude release? Can we revert it completely urgently ?

[ptcodes]

Temporary fix:

cargo update -p native-tls --precise 0.2.16

[LordZeuss]

Temporary fix:

cargo update -p native-tls --precise 0.2.16

Thank you! I am trying to use dioxus for the first time, and was wondering what happened. Turns out I choose the exact wrong moment as this dependency is blowing up.

[sempervictus]

to quote ET - "ouch" this is one of those libs that just trashes CIs. Please push a fixed rev (and coverage) ASAP because i'm sure we're not the only ones having to pause CI/CD flows