microsoft/mu_feature_uefi_variable v0.1.1

v0.1.1

Repository: microsoft/mu_feature_uefi_variable

Tag: v0.1.1

Published: 2026-02-24T21:04:11Z

Prerelease: no

Release notes:

What's Changed

remove edk2-basetools @Javagedes (#162)

Change Details

Description

Removes edk2-basetools from pip-requirements.txt and any usage of it in the CISettings.py. The is done as there are changes in the build tools python source code that are available locally in BaseTools (as is managed by Project Mu) that is not available in edk2-basetools.

• [ ] 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 the build system continues to use the local python source

Integration Instructions

N/A - only effects this repository's CI system.

Remove old CodeQL GitHub workflow @makubacki (#159)

Change Details

Description

The leaf workflow from Mu Devops is not synced to this repo right now, so it is using an old version of the CodeQL workflow that has not been updated.

Due to the permission change, this version will not function without permissions being added. For now, the workflow can just be removed and replaced with the current version when needed later.

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

Integration Instructions

N/A - Only affects workflows run on GitHub.

Update pip-requirements.txt @Javagedes (#156)

Change Details

Description

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

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

Full Changelog: https://github.com/microsoft/mu_feature_uefi_variable/compare/v0.1.0...v0.1.1