v1.0.0

Adoption of Semantic Versioning

• Note: Shared Crypto follows semantic versioning. The version number is incremented based on the type of changes made to the shared crypto binaries. The version number is not tied to the version of the underlying crypto provider.
• Note: Prior to adopting semantic versioning in the 1.0.0 release, the version number followed a form of YYYY.MM.PATCH. The 1.0.0 release was the first to use semantic versioning and proceeds any of those versions.

Breaking Change - Standalone MM Integration

Two options are now provided for Standalone MM. It is important to select the option based on the Standalone MM core used on your platform:

• StandaloneMmPkg - Use STANDALONEMM_CRYPTO_SERVICES
• MmSupervisorPkg - Use STANDALONEMM_MMSUPV_CRYPTO_SERVICES

Since the MM Supervisor currently does not support AARCH64, only a X64 MM Supervisor Standalone MM binary is available. A platform should not have both STANDALONEMM_CRYPTO_SERVICES and STANDALONEMM_MMSUPV_CRYPTO_SERVICES set to non-NONE values.

What's Changed

• Use OpenSSL intrinsic lib for all archs by @makubacki in #96
• [Release/202311] CryptoBinPkg: Update EDKII_CRYPTO_VERSION from 17 to 18 by @Flickdm in #102
• generate_cryptodriver: Add useful versioning to shared crypto binaries by @makubacki in #105
• Remove temporary files from the published binary files by @kenlautner in #106
• Add PR test gates for Mu_Crypto_Release by @kenlautner in #104
• Update MU_BASECORE to include cherrypick subhook submodule by @Flickdm in #112
• Fix OpensslPkg CI by @makubacki in #114
• Add Non-MM Supervisor Standalone MM X64 Binary by @makubacki in #113
• Update instructions for semantic versioning by @makubacki in #115

Full Changelog: v2023.12.2...v1.0.0