Commit 917e45d
Merge #729
729: Let users chose what crypto backend of jsonwebtoken to use r=curquiza a=LukasKalbertodt
# Pull Request
## What does this PR do?
`jsonwebtoken` was updated to 10.x in #717, but there, `aws_lc_rs` was unconditionally enabled. While I also prefer that backend, this library should probably leave the choice to users. I think my PR achieves exactly that, while still defaulting to aws_lc_rs.
## PR checklist
Please check if your PR fulfills the following requirements:
- [x] Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)?
- [x] Have you read the contributing guidelines?
- [x] Have you made sure that the title is accurate and descriptive of the changes?
Thank you so much for contributing to Meilisearch!
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
## Summary by CodeRabbit
* **Chores**
* Updated jsonwebtoken dependency to v10.2.0.
* Enhanced WASM32 support by expanding UUID handling.
* **New Features**
* Added selectable JWT cryptographic backend feature flags (AWS-LC and Rust-Crypto).
* Default feature set now includes AWS-LC cryptographic support.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Co-authored-by: Lukas Kalbertodt <[email protected]>2 files changed
+4
-3
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
33 | 33 | | |
34 | 34 | | |
35 | 35 | | |
36 | | - | |
| 36 | + | |
37 | 37 | | |
38 | 38 | | |
39 | 39 | | |
| |||
42 | 42 | | |
43 | 43 | | |
44 | 44 | | |
45 | | - | |
| 45 | + | |
46 | 46 | | |
47 | 47 | | |
48 | 48 | | |
| 49 | + | |
| 50 | + | |
49 | 51 | | |
50 | 52 | | |
51 | 53 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
6 | 6 | | |
7 | 7 | | |
8 | 8 | | |
9 | | - | |
10 | 9 | | |
11 | 10 | | |
12 | 11 | | |
| |||
0 commit comments