You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a PR is created/updated in the mbedtls-framework repo, we currently run all.sh components of mbedtls-3.6 and development associated with the framework as resulting from the PR. We should do the same with TF-PSA-Crypto development.
Result of the CI will still be only informative, even if it fails the PR can be merged. It's intended use is to check that when we do not aim to make a backward-compatible change for some (if not all) mbedlts/TF-PSA-Crypto branches, the change is actually backward compatible for those branches.
When a PR is created/updated in the mbedtls-framework repo, we currently run all.sh components of mbedtls-3.6 and development associated with the framework as resulting from the PR. We should do the same with TF-PSA-Crypto development.
Result of the CI will still be only informative, even if it fails the PR can be merged. It's intended use is to check that when we do not aim to make a backward-compatible change for some (if not all) mbedlts/TF-PSA-Crypto branches, the change is actually backward compatible for those branches.
Probably this depends on Mbed-TLS/TF-PSA-Crypto#116.
The text was updated successfully, but these errors were encountered: