v2023020000.2.0

What's Changed

• Update pip-requirements.txt @Javagedes (#230)
  
  Change Details

    ## Description

  Updates edk2-pytool-extensions and edk2-pytool-library to work with the latest commit of MU_BASECORE

  • Impacts functionality?
    • Functionality - Does the change ultimately impact how firmware functions?
    • Examples: Add a new library, publish a new PPI, update an algorithm, ...
  • Impacts security?
    • Security - Does the change have a direct security impact on an application,
      flow, or firmware?
    • Examples: Crypto algorithm change, buffer overflow fix, parameter
      validation improvement, ...
  • Breaking change?
    • Breaking change - Will anyone consuming this change experience a break
      in build or boot behavior?
    • Examples: Add a new library class, move a module to a different repo, call
      a function in a new library class in a pre-existing module, ...
  • Includes tests?
    • Tests - Does the change include any explicit test code?
    • Examples: Unit tests, integration tests, robot tests, ...
  • Includes documentation?
    • Documentation - Does the change contain explicit documentation additions
      outside direct code modifications (and comments)?
    • Examples: Update readme file, add feature readme file, link to documentation
      on an a separate Web page, ...

  How This Was Tested

  N/A

  Integration Instructions

  N/A
  

  
  

  ---

  
  

• Removed references to OpensslLib and changed all instances of BaseCryptLib to be the NULL implementation @kenlautner (#222)
  
  Change Details

    ## Description

  There are some references to BaseCryptLib and Openssl in package dsc files. In MU_BASECORE Openssl and it's BaseCryptLib implementations were removed so we need to update to using the NULL lib.

  • Impacts functionality?
    • Functionality - Does the change ultimately impact how firmware functions?
    • Examples: Add a new library, publish a new PPI, update an algorithm, ...
  • Impacts security?
    • Security - Does the change have a direct security impact on an application,
      flow, or firmware?
    • Examples: Crypto algorithm change, buffer overflow fix, parameter
      validation improvement, ...
  • Breaking change?
    • Breaking change - Will anyone consuming this change experience a break
      in build or boot behavior?
    • Examples: Add a new library class, move a module to a different repo, call
      a function in a new library class in a pre-existing module, ...
  • Includes tests?
    • Tests - Does the change include any explicit test code?
    • Examples: Unit tests, integration tests, robot tests, ...
  • Includes documentation?
    • Documentation - Does the change contain explicit documentation additions
      outside direct code modifications (and comments)?
    • Examples: Update readme file, add feature readme file, link to documentation
      on an a separate Web page, ...

  How This Was Tested

  Tested with CI

  Integration Instructions

  N/A
  

  
  

  ---

  
  

🚀 Features & ✨ Enhancements

• [CHERRY-PICK] RNG Related Commits (Needed for Arm RngDxe to Work) [Rebase \& FF] @makubacki (#233)
  
  Change Details

    ## Description

  ---

  [CHERRY-PICK] SecurityPkg/SecurityPkg.dec: Move PcdCpuRngSupportedAlgorithm to MdePkg

  In order to use PcdCpuRngSupportedAlgorithm in the MdePkg in a
  following patch and to avoid making the MdePkg dependent on another
  package, move PcdCpuRngSupportedAlgorithm to the MdePkg.

  As the Pcd is only used for AARCH64, place it in an AARCH64
  specific sections.

  Signed-off-by: Pierre Gondois [email protected]
  Reviewed-by: Liming Gao [email protected]
  Reviewed-by: Sami Mujawar [email protected]
  Acked-by: Ard Biesheuvel [email protected]
  Acked-by: Jiewen Yao [email protected]
  Tested-by: Kun Qin [email protected]
  (cherry picked from commit 65b5dd8)

  ---

  [CHERRY-PICK] SecurityPkg/RngDxe: Simplify Rng algorithm selection for Arm

  The first element of mAvailableAlgoArray is defined as the default
  Rng algorithm to use. Don't go through the array at each RngGetRNG()
  call and just return the first element of the array.

  Signed-off-by: Pierre Gondois [email protected]
  Reviewed-by: Sami Mujawar [email protected]
  Acked-by: Ard Biesheuvel [email protected]
  Acked-by: Jiewen Yao [email protected]
  Tested-by: Kun Qin [email protected]
  (cherry picked from commit ff7ddc0)

  ---

  [CHERRY-PICK] SecurityPkg/RngDxe: Use GetRngGuid() when probing RngLib

  BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=4151

  The EFI_RNG_PROTOCOL can rely on the RngLib. The RngLib has multiple
  implementations, some of them are unsafe (e.g. BaseRngLibTimerLib).
  To allow the RngDxe to detect when such implementation is used,
  a GetRngGuid() function was added in a previous patch.

  The EFI_RNG_PROTOCOL can advertise multiple algorithms through
  Guids. The PcdCpuRngSupportedAlgorithm is currently used to
  advertise the RngLib in the Arm implementation.

  The issues of doing that are:

  • the RngLib implementation might not use CPU instructions,
    cf. the BaseRngLibTimerLib
  • most platforms don't set PcdCpuRngSupportedAlgorithm

  A GetRngGuid() was added to the RngLib in a previous patch,
  allowing to identify the algorithm implemented by the RngLib.
  Make use of this function and place the unsage algorithm
  at the last position in the mAvailableAlgoArray.

  Signed-off-by: Pierre Gondois [email protected]
  Reviewed-by: Sami Mujawar [email protected]
  Acked-by: Ard Biesheuvel [email protected]
  Acked-by: Jiewen Yao [email protected]
  Tested-by: Kun Qin [email protected]
  (cherry picked from commit 19438cf)

  ---

  [CHERRY-PICK] SecurityPkg/SecurityPkg.dec: Move PcdCpuRngSupportedAlgorithm to MdePkg

  In order to use PcdCpuRngSupportedAlgorithm in the MdePkg in a
  following patch and to avoid making the MdePkg dependent on another
  package, move PcdCpuRngSupportedAlgorithm to the MdePkg.

  As the Pcd is only used for AARCH64, place it in an AARCH64
  specific sections.

  Signed-off-by: Pierre Gondois [email protected]
  Reviewed-by: Liming Gao [email protected]
  Reviewed-by: Sami Mujawar [email protected]
  Acked-by: Ard Biesheuvel [email protected]
  Acked-by: Jiewen Yao [email protected]
  Tested-by: Kun Qin [email protected]
  (cherry picked from commit 65b5dd8)

  ---

  • Impacts functionality?
    • Functionality - Does the change ultimately impact how firmware functions?
    • Examples: Add a new library, publish a new PPI, update an algorithm, ...
  • Impacts security?
    • Security - Does the change have a direct security impact on an application,
      flow, or firmware?
    • Examples: Crypto algorithm change, buffer overflow fix, parameter
      validation improvement, ...
  • Breaking change?
    • Breaking change - Will anyone consuming this change experience a break
      in build or boot behavior?
    • Examples: Add a new library class, move a module to a different repo, call
      a function in a new library class in a pre-existing module, ...
  • Includes tests?
    • Tests - Does the change include any explicit test code?
    • Examples: Unit tests, integration tests, robot tests, ...
  • Includes documentation?
    • Documentation - Does the change contain explicit documentation additions
      outside direct code modifications (and comments)?
    • Examples: Update readme file, add feature readme file, link to documentation
      on an a separate Web page, ...

  How This Was Tested

  • Mu Basecore CI.
  • Build QemuQ35Pkg and QemuSbsaPkg IA32, X64, and AARCH64 with the changes.
  • Leverage edk2 upstream testing.

  Integration Instructions

  • Use the gEdkiiRngAlgorithmUnSafe if needed to integrate other code changes.
    

  
  

  ---

🔐 Security Impacting

• [CHERRY-PICK] RNG Related Commits (Needed for Arm RngDxe to Work) [Rebase \& FF] @makubacki (#233)
  
  Change Details

    ## Description

  ---

  [CHERRY-PICK] SecurityPkg/SecurityPkg.dec: Move PcdCpuRngSupportedAlgorithm to MdePkg

  In order to use PcdCpuRngSupportedAlgorithm in the MdePkg in a
  following patch and to avoid making the MdePkg dependent on another
  package, move PcdCpuRngSupportedAlgorithm to the MdePkg.

  As the Pcd is only used for AARCH64, place it in an AARCH64
  specific sections.

  Signed-off-by: Pierre Gondois [email protected]
  Reviewed-by: Liming Gao [email protected]
  Reviewed-by: Sami Mujawar [email protected]
  Acked-by: Ard Biesheuvel [email protected]
  Acked-by: Jiewen Yao [email protected]
  Tested-by: Kun Qin [email protected]
  (cherry picked from commit 65b5dd8)

  ---

  [CHERRY-PICK] SecurityPkg/RngDxe: Simplify Rng algorithm selection for Arm

  The first element of mAvailableAlgoArray is defined as the default
  Rng algorithm to use. Don't go through the array at each RngGetRNG()
  call and...

v2023020000.1.3

What's Changed

• .git-blame-ignore-revs: Ignore Line Ending and Uncrustify only commits @makubacki (#219)
  
  Change Details

    ## Description

  Adds commits that only applied Uncrustify formatting or converted
  line endings to a .git-blame-ignore-revs file so they are ignored
  by git blame. This is supported by GitHub:
  https://github.blog/changelog/2022-03-24-ignore-commits-in-the-blame-view-beta/

  This helps clean up git blame by filtering out these changes.

  Note: This file needs to be updated on rebase branches. Processes
  like filter-branch can automatically update relevant SHAs.

  • Impacts functionality?
    • Functionality - Does the change ultimately impact how firmware functions?
    • Examples: Add a new library, publish a new PPI, update an algorithm, ...
  • Impacts security?
    • Security - Does the change have a direct security impact on an application,
      flow, or firmware?
    • Examples: Crypto algorithm change, buffer overflow fix, parameter
      validation improvement, ...
  • Breaking change?
    • Breaking change - Will anyone consuming this change experience a break
      in build or boot behavior?
    • Examples: Add a new library class, move a module to a different repo, call
      a function in a new library class in a pre-existing module, ...
  • Includes tests?
    • Tests - Does the change include any explicit test code?
    • Examples: Unit tests, integration tests, robot tests, ...
  • Includes documentation?
    • Documentation - Does the change contain explicit documentation additions
      outside direct code modifications (and comments)?
    • Examples: Update readme file, add feature readme file, link to documentation
      on an a separate Web page, ...

  How This Was Tested

  • git blame

  Integration Instructions

  N/A
  

  
  

  ---

  
  

• [CHERRY-PICK] SecurityPkg: Apply uncrustify formatting to relevant files @VivianNK (#215)
  
  Change Details

    ## Description

  Updating Mu projects to apply uncrusty formatting for Cpp and header files, config updated upstream in edk2 tianocore/edk2#4957 .

  Config will be updated in mu_basecore microsoft/mu_basecore#609.

  • Impacts functionality?
    • Functionality - Does the change ultimately impact how firmware functions?
    • Examples: Add a new library, publish a new PPI, update an algorithm, ...
  • Impacts security?
    • Security - Does the change have a direct security impact on an application,
      flow, or firmware?
    • Examples: Crypto algorithm change, buffer overflow fix, parameter
      validation improvement, ...
  • Breaking change?
    • Breaking change - Will anyone consuming this change experience a break
      in build or boot behavior?
    • Breaks Uncrustify check on header file. Dependent on Uncrustify update in mu_basecore (microsoft/mu_basecore#609)
  • Includes tests?
    • Tests - Does the change include any explicit test code?
    • Examples: Unit tests, integration tests, robot tests, ...
  • Includes documentation?
    • Documentation - Does the change contain explicit documentation additions
      outside direct code modifications (and comments)?
    • Examples: Update readme file, add feature readme file, link to documentation
      on an a separate Web page, ...

  How This Was Tested

  Local CI build using a local mu_basecore branch with the Uncrustify config changes.

  Integration Instructions

  Project needs update mu_basecore with config changes.
  

  
  

  ---

  
  

Full Changelog: v2023020000.1.2...v2023020000.1.3

v2023020000.1.2

What's Changed

🔐 Security Impacting

• Use New Stack Cookie Library @TaylorBeebe (#204)
  
  Change Details

    ## Description

  Update one DSC file to use the new stack cookie library, and MdePkg/MdeLibs.dsc.inc contains the definitions for the new stack cookie libraries for the remaining DSC files.

  • Impacts functionality?
    • Functionality - Does the change ultimately impact how firmware functions?
    • Examples: Add a new library, publish a new PPI, update an algorithm, ...
  • Impacts security?
    • Security - Does the change have a direct security impact on an application,
      flow, or firmware?
    • Examples: Crypto algorithm change, buffer overflow fix, parameter
      validation improvement, ...
  • Breaking change?
    • Breaking change - Will anyone consuming this change experience a break
      in build or boot behavior?
    • Examples: Add a new library class, move a module to a different repo, call
      a function in a new library class in a pre-existing module, ...
  • Includes tests?
    • Tests - Does the change include any explicit test code?
    • Examples: Unit tests, integration tests, robot tests, ...
  • Includes documentation?
    • Documentation - Does the change contain explicit documentation additions
      outside direct code modifications (and comments)?
    • Examples: Update readme file, add feature readme file, link to documentation
      on an a separate Web page, ...

  How This Was Tested

  Tested on Q35 GCC and MSVC builds

  Integration Instructions

  N/A
  

  
  

  ---

  
  

Full Changelog: v2023020000.1.1...v2023020000.1.2

v2023020000.1.1

What's Changed

• SecurityPkg: Tcg2Smm: Inspect target address before usage @kuqin12 (#195)
  
  Change Details

    ## Description

  This change uses abstracted interface from MemLib to validate incoming nested pointer before usage to ensure user supplied legitimate NVS buffer for corresponding TCG operations.

  • Impacts functionality?
    • Functionality - Does the change ultimately impact how firmware functions?
    • Examples: Add a new library, publish a new PPI, update an algorithm, ...
  • Impacts security?
    • Security - Does the change have a direct security impact on an application,
      flow, or firmware?
    • Examples: Crypto algorithm change, buffer overflow fix, parameter
      validation improvement, ...
  • Breaking change?
    • Breaking change - Will anyone consuming this change experience a break
      in build or boot behavior?
    • Examples: Add a new library class, move a module to a different repo, call
      a function in a new library class in a pre-existing module, ...
  • Includes tests?
    • Tests - Does the change include any explicit test code?
    • Examples: Unit tests, integration tests, robot tests, ...
  • Includes documentation?
    • Documentation - Does the change contain explicit documentation additions
      outside direct code modifications (and comments)?
    • Examples: Update readme file, add feature readme file, link to documentation
      on an a separate Web page, ...

  How This Was Tested

  This change is validated on proprietary hardware platform.

  Integration Instructions

  N/A
  

  
  

  ---

  
  

Full Changelog: v2023020000.1.0...v2023020000.1.1

v2023020000.1.0

What's Changed

🚀 Features & ✨ Enhancements

• CodeQlFilters.yml: Glob file patterns in nested directories @makubacki (#177)
  
  Change Details

    ## Description

  This filter file is picked up both directly in mu_tiano_plus but also
  downstream repos. Therefore, the file patterns should allow matches
  regardless of where a mu_tiano_plus submodule or external dependency
  may reside in the overall repo structure.

  • Impacts functionality?
    • Functionality - Does the change ultimately impact how firmware functions?
    • Examples: Add a new library, publish a new PPI, update an algorithm, ...
  • Impacts security?
    • Security - Does the change have a direct security impact on an application,
      flow, or firmware?
    • Examples: Crypto algorithm change, buffer overflow fix, parameter
      validation improvement, ...
  • Breaking change?
    • Breaking change - Will anyone consuming this change experience a break
      in build or boot behavior?
    • Examples: Add a new library class, move a module to a different repo, call
      a function in a new library class in a pre-existing module, ...
  • Includes tests?
    • Tests - Does the change include any explicit test code?
    • Examples: Unit tests, integration tests, robot tests, ...
  • Includes documentation?
    • Documentation - Does the change contain explicit documentation additions
      outside direct code modifications (and comments)?
    • Examples: Update readme file, add feature readme file, link to documentation
      on an a separate Web page, ...

  How This Was Tested

  • Verified local mu_tiano_plus CodeQL build
  • Verified downstream (mu_tiano_platforms) CodeQL build that leverages
    the CodeQlFilters.yml file from mu_tiano_plus.

  Integration Instructions

  No change in filtering behavior within mu_tiano_plus. Downstream repos that use
  mu_tiano_plus will see more results auto filtered matching the expectations of
  upstream repos.
  

  
  

  ---

  
  

🐛 Bug Fixes

• CodeQlFilters.yml: Glob file patterns in nested directories @makubacki (#177)
  
  Change Details

    ## Description

  This filter file is picked up both directly in mu_tiano_plus but also
  downstream repos. Therefore, the file patterns should allow matches
  regardless of where a mu_tiano_plus submodule or external dependency
  may reside in the overall repo structure.

  • Impacts functionality?
    • Functionality - Does the change ultimately impact how firmware functions?
    • Examples: Add a new library, publish a new PPI, update an algorithm, ...
  • Impacts security?
    • Security - Does the change have a direct security impact on an application,
      flow, or firmware?
    • Examples: Crypto algorithm change, buffer overflow fix, parameter
      validation improvement, ...
  • Breaking change?
    • Breaking change - Will anyone consuming this change experience a break
      in build or boot behavior?
    • Examples: Add a new library class, move a module to a different repo, call
      a function in a new library class in a pre-existing module, ...
  • Includes tests?
    • Tests - Does the change include any explicit test code?
    • Examples: Unit tests, integration tests, robot tests, ...
  • Includes documentation?
    • Documentation - Does the change contain explicit documentation additions
      outside direct code modifications (and comments)?
    • Examples: Update readme file, add feature readme file, link to documentation
      on an a separate Web page, ...

  How This Was Tested

  • Verified local mu_tiano_plus CodeQL build
  • Verified downstream (mu_tiano_platforms) CodeQL build that leverages
    the CodeQlFilters.yml file from mu_tiano_plus.

  Integration Instructions

  No change in filtering behavior within mu_tiano_plus. Downstream repos that use
  mu_tiano_plus will see more results auto filtered matching the expectations of
  upstream repos.
  

  
  

  ---

  
  

Full Changelog: v2023020000.0.4...v2023020000.1.0

v2023020000.0.4

What's Changed

• SourceLevelDebugPkg: Integrate UefiCpuLib breaking change @makubacki (#174)
  
  Change Details

    ## Description

  Updates the repo for a change that merged UefiCpuLib with CpuLib.

  UefiCpuLib will be removed entirely soon so all references are updated to CpuLib.

  • Impacts functionality?
    • Functionality - Does the change ultimately impact how firmware functions?
    • Examples: Add a new library, publish a new PPI, update an algorithm, ...
  • Impacts security?
    • Security - Does the change have a direct security impact on an application,
      flow, or firmware?
    • Examples: Crypto algorithm change, buffer overflow fix, parameter
      validation improvement, ...
  • Breaking change?
    • Breaking change - Will anyone consuming this change experience a break
      in build or boot behavior?
    • Examples: Add a new library class, move a module to a different repo, call
      a function in a new library class in a pre-existing module, ...
  • Includes tests?
    • Tests - Does the change include any explicit test code?
    • Examples: Unit tests, integration tests, robot tests, ...
  • Includes documentation?
    • Documentation - Does the change contain explicit documentation additions
      outside direct code modifications (and comments)?
    • Examples: Update readme file, add feature readme file, link to documentation
      on an a separate Web page, ...

  How This Was Tested

  • Repo CI build
  • Platform integration build (in QemuQ35Pkg)

  Integration Instructions

  N/A
  

  
  

  ---

  
  

Full Changelog: v2023020000.0.3...v2023020000.0.4

v2023020000.0.3

What's Changed

• SecurityPkg/Tpm2DeviceLibTcg2: Make mTcg2Protocol static @makubacki (#170)
  
  Change Details

    ## Description

  The global variable has a common name that can conflict with other
  TCG modules. For example, Tcg2Dxe has a similarly named global that
  is of type EFI_TCG2_PROTOCOL instead of EFI_TCG2_PROTOCOL*.

  Cc: Jiewen Yao [email protected]
  Cc: Jian J Wang [email protected]
  Signed-off-by: Michael Kubacki [email protected]
  (sent to edk2 mailing list after 202308 stable tag)

  https://edk2.groups.io/g/devel/message/107769

  • Impacts functionality?
    • Functionality - Does the change ultimately impact how firmware functions?
    • Examples: Add a new library, publish a new PPI, update an algorithm, ...
  • Impacts security?
    • Security - Does the change have a direct security impact on an application,
      flow, or firmware?
    • Examples: Crypto algorithm change, buffer overflow fix, parameter
      validation improvement, ...
  • Breaking change?
    • Breaking change - Will anyone consuming this change experience a break
      in build or boot behavior?
    • Examples: Add a new library class, move a module to a different repo, call
      a function in a new library class in a pre-existing module, ...
  • Includes tests?
    • Tests - Does the change include any explicit test code?
    • Examples: Unit tests, integration tests, robot tests, ...
  • Includes documentation?
    • Documentation - Does the change contain explicit documentation additions
      outside direct code modifications (and comments)?
    • Examples: Update readme file, add feature readme file, link to documentation
      on an a separate Web page, ...

  How This Was Tested

  SecurityPkg package build.

  Integration Instructions

  N/A
  

  
  

  ---

  
  

• SecurityPkg/HashInstanceLibSha1: Added Allocation check for codeql @kenlautner (#163)
  
  Change Details

    ## Description

  A small change to check if we're able to successfully allocate. This allows us to pass CodeQL checks.

  • Impacts functionality?
    • Functionality - Does the change ultimately impact how firmware functions?
    • Examples: Add a new library, publish a new PPI, update an algorithm, ...
  • Impacts security?
    • Security - Does the change have a direct security impact on an application,
      flow, or firmware?
    • Examples: Crypto algorithm change, buffer overflow fix, parameter
      validation improvement, ...
  • Breaking change?
    • Breaking change - Will anyone consuming this change experience a break
      in build or boot behavior?
    • Examples: Add a new library class, move a module to a different repo, call
      a function in a new library class in a pre-existing module, ...
  • Includes tests?
    • Tests - Does the change include any explicit test code?
    • Examples: Unit tests, integration tests, robot tests, ...
  • Includes documentation?
    • Documentation - Does the change contain explicit documentation additions
      outside direct code modifications (and comments)?
    • Examples: Update readme file, add feature readme file, link to documentation
      on an a separate Web page, ...

  How This Was Tested

  Tested to make sure physical platforms could boot. Also confirmed codeql tests pass as well.

  Integration Instructions

  N/A

    </blockquote>
    <hr>
  </details>
  

🐛 Bug Fixes

• FmpDevicePkg: Fix links in FmpDxe @makubacki (#161)
  
  Change Details

    ## Description

  Links are invalid causing a lint failure when moving to markdownlint
  0.32.2:

  FmpDevicePkg/FmpDxe/ReadMe.md:57:1 MD052/reference-links-images
    Reference links and images should use a label that is defined
    [Missing link or image reference definition:
     "fmpdevicepkg/library/fmpdependencychecklib/readme.md"]
  
  FmpDevicePkg/FmpDxe/ReadMe.md:58:1 MD052/reference-links-images
    Reference links and images should use a label that is defined
    [Missing link or image reference definition:
     "fmpdevicepkg/library/fmpdependencylib/readme.md"]
  

  Links are fixed in this change.

  • Impacts functionality?
    • Functionality - Does the change ultimately impact how firmware functions?
    • Examples: Add a new library, publish a new PPI, update an algorithm, ...
  • Impacts security?
    • Security - Does the change have a direct security impact on an application,
      flow, or firmware?
    • Examples: Crypto algorithm change, buffer overflow fix, parameter
      validation improvement, ...
  • Breaking change?
    • Breaking change - Will anyone consuming this change experience a break
      in build or boot behavior?
    • Examples: Add a new library class, move a module to a different repo, call
      a function in a new library class in a pre-existing module, ...
  • Includes tests?
    • Tests - Does the change include any explicit test code?
    • Examples: Unit tests, integration tests, robot tests, ...
  • Includes documentation?
    • Documentation - Does the change contain explicit documentation additions
      outside direct code modifications (and comments)?
    • Examples: Update readme file, add feature readme file, link to documentation
      on an a separate Web page, ...

  How This Was Tested

  Tested against markdownlint 0.32.2.

  Integration Instructions

  N/A
  

  
  

  ---

  
  

📖 Documentation Updates

• FmpDevicePkg: Fix links in FmpDxe @makubacki (#161)
  
  Change Details

    ## Description

  Links are invalid causing a lint failure when moving to markdownlint
  0.32.2:

  FmpDevicePkg/FmpDxe/ReadMe.md:57:1 MD052/reference-links-images
    Reference links and images should use a label that is defined
    [Missing link or image reference definition:
     "fmpdevicepkg/library/fmpdependencychecklib/readme.md"]
  
  FmpDevicePkg/FmpDxe/ReadMe.md:58:1 MD052/reference-links-images
    Reference links and images should use a label that is defined
    [Missing link or image reference definition:
     "fmpdevicepkg/library/fmpdependencylib/readme.md"]
  

  Links are fixed in this change.

  • Impacts functionality?
    • Functionality - Does the change ultimately impact how firmware functions?
    • Examples: Add a new library, publish a new PPI, update an algorithm, ...
  • Impacts security?
    • Security - Does the change have a direct security impact on an application,
      flow, or firmware?
    • Examples: Crypto algorithm change, buffer overflow fix, parameter
      validation improvement, ...
  • Breaking change?
    • Breaking change - Will anyone consuming this change experience a break
      in build or boot behavior?
    • Examples: Add a new library class, move a module to a different repo, call
      a function in a new library class in a pre-existing module, ...
  • Includes tests?
    • Tests - Does the change include any explicit test code?
    • Examples: Unit tests, integration tests, robot tests, ...
  • Includes documentation?
    • Documentation - Does the change contain explicit documentation additions
      outside direct code modifications (and comments)?
    • Examples: Update readme file, add feature readme file, link to documentation
      on an a separate Web page, ...

  How This Was Tested

  Tested against markdownlint 0.32.2.

  Integration Instructions

  N/A
  

  
  

  ---

  
  

Full Changelog: v2023020000.0.2...v2023020000.0.3

v2023020000.0.2

What's Changed

• ci.yaml: Add PrEval entry @Javagedes (#154)
  
  Change Details

    ## Description

  Add PrEval entry to each package ci.yaml file, used to enable the new preval policy 5.

  • Impacts functionality?
    • Functionality - Does the change ultimately impact how firmware functions?
    • Examples: Add a new library, publish a new PPI, update an algorithm, ...
  • Impacts security?
    • Security - Does the change have a direct security impact on an application,
      flow, or firmware?
    • Examples: Crypto algorithm change, buffer overflow fix, parameter
      validation improvement, ...
  • Breaking change?
    • Breaking change - Will anyone consuming this change experience a break
      in build or boot behavior?
    • Examples: Add a new library class, move a module to a different repo, call
      a function in a new library class in a pre-existing module, ...
  • Includes tests?
    • Tests - Does the change include any explicit test code?
    • Examples: Unit tests, integration tests, robot tests, ...
  • Includes documentation?
    • Documentation - Does the change contain explicit documentation additions
      outside direct code modifications (and comments)?
    • Examples: Update readme file, add feature readme file, link to documentation
      on an a separate Web page, ...

  How This Was Tested

  N/A

  Integration Instructions

  N/A

    </blockquote>
    <hr>
  </details>
  

🐛 Bug Fixes

• [Rebase \& FF] Fixing RNG related problems @kuqin12 (#155)
  
  Change Details

    # Preface

  Please ensure you have read the contribution docs prior
  to submitting the pull request. In particular,
  pull request guidelines.

  Description

  This change cherry-picked 2 commits from EDK2 202305 release, also fixed one buffer too small issue and one zero GUID filter issue.

  Fixes microsoft/mu_silicon_arm_tiano#136.

  For each item, place an "x" in between [ and ] if true. Example: [x].
  (you can also check items in the GitHub UI)

  • Impacts functionality?
    • Functionality - Does the change ultimately impact how firmware functions?
    • Examples: Add a new library, publish a new PPI, update an algorithm, ...
  • Impacts security?
    • Security - Does the change have a direct security impact on an application,
      flow, or firmware?
    • Examples: Crypto algorithm change, buffer overflow fix, parameter
      validation improvement, ...
  • Breaking change?
    • Breaking change - Will anyone consuming this change experience a break
      in build or boot behavior?
    • Examples: Add a new library class, move a module to a different repo, call
      a function in a new library class in a pre-existing module, ...
  • Includes tests?
    • Tests - Does the change include any explicit test code?
    • Examples: Unit tests, integration tests, robot tests, ...
  • Includes documentation?
    • Documentation - Does the change contain explicit documentation additions
      outside direct code modifications (and comments)?
    • Examples: Update readme file, add feature readme file, link to documentation
      on an a separate Web page, ...

  How This Was Tested

  This was tested on QemuSbsaPkg and booted to Windows.

  Integration Instructions

  N/A

    </blockquote>
    <hr>
  </details>
  

Full Changelog: v2023020000.0.1...v2023020000.0.2

v2023020000.0.1

What's Changed

• Onboarding ARM64 builds on selfhosted Azure pipeline agents @kuqin12 (#134)
  
  Change Details

    # Preface

  Please ensure you have read the contribution docs prior
  to submitting the pull request. In particular,
  pull request guidelines.

  Description

  This change added a few new matrix entries to support building mu_tiano_platforms on native ARM64 systems. The PR will cover both microsoft/mu_basecore#369 and microsoft/mu_basecore#305.

  The PR should also be incorporated with mu_devops change.

  For each item, place an "x" in between [ and ] if true. Example: [x].
  (you can also check items in the GitHub UI)

  • Impacts functionality?
    • Functionality - Does the change ultimately impact how firmware functions?
    • Examples: Add a new library, publish a new PPI, update an algorithm, ...
  • Impacts security?
    • Security - Does the change have a direct security impact on an application,
      flow, or firmware?
    • Examples: Crypto algorithm change, buffer overflow fix, parameter
      validation improvement, ...
  • Breaking change?
    • Breaking change - Will anyone consuming this change experience a break
      in build or boot behavior?
    • Examples: Add a new library class, move a module to a different repo, call
      a function in a new library class in a pre-existing module, ...
  • Includes tests?
    • Tests - Does the change include any explicit test code?
    • Examples: Unit tests, integration tests, robot tests, ...
  • Includes documentation?
    • Documentation - Does the change contain explicit documentation additions
      outside direct code modifications (and comments)?
    • Examples: Update readme file, add feature readme file, link to documentation
      on an a separate Web page, ...

  How This Was Tested

  This was tested on selfhost-agents and existing agents.

  Integration Instructions

  Pipeline changes, N/A for integration.

    </blockquote>
    <hr>
  </details>
  

• REBASE: Re-remove the codeql workflow @kenlautner (#138)
  
  Change Details

    ## Description

  Removed CodeQL workflows that were accidentally included in the rebase.

  For each item, place an "x" in between [ and ] if true. Example: [x].
  (you can also check items in the GitHub UI)

  • Impacts functionality?
    • Functionality - Does the change ultimately impact how firmware functions?
    • Examples: Add a new library, publish a new PPI, update an algorithm, ...
  • Impacts security?
    • Security - Does the change have a direct security impact on an application,
      flow, or firmware?
    • Examples: Crypto algorithm change, buffer overflow fix, parameter
      validation improvement, ...
  • Breaking change?
    • Breaking change - Will anyone consuming this change experience a break
      in build or boot behavior?
    • Examples: Add a new library class, move a module to a different repo, call
      a function in a new library class in a pre-existing module, ...
  • Includes tests?
    • Tests - Does the change include any explicit test code?
    • Examples: Unit tests, integration tests, robot tests, ...
  • Includes documentation?
    • Documentation - Does the change contain explicit documentation additions
      outside direct code modifications (and comments)?
    • Examples: Update readme file, add feature readme file, link to documentation
      on an a separate Web page, ...

  How This Was Tested

  N/A

  Integration Instructions

  N/A

    </blockquote>
    <hr>
  </details>
  

Full Changelog: v2023020000.0.0...v2023020000.0.1

v2023020000.0.0

What's Changed

This is the first MU Tiano Plus 202302 release 🎉

The previous branch was 202208.

These versions correspond to edk2 stable release tags that the code is based upon.

Since edk2 makes a release every 3 months, two stable tags were actually picked up in this release:

• edk2-stable202211
• edk2-stable202302

Review those release notes to understand the changes coming in from edk2. In addition, Mu repos highlight important changes in their Readme files. Review the 202302 Readme before you move code to this branch to understand major changes.