Hello,
Let me provide an update on the TF-M release status. Unfortunately, the release has been delayed due to last-minute change requests and some unexpected failures. The main factors contributing to the delay are:
1. PSA-Crypto v1.1 adoption - completed. 2. Moving MCUBoot back to the mainline from a forked version - one issue still remains. 3. Building RTX OS in tf-m-tests from source to align build options, particularly FPU support - there is a known issue with IAR toolchain, not blocking. 4. Heavy load on the OpenCI system, which has been blocking large nightly and release tests - this should now be resolved
The current plan is to run the release tests overnight and if everything looks good create a release candidate.
Best regards, and apologies for the inconvenience, Anton
From: Anton Komlev via TF-M tf-m@lists.trustedfirmware.org Sent: Tuesday, March 24, 2026 3:13 PM To: tf-m@lists.trustedfirmware.org Cc: nd nd@arm.com Subject: [TF-M] Upcoming TF-M Releases: v2.3.0 and v2.1.5
Hello,
We're preparing two new TF-M releases: v2.3.0 and v2.1.5. The current plan is to start on April 1st and target April 14th for v2.3.0. Among other improvements and fixes, v2.3.0 will be based on PSA-Crypto v1.1 expected on March 31st . We'll aim to test both releases in parallel with priority given to v2.3.0, while v2.1.5 will follow.
If there are any changes you'd like included in these releases, please ensure they are reviewed and merged by March 31st.
After successful testing of the v2.3.0 on platforms in OpenCI we plan to allow a one-week window for other platforms to validate and confirm correct operation. For v2.1.5, we don't expect platform-specific testing, assuming the changes are platform-independent and that CI coverage will be sufficient. However, please feel free to reach out if you have any concerns or anticipate any platform impact.
Thank you and best regards, Anton