Bump version to Mbed TLS 2.21.0 #370
No reviewers
Labels
No labels
api-spec
bug
CLA requested
CLA valid
compliance
DO NOT MERGE
duplicate
enhancement
feature branch
good first issue
HEADER FORMATTING ISSUE
help wanted
Information
invalid
Jira status: AWAITING REVIEW
Jira status: CLOSED
Jira status: DONE
Jira status: IN PROGRESS
Jira status: IN REVIEW
Jira status: OPEN
Jira status: REOPENED
Jira status: RESOLVED
mirrored
mirror internally
needs: backports
needs: ci
needs: design review
needs: preceding PR
needs: review
needs: work
notabug
open for community contribution
Product Backlog
question
ready for merge
security
stale
type: bug
type: enhancement
type: question
web pages
wontfix
writing
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-ARMmbed/mbed-crypto!370
Loading…
Reference in a new issue
No description provided.
Delete branch "update-version-2.21.0"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Not bumping the SO version:
The API/ABI breaking changes only affect internal APIs (changes related to
mbedtls_asn1_traverse_sequence_of()) and to PSA, which is from the point of view of Mbed TLS is an unstable API.Don't we need to update the crypto submodule and the changelog first?
This is mbed-crypto, it does not have it's own version reporting, it reports the Mbed TLS version it is included in. I wanted to update the version here first so that we can do a single submodule update on Mbed TLS instead of two.
LGTM. To be immediately followed by updating the submodule and updating the library version in mbedtls.
The CI failures are mostly an issue in Mbed OS, with one exception, which is an ssl-opt.sh DTLS spurious resend. All of these are known issues unrelated to this PR.