[experiment] Unify mbedtls dependants #27581
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
From https://github.com/Mbed-TLS/mbedtls/blob/development/BRANCHES.md, we should probably try to align mbedtls. This also readies us for the next LTS to be released late this year
Currently there are 19 requirements, where only a few are there by default. 7 in 2.x, the rest in 3.x, where major version releases break API compatibility.
Note that some of these requirements belong to the same recipe, which got upgraded support for mbedtls in newer versions
If not mentioned below, all changes here compile successfully for both shared/static in both the oldest and newest versions
As the 2.x branch does not get any more updates, we should try to converge on the latest if possible
For the 3.x branch, the current LTS is 3.6, so those that use it might want to see a version range for the patch releases of said version, and we should prefer that version in recipes above others unless necessary
This PR won’t create new missing binaries downstream as it modifies the revisions of all recipes that get their mbedtls version bumped
Would close #23762 mbedtls side, would still need to bump openssl, leaving it for that PR (There are probably more PRs that would be a subset of this one, I'll note them here once I find them, but they should already show up in the Related PR check)