Skip to content

v2.0.0
Compare
Choose a tag to compare
@github-actions github-actions released this 28 Feb 21:28
· 173 commits to refs/heads/main since this release
v2.0.0
c0f7b04
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

What's Changed

Note: v2.0.0 marks the first release from mu_feature_dfci 🎉. Previous
major release versions were made before moving to this repo.

  • .pytool/CISettings.py: Use all CodeQL filter files @makubacki (#35)
    Change Details
      ## Description

    Updates the CodeQL file filter list to include all filters found in
    the repo. This will pick up filters from repos like 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

    Verified CodeQL filter files being used are expected.

    Integration Instructions

    N/A

    Signed-off-by: Michael Kubacki [email protected]



  • pip: bump edk2-pytool-extensions from 0.21.8 to 0.22.0 @dependabot (#34)
    Change Details
      Bumps [edk2-pytool-extensions](https://github.com/tianocore/edk2-pytool-extensions) from 0.21.8 to 0.22.0.
    Release notes

    Sourced from edk2-pytool-extensions's releases.

    Version 0.22.0

    What's Changed

    Integration Instructions

    This release has no integration instructions, however git management for edk2_setup, edk2_ci_setup, and git_depenencies has been completely rewritten. While this change has passed all unit and integration tests, it is expected that there will be some growing pains. Please raise an issue for anything that comes up here.

    Full Changelog: tianocore/edk2-pytool-extensions@v0.21.9...v0.22.0

    Version 0.21.9

    What's Changed

    Other Changes

    Full Changelog: tianocore/edk2-pytool-extensions@v0.21.8...v0.21.9

    Commits
    • f03cc88 Remove edk2_git.py (#407)
    • b202e95 Update vscode settings
    • 12acb07 edk2_logging: filter secrets from logs
    • 0ee5614 Add CLI env information to the argument parser --help (#417)
    • 439b70a Bump mkdocs-material from 9.0.12 to 9.0.13 in /docs/user (#448)
    • 88043ec Bump setuptools from 67.3.1 to 67.3.2 (#447)
    • f0aab31 Bump setuptools from 67.2.0 to 67.3.1 (#444)
    • 921b8ab edk2_logging: Add GCC compilation error info to log
    • c09a684 edk2_logging: Strip whitespace from errors
    • f7d91d4 test_edk2_logging: Add initial set of logging unit tests
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • Correct TPL processing for Apply packets @mikeytdisco (#29)
    Change Details
      # Preface

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

    Description

    Additional testing showed Semm enroll fails to prompt for the thumbprint.

    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

    Ran Semm Enroll and Semm Unenroll tests to verify the UI prompt occurred.

    Integration Instructions

    N/A

      </blockquote>
  <hr>
</details>
  • GitHub Action: Bump microsoft/mu\_devops from 2.0.1 to 2.1.0 @dependabot (#27)
    Change Details
      Bumps [microsoft/mu_devops](https://github.com/microsoft/mu_devops) from 2.0.1 to 2.1.0.
    Release notes

    Sourced from microsoft/mu_devops's releases.

    v2.1.0

    What's Changed

    🚀 Features & ✨ Enhancements

    Signed-off-by: Michael Kubacki [email protected]

    📖 Documentation Updates

    Signed-off-by: Michael Kubacki [email protected]

      </blockquote>
  <hr>
</details>

    Full Changelog: microsoft/mu_devops@v2.0.2...v2.1.0

    v2.0.2

    What's Changed

    ... (truncated)

    Commits
    • bcace84 .sync/workflows/leaf: Add PR formatting validator workflow (#118)
    • fe730bb PullRequests.github-issues: Remove uefibot and ProjectMuBot from human PRs (#...
    • 883f72d .sync/azure_pipelines: Switch from microdnf to dnf (#115)
    • badf2c8 Repo File Sync: synced file(s) with microsoft/mu_devops (#114)
    • See full diff in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • pip: bump antlr4-python3-runtime from 4.11.1 to 4.12.0 @dependabot (#26)
    Change Details
      Bumps [antlr4-python3-runtime](http://www.antlr.org) from 4.11.1 to 4.12.0.

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • pip: bump edk2-pytool-extensions from 0.21.7 to 0.21.8 @dependabot (#20)
    Change Details
      Bumps [edk2-pytool-extensions](https://github.com/tianocore/edk2-pytool-extensions) from 0.21.7 to 0.21.8.
    Release notes

    Sourced from edk2-pytool-extensions's releases.

    Version 0.21.8

    What's Changed

    Full Changelog: tianocore/edk2-pytool-extensions@v0.21.7...v0.21.8

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • pip: bump edk2-pytool-extensions from 0.21.6 to 0.21.7 @dependabot (#19)
    Change Details
      Bumps [edk2-pytool-extensions](https://github.com/tianocore/edk2-pytool-extensions) from 0.21.6 to 0.21.7.
    Release notes

    Sourced from edk2-pytool-extensions's releases.

    Version 0.21.7

    What's Changed

    Full Changelog: tianocore/edk2-pytool-extensions@v0.21.6...v0.21.7

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • pip: bump edk2-pytool-library from 0.13.1 to 0.14.0 @dependabot (#17)
    Change Details
      Bumps [edk2-pytool-library](https://github.com/tianocore/edk2-pytool-library) from 0.13.1 to 0.14.0.
    Release notes

    Sourced from edk2-pytool-library's releases.

    Version 0.14.0

    Breaking Changes

    Integration Steps

    • Replace with standard library enum definition

    What's Changed

    Other Changes

    New Contributors

    Full Changelog: tianocore/edk2-pytool-library@v0.13.1...v0.14.0

    Commits
    • abce13c utility_functions: Force GetHostInfo() to return MacOs (#257)
    • e1645a4 Remove Deprecated custom enum (#249)
    • d431b09 Update buildreport_parser (#256)
    • fc56d9e EfiVariableAttributes: Enable string / int conversions (#242)
    • eb8e5d2 Implmented C array export function and updated utility_functions.py (#244)
    • 163b5c8 Bump mkdocs-material from 8.5.6 to 9.0.11 in /docs/user (#255)
    • See full diff in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • Simplifiy Tpl changes @mikeytdisco (#11)
    Change Details
      # Preface

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

    Description

    A TPL inversion was created with how TPL changes were done. This was corrected to always follow normal TPL transitions. The TPL inversion also caused errors on some platfoms.

    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

    Tested locally on Zeus

    Integration Instructions

    N/A

      </blockquote>
  <hr>
</details>
  • pip: bump edk2-pytool-library from 0.13.0 to 0.13.1 @dependabot (#13)
    Change Details
      Bumps [edk2-pytool-library](https://github.com/tianocore/edk2-pytool-library) from 0.13.0 to 0.13.1.
    Release notes

    Sourced from edk2-pytool-library's releases.

    Version 0.13.1

    What's Changed

    N/A

    Other Changes

    Full Changelog: tianocore/edk2-pytool-library@v0.13.0...v0.13.1

    Commits
    • 1d6fb1a Bump mkdocs from 1.4.0 to 1.4.2 in /docs/user (#254)
    • f9c6233 Bump mkdocstrings-python from 0.7.1 to 0.8.3 in /docs/user (#253)
    • 354d422 Bump black from 22.10.0 to 23.1.0 in /docs/user (#252)
    • 7a8493e Bump markdown-include from 0.6.0 to 0.8.0 in /docs/user (#251)
    • 4afb6f0 Bump mkdocstrings[python] from 0.19.0 to 0.20.0 in /docs/user (#250)
    • 509c958 Replace pipeline CI with action CI (#248)
    • 985dc67 Bump setuptools from 67.0.0 to 67.1.0 (#247)
    • See full diff in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • Matrix-Build-Job.yml: Add container support @makubacki (#6)
    Change Details
      Adds support for container images to the matrix.

    Signed-off-by: Michael Kubacki [email protected]



  • Bump edk2-pytool-library to 0.13.0 @Javagedes (#5)
    Change Details
     

⚠️ Breaking Changes

  • .azurepipelines: Add support for new artifacts\_identifier param @makubacki (#15)
    Change Details
      ## Description

    A new identifier can be used to identify published artifacts (as
    of mu_devops 2.0.0 release). This change passes the packages and
    targets being built to clarify artifact names.

    The default value for the identifier is "Artifacts" so that is
    what is being used at the moment. For example, build logs are
    published under "Logs Artifacts". After this change, the
    identifier will be "Logs <packages> <targets>".

    • 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 pipeline artifacts are named as expected.

    Integration Instructions

    This is considered a "breaking change" because artifacts are accessible via
    ADO APIs and can be identified by the artifact name. While it is unlikely any
    process is consuming these artifacts based on name, if they are, they will
    need to use the new artifact naming convention introduced in this change.

    Signed-off-by: Michael Kubacki [email protected]



🚀 Features & ✨ Enhancements

  • Add CodeQL Stuart parameter to this repo @makubacki (#21)
    Change Details
      ## Description

    Allows CodeQL to be run locally by specifying --codeql when
    providing stuart_update and stuart_ci_build commands in this
    repo.

    • stuart_update - Automatically downloads the CodeQL CLI application
      appropriate for your host operating system
      • Note: This may take several minutes depending on your Internet
        connection speed
    • stuart_ci_build - Automatically runs CodeQL against the packages
      built after they are built.

    NOTE: Running with CodeQL will increase your overall build time for a
    couple of reasons:

    1. Every package must be clean built to get proper results
    2. The CodeQL analysis phase takes a while to run

    (1) happens automatically, you do not need to specify a clean build
    manually

    For more information, such as:

    1. How to view results
    2. How to modify the CodeQL rules run
    3. How to include/exclude files/rules at various levels of granularity

    And more...

    Go to the CodeQL plugin readme:

    https://github.com/microsoft/mu_basecore/blob/HEAD/.pytool/Plugin/CodeQL/Readme.md

    Also, this commit sets STUART_CODEQL_AUDIT_ONLY to TRUE. This is
    done to:

    1. Demonstrate how to set an entire repo to audit-only mode
    2. Allow CodeQL to run without breaking the build at this point in
      source history since issues remain to be fixed on this branch

    This will be removed from the file when (2) is completed.

    • 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 --codeql usage with stuart_update and stuart_ci_build locally.

    Integration Instructions

    See earlier PR description and CodeQL plugin readme:

    https://github.com/microsoft/mu_basecore/blob/HEAD/.pytool/Plugin/CodeQL/Readme.md

    Signed-off-by: Michael Kubacki [email protected]



  • .azurepipelines: Add support for new artifacts\_identifier param @makubacki (#15)
    Change Details
      ## Description

    A new identifier can be used to identify published artifacts (as
    of mu_devops 2.0.0 release). This change passes the packages and
    targets being built to clarify artifact names.

    The default value for the identifier is "Artifacts" so that is
    what is being used at the moment. For example, build logs are
    published under "Logs Artifacts". After this change, the
    identifier will be "Logs <packages> <targets>".

    • 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 pipeline artifacts are named as expected.

    Integration Instructions

    This is considered a "breaking change" because artifacts are accessible via
    ADO APIs and can be identified by the artifact name. While it is unlikely any
    process is consuming these artifacts based on name, if they are, they will
    need to use the new artifact naming convention introduced in this change.

    Signed-off-by: Michael Kubacki [email protected]



🐛 Bug Fixes

  • Update lock test pass message to avoid confusion @mikeytdisco (#39)
    Change Details
      # Preface

    Description

    Change the Pass message to not be associated with an error message.

    • 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>
  • DfciPkg/UiSupport: Fix bad size in memory alloc @makubacki (#31)
    Change Details
      ## Description

    AllocatePool () takes a UINTN argument that specifies the size
    of buffer to allocate. If the size is 0, a buffer of size 0 is
    returned.

    The code modified here calls AllocatePool () as follows:
    CertText = AllocatePool (L'\0');

    The single wide-character literal \0 has an integer value of zero.

    This change updates the call to be sizeof (L'\0') which will
    pass the bytes required to hold the character.

    This will allow the buffer to hold the character in the following
    assignment to the buffer:

    CertText[0] = L'\0';

    • 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

    Compile DfciPkg with change

    Integration Instructions

    N/A

    Signed-off-by: Michael Kubacki [email protected]

      </blockquote>
  <hr>
</details>

🔐 Security Impacting

  • DfciPkg: Additional CodeQL fixes @TaylorBeebe (#24)
    Change Details
      ## Description

    Various fixes

    • 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

    Building DfciPkg

    Integration Instructions

    N/A



  • Update DfciVarLock to correctly lock Dfci Variables @mikeytdisco (#23)
    Change Details
      # Preface

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

    Description

    The commit at ac4bd1b was not tested thoroughly and left some DFCI variables unlocked.

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

    • [x ] Impacts functionality?
      • Functionality - Does the change ultimately impact how firmware functions?
      • Examples: Add a new library, publish a new PPI, update an algorithm, ...
    • [x ] 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, ...
    • [x ] 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 multiple platforms.

    Integration Instructions

    N/A

      </blockquote>
  <hr>
</details>

📖 Documentation Updates

  • Add Test requirement for using local Refresh from Network server. @mikeytdisco (#3)
    Change Details
      # Preface

    Description

    This PR adds a requirement to use a local Refresh from Network server, and how to set one up on a Windows system using WSL2 and Docket Desktop. This PR is a test environment only PR, and does not affect Dfci operation.

    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

    Tested locally

    Integration Instructions

    The ability to test Refresh from Network has changed significantly.
    You will have to read the DfciTests Documentation, as there are significant changes on testing Refresh from Network.
    Instead of a hand built Azure server, each entity testing Dfci has to publish their own Refresh Server.



  • Minor changes to Readme.rst @mikeytdisco (#4)
    Change Details
      # Preface

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

    Description

    <Please include a description of the change and why this change was made.>

    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

    None

    Integration Instructions

    N/A

      </blockquote>
  <hr>
</details>
  • Update document links to point into mu\_feature\_dfci @mikeytdisco (#2)
    Change Details
      # Preface

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

    Description

    Updated document links to point into this repository.

    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, ...
    • [x ] 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 locally.

    Integration Instructions

    N/A



Full Changelog: ...v0.1.0

Contributors

mikeytdisco, makubacki, and 3 other contributors
Assets 2
Loading