|
1 | 1 | # Changelog |
2 | 2 |
|
| 3 | +## 11.0.0 (unreleased) |
| 4 | + |
| 5 | +- Add conversions between `Algorithm` and `KeyAlgorithm` |
| 6 | +- JWKs can now be created from `DecodingKey`s, creation from `EncodingKey` and `DecodingKey` supports Ed25519 now as well |
| 7 | +- BREAKING: `Algorithm` and `EllipticCurve` are now `non_exhaustive` |
| 8 | +- BREAKING: `Header.extras` is now a struct that allows for deserialization to any `T` |
| 9 | +- BREAKING: Implicit features resulting from optional crates have been removed |
| 10 | +- BREAKING: `Validation.insecure_disable_signature_validation` has been removed, use `dangerous::insecure_decode` instead |
| 11 | +- BREAKING: `EncodingKey.inner` has been renamed to `as_bytes`, `try_get_hmac_secret` has been removed |
| 12 | +- BREAKING: `DecodingKey.as_bytes` and `try_get_hmac_secret` have been removed, use `try_get_as_bytes` instead |
| 13 | + |
| 14 | +### Changes for `CryptoProvider`s |
| 15 | + |
| 16 | +- When constructing HMAC signers, the algorithm family must now be verified on construction |
| 17 | +- `JwkUtils` has been renamed to `KeyUtils` |
| 18 | + - `compute_digest` now returns a `Result<_>` |
| 19 | + - `extract_rsa_public_key_components` has been renamed to `rsa_pub_components_from_private_key` |
| 20 | + - `rsa_pub_components_from_public_key` has been added |
| 21 | + - `extract_ec_public_key_coordinates` has been renamed to `ec_pub_components_from_private_key` |
| 22 | + - `ed_pub_components_from_private_key` has been added |
| 23 | + |
3 | 24 | ## 10.4.0 (2026-05-11) |
4 | 25 |
|
5 | 26 | - Fix incorrect encoding for Ed25519 JWK thumbprints |
|
45 | 66 |
|
46 | 67 | - Supports deserialization of unsupported algorithms for JWKs |
47 | 68 |
|
48 | | - |
49 | 69 | ## 9.0.0 (2023-10-16) |
50 | 70 |
|
51 | 71 | - Update ring |
|
56 | 76 | - Update base64 |
57 | 77 | - Implement Clone for TokenData<T> if T impls Clone |
58 | 78 |
|
59 | | - |
60 | 79 | ## 8.2.0 (2022-12-03) |
61 | 80 |
|
62 | 81 | - Add DecodingKey::from_jwk |
63 | 82 | - Can now use PEM certificates if you have the `use_pem` feature enabled |
64 | 83 |
|
65 | | - |
66 | 84 | ## 8.1.1 (2022-06-17) |
67 | 85 |
|
68 | 86 | - Fix invalid field name on OctetKeyParameters |
|
76 | 94 |
|
77 | 95 | - Fix documentation of leeway |
78 | 96 |
|
79 | | - |
80 | 97 | ## 8.0.0 (2022-02-02) |
81 | | - |
| 98 | + |
82 | 99 | - Add EdDSA algorithm |
83 | 100 | - `sign`/`verify` now takes a `&[u8]` instead of `&str` to be more flexible |
84 | 101 | - `DecodingKey` now own its data |
|
115 | 132 | - Add support for PS256, PS384 and PS512 |
116 | 133 | - Add support for verifying with modulus/exponent components for RSA |
117 | 134 | - Update to 2018 edition |
118 | | -- Changed aud field type in Validation to `Option<HashSet<String>>`. Audience |
| 135 | +- Changed aud field type in Validation to `Option<HashSet<String>>`. Audience |
119 | 136 | validation now tests for "any-of-these" audience membership. |
120 | 137 | - Add support for keys in PEM format |
121 | 138 | - Add EncodingKey/DecodingKey API to improve performance and UX |
|
154 | 171 | ## 3.0.0 (2017-09-08) |
155 | 172 |
|
156 | 173 | ### Breaking changes |
| 174 | + |
157 | 175 | - Remove `validate_signature` from `Validation`, use `decode_header` instead if you don't know the alg used |
158 | 176 | - Make `typ` optional in header, some providers apparently don't use it |
159 | 177 |
|
|
0 commit comments