There is one release in https://github.com/Mbed-TLS/TF-PSA-Crypto/releases (manual tag tf-psa-crypto-1.0.0-beta, GitHub automatic tag v1.0.0-beta). There will be another one when 1.0.0 comes out (we aren't planning a second beta).
For packaging purposes, note that it's likely that during the early days of 1.x/4.x we'll make simultaneous releases where Mbed TLS 4.x includes TF-PSA-Crypto 1.x and does not work with another version. But our objective at some point during the 4.x series is to make the projects independent, where Mbed TLS 4.x could work with TF-PSA-Crypto 1.y, and eventually (but don't hold your breath) could work with an independent implementation of the PSA Crypto API.
-- Gilles
On 31/07/2025 23:27, Andrea Pappacoda wrote:
On Tue Jul 29, 2025 at 5:19 PM CEST, Gilles Peskine wrote:
The vVERSION tags are automatically created by GitHub when we create a release. The mbedtls-VERSION and now tf-psa-crypto-VERSION tags follow the historical pattern that the project has been using, and have the benefit of reflecting the project name. I believe that they're equivalent: I don't think we've ever had a reason to make them point to different commits.
The thing to watch is a new release on GitHub.
Hi Gilles! The thing is: tf-psa-crypto has no GitHub releases (yet), just tags. So these must have been created manually, right?
Thank you for maintaining these packages!
Thank you for maintaining LTS branches :)
Bye!