From fdef50e311baba4dedbd1d575ce705ccfe9e2a05 Mon Sep 17 00:00:00 2001 From: kenlautner <85201046+kenlautner@users.noreply.github.com> Date: Tue, 14 May 2024 08:40:27 -0700 Subject: [PATCH 1/8] Updated MorLockTestApp to expect the new standard return values (#482) ## Description In TcgMorLockSmm.c the SetVariableCheckHandlerMorLock() function was changed to set the MorLock variable Value to 0x01 to indicate Locked Without Key to match the spec when addressing a possible dictionary attack. The commit in question is [here](https://github.com/microsoft/mu_basecore/commit/63923a5642e86f386a5c719a90cfc6a929ea9cb0). This PR changes the checked test results to match the new expected behavior. - [ ] 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, ... - [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 in the uefi shell. The tests that previously failed now pass. ## Integration Instructions N/A --- .../FunctionalSystemTests/MorLockTestApp/MorLockTestApp.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/UefiTestingPkg/FunctionalSystemTests/MorLockTestApp/MorLockTestApp.c b/UefiTestingPkg/FunctionalSystemTests/MorLockTestApp/MorLockTestApp.c index 51552355e4..078e25d61b 100644 --- a/UefiTestingPkg/FunctionalSystemTests/MorLockTestApp/MorLockTestApp.c +++ b/UefiTestingPkg/FunctionalSystemTests/MorLockTestApp/MorLockTestApp.c @@ -236,7 +236,7 @@ MorLockShouldNotBeSet ( } UT_ASSERT_NOT_EFI_ERROR (Status); - UT_ASSERT_EQUAL (MorLock, MOR_LOCK_DATA_UNLOCKED); + UT_ASSERT_EQUAL (MorLock, MOR_LOCK_DATA_LOCKED_WITHOUT_KEY); return UNIT_TEST_PASSED; } // MorLockShouldNotBeSet() @@ -790,7 +790,7 @@ MorLockv2ShouldReportCorrectly ( UT_LOG_VERBOSE ("%a - Status = %r, MorLock = %d\n", __FUNCTION__, Status, MorLock); UT_ASSERT_NOT_EFI_ERROR (Status); - UT_ASSERT_EQUAL (MorLock, MOR_LOCK_DATA_LOCKED_WITH_KEY); + UT_ASSERT_EQUAL (MorLock, MOR_LOCK_DATA_LOCKED_WITHOUT_KEY); return UNIT_TEST_PASSED; } // MorLockv2ShouldReportCorrectly() From 5d7b0e0ab76fb9a9fde5acfd38480c477f722795 Mon Sep 17 00:00:00 2001 From: "Project Mu UEFI Bot [bot]" <45776386+uefibot@users.noreply.github.com> Date: Tue, 14 May 2024 13:33:42 -0400 Subject: [PATCH 2/8] Repo File Sync: .gitattributes: Prevent line ending conversion (#485) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit synced local file(s) with [microsoft/mu_devops](https://github.com/microsoft/mu_devops). 🤖: View the [Repo File Sync Configuration File](https://github.com/microsoft/mu_devops/blob/main/.sync/Files.yml) to see how files are synced. --- This PR was created automatically by the [repo-file-sync-action](https://github.com/BetaHuhn/repo-file-sync-action) workflow run [#9076674548](https://github.com/microsoft/mu_devops/actions/runs/9076674548) Signed-off-by: Project Mu UEFI Bot --- .gitattributes | 1 + 1 file changed, 1 insertion(+) create mode 100644 .gitattributes diff --git a/.gitattributes b/.gitattributes new file mode 100644 index 0000000000..625449502b --- /dev/null +++ b/.gitattributes @@ -0,0 +1 @@ +* -text From e47791add4a1c17cf77fb074f1f38a03449c7bf5 Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Wed, 15 May 2024 08:08:47 -0700 Subject: [PATCH 3/8] pip: bump regex from 2024.4.28 to 2024.5.10 (#487) Bumps [regex](https://github.com/mrabarnett/mrab-regex) from 2024.4.28 to 2024.5.10. Signed-off-by: dependabot[bot] Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> --- pip-requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pip-requirements.txt b/pip-requirements.txt index ebd6910d0d..1f47a98320 100644 --- a/pip-requirements.txt +++ b/pip-requirements.txt @@ -15,5 +15,5 @@ edk2-pytool-library==0.21.5 edk2-pytool-extensions==0.27.4 antlr4-python3-runtime==4.13.1 -regex==2024.4.28 +regex==2024.5.10 pygount==1.6.1 From 72e86e94c970bd03605a52ef7f70460070c406e5 Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Wed, 15 May 2024 10:36:25 -0700 Subject: [PATCH 4/8] pip: bump pygount from 1.6.1 to 1.8.0 (#486) Bumps [pygount](https://github.com/roskakori/pygount) from 1.6.1 to 1.8.0. Signed-off-by: dependabot[bot] Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> --- pip-requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pip-requirements.txt b/pip-requirements.txt index 1f47a98320..7f04f89195 100644 --- a/pip-requirements.txt +++ b/pip-requirements.txt @@ -16,4 +16,4 @@ edk2-pytool-library==0.21.5 edk2-pytool-extensions==0.27.4 antlr4-python3-runtime==4.13.1 regex==2024.5.10 -pygount==1.6.1 +pygount==1.8.0 From 0b2315b5f35930943382bf9aeb3712bc60753fa6 Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Wed, 22 May 2024 21:14:20 -0700 Subject: [PATCH 5/8] pip: bump regex from 2024.5.10 to 2024.5.15 (#489) Bumps [regex](https://github.com/mrabarnett/mrab-regex) from 2024.5.10 to 2024.5.15. Signed-off-by: dependabot[bot] Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> --- pip-requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pip-requirements.txt b/pip-requirements.txt index 7f04f89195..3faaa65131 100644 --- a/pip-requirements.txt +++ b/pip-requirements.txt @@ -15,5 +15,5 @@ edk2-pytool-library==0.21.5 edk2-pytool-extensions==0.27.4 antlr4-python3-runtime==4.13.1 -regex==2024.5.10 +regex==2024.5.15 pygount==1.8.0 From ab1129bd24b051e2f9068bb2fe7e71bb300c5283 Mon Sep 17 00:00:00 2001 From: Ken Date: Thu, 30 May 2024 01:59:16 +0800 Subject: [PATCH 6/8] Update MorLockTestApp to fix errors with new standard return values (#488) ## Description When TcgMorLockSmm.c the SetVariableCheckHandlerMorLock() function was changed to set the MorLock variable Value to 0x01 to indicate Locked Without Key, MorLockTestApp also need to be changed to make sure the test flow can get positive results. Changes are listed as below 1. MorLockShouldNotBeSet(): This function should compare with MOR_LOCK_DATA_UNLOCKED. 2. MorLockv2LockedWithoutKeyShouldReportCorrectly(): Rename from MorLockv2ShouldReportCorrectly() and update usage in MorLockTestApp() as it is compared with MOR_LOCK_DATA_LOCKED_WITHOUT_KEY. 3. MorLockv2LockedWithKeyShouldReportCorrectly(): This new function compares MorLock with MOR_LOCK_DATA_LOCKED_WITH_KEY for Morlock V2 testing. Also update usage in MorLockTestApp(). 4. MorLockv2ShouldNotClearWithWrongKey(): Should compare with MOR_LOCK_DATA_LOCKED_WITHOUT_KEY when using wrong key to clear MorLock. 5. MorLockv2ShouldSetClearSet(): Should compare with MOR_LOCK_DATA_LOCKED_WITHOUT_KEY when using different key to clear MorLock. 6. MorLockTestApp(): Update above function usage in different test cases to make sure the test can be finished. - [ ] 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, ... - [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 in the uefi shell. The tests should get positive results and no errors are reported. ## Integration Instructions N/A --- .../MorLockTestApp/MorLockTestApp.c | 47 ++++++++++++++----- 1 file changed, 34 insertions(+), 13 deletions(-) diff --git a/UefiTestingPkg/FunctionalSystemTests/MorLockTestApp/MorLockTestApp.c b/UefiTestingPkg/FunctionalSystemTests/MorLockTestApp/MorLockTestApp.c index 078e25d61b..0c78636548 100644 --- a/UefiTestingPkg/FunctionalSystemTests/MorLockTestApp/MorLockTestApp.c +++ b/UefiTestingPkg/FunctionalSystemTests/MorLockTestApp/MorLockTestApp.c @@ -236,7 +236,7 @@ MorLockShouldNotBeSet ( } UT_ASSERT_NOT_EFI_ERROR (Status); - UT_ASSERT_EQUAL (MorLock, MOR_LOCK_DATA_LOCKED_WITHOUT_KEY); + UT_ASSERT_EQUAL (MorLock, MOR_LOCK_DATA_UNLOCKED); return UNIT_TEST_PASSED; } // MorLockShouldNotBeSet() @@ -776,7 +776,7 @@ MorLockv2ShouldBeLockable ( UNIT_TEST_STATUS EFIAPI -MorLockv2ShouldReportCorrectly ( +MorLockv2LockedWithoutKeyShouldReportCorrectly ( IN UNIT_TEST_CONTEXT Context ) { @@ -793,7 +793,28 @@ MorLockv2ShouldReportCorrectly ( UT_ASSERT_EQUAL (MorLock, MOR_LOCK_DATA_LOCKED_WITHOUT_KEY); return UNIT_TEST_PASSED; -} // MorLockv2ShouldReportCorrectly() +} // MorLockv2LockedWithoutKeyShouldReportCorrectly() + +UNIT_TEST_STATUS +EFIAPI +MorLockv2LockedWithKeyShouldReportCorrectly ( + IN UNIT_TEST_CONTEXT Context + ) +{ + EFI_STATUS Status; + UINT8 MorLock; + + UT_LOG_VERBOSE ("%a()\n", __FUNCTION__); + + Status = GetMorLockVariable (&MorLock); + + UT_LOG_VERBOSE ("%a - Status = %r, MorLock = %d\n", __FUNCTION__, Status, MorLock); + + UT_ASSERT_NOT_EFI_ERROR (Status); + UT_ASSERT_EQUAL (MorLock, MOR_LOCK_DATA_LOCKED_WITH_KEY); + + return UNIT_TEST_PASSED; +} // MorLockv2LockedWithKeyShouldReportCorrectly() UNIT_TEST_STATUS EFIAPI @@ -1040,7 +1061,7 @@ MorLockv2ShouldNotClearWithWrongKey ( // Verify that mode is still enabled. Status = GetMorLockVariable (&MorLock); UT_ASSERT_NOT_EFI_ERROR (Status); - UT_ASSERT_EQUAL (MorLock, MOR_LOCK_DATA_LOCKED_WITH_KEY); + UT_ASSERT_EQUAL (MorLock, MOR_LOCK_DATA_LOCKED_WITHOUT_KEY); return UNIT_TEST_PASSED; } // MorLockv2ShouldNotClearWithWrongKey() @@ -1181,7 +1202,7 @@ MorLockv2ShouldSetClearSet ( // Verify that mode is still enabled. Status = GetMorLockVariable (&MorLock); UT_ASSERT_NOT_EFI_ERROR (Status); - UT_ASSERT_EQUAL (MorLock, MOR_LOCK_DATA_LOCKED_WITH_KEY); + UT_ASSERT_EQUAL (MorLock, MOR_LOCK_DATA_LOCKED_WITHOUT_KEY); return UNIT_TEST_PASSED; } // MorLockv2ShouldSetClearSet() @@ -1296,14 +1317,14 @@ MorLockTestApp ( // reboots. So let's say this is for efficiency. // AddTestCase (MorLockV2Tests, "Should be able to set the v2 MORLock", "Security.MOR.LockV2.SetLock", MorLockv2ShouldBeLockable, MorLockShouldNotBeSet, NULL, NULL); - AddTestCase (MorLockV2Tests, "Should report version correctly when locked with MORLock v2", "Security.MOR.LockV2.LockVersion", MorLockv2ShouldReportCorrectly, NULL, NULL, NULL); - AddTestCase (MorLockV2Tests, "Should only return one byte when reading MORLock v2", "Security.MOR.LockV2.LockSize", MorLockv2ShouldOnlyReturnOneByte, MorLockv2ShouldReportCorrectly, NULL, NULL); - AddTestCase (MorLockV2Tests, "Should not return the key contents when locked with MORLock v2", "Security.MOR.LockV2.LockDataProtection", MorLockv2ShouldNotReturnKey, MorLockv2ShouldReportCorrectly, NULL, NULL); - AddTestCase (MorLockV2Tests, "Should not be able to change the MOR control when locked with MORLock v2", "Security.MOR.LockV2.Lock", MorControlShouldNotChange, MorLockv2ShouldReportCorrectly, NULL, NULL); - AddTestCase (MorLockV2Tests, "Should not be able to change the key when locked with MORLock v2", "Security.MOR.LockV2.LockImmutable", MorLockv2ShouldNotChangeWhenLocked, MorLockv2ShouldReportCorrectly, NULL, NULL); - AddTestCase (MorLockV2Tests, "Should not be able to change to MORLock v1 when locked with MORLock v2", "Security.MOR.LockV2.ChangeToV1Lock", MorLockv2ShouldNotChangeTov1, MorLockv2ShouldReportCorrectly, NULL, NULL); - AddTestCase (MorLockV2Tests, "Should not be able to delete the MORLock when locked with MORLock v2", "Security.MOR.LockV2.LockDelete", MorLockv2ShouldNotBeDeleteable, MorLockv2ShouldReportCorrectly, NULL, NULL); - AddTestCase (MorLockV2Tests, "MORLock v2 should clear after reboot", "Security.MOR.MorLockV2.ClearOnReboot", MorLockShouldClearAfterReboot, MorLockv2ShouldReportCorrectly, NULL, NULL); + AddTestCase (MorLockV2Tests, "Should report version correctly when locked with MORLock v2", "Security.MOR.LockV2.LockVersion", MorLockv2LockedWithKeyShouldReportCorrectly, NULL, NULL, NULL); + AddTestCase (MorLockV2Tests, "Should only return one byte when reading MORLock v2", "Security.MOR.LockV2.LockSize", MorLockv2ShouldOnlyReturnOneByte, MorLockv2LockedWithKeyShouldReportCorrectly, NULL, NULL); + AddTestCase (MorLockV2Tests, "Should not return the key contents when locked with MORLock v2", "Security.MOR.LockV2.LockDataProtection", MorLockv2ShouldNotReturnKey, MorLockv2LockedWithKeyShouldReportCorrectly, NULL, NULL); + AddTestCase (MorLockV2Tests, "Should not be able to change the MOR control when locked with MORLock v2", "Security.MOR.LockV2.Lock", MorControlShouldNotChange, MorLockv2LockedWithKeyShouldReportCorrectly, NULL, NULL); + AddTestCase (MorLockV2Tests, "Should not be able to change the key when locked with MORLock v2", "Security.MOR.LockV2.LockImmutable", MorLockv2ShouldNotChangeWhenLocked, MorLockv2LockedWithKeyShouldReportCorrectly, NULL, NULL); + AddTestCase (MorLockV2Tests, "Should not be able to change to MORLock v1 when locked with MORLock v2", "Security.MOR.LockV2.ChangeToV1Lock", MorLockv2ShouldNotChangeTov1, MorLockv2LockedWithoutKeyShouldReportCorrectly, NULL, NULL); + AddTestCase (MorLockV2Tests, "Should not be able to delete the MORLock when locked with MORLock v2", "Security.MOR.LockV2.LockDelete", MorLockv2ShouldNotBeDeleteable, MorLockv2LockedWithoutKeyShouldReportCorrectly, NULL, NULL); + AddTestCase (MorLockV2Tests, "MORLock v2 should clear after reboot", "Security.MOR.MorLockV2.ClearOnReboot", MorLockShouldClearAfterReboot, MorLockv2LockedWithoutKeyShouldReportCorrectly, NULL, NULL); // // End of tests that assume precedence. // From here on, each test is isolated and will clean up after itself. From 8213f0ef0d88f9129bf82323debae78774f8da47 Mon Sep 17 00:00:00 2001 From: "Project Mu UEFI Bot [bot]" <45776386+uefibot@users.noreply.github.com> Date: Thu, 30 May 2024 10:25:17 -0400 Subject: [PATCH 7/8] Repo File Sync: synced file(s) with microsoft/mu_devops (#490) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit synced local file(s) with [microsoft/mu_devops](https://github.com/microsoft/mu_devops). 🤖: View the [Repo File Sync Configuration File](https://github.com/microsoft/mu_devops/blob/main/.sync/Files.yml) to see how files are synced. --- This PR was created automatically by the [repo-file-sync-action](https://github.com/BetaHuhn/repo-file-sync-action) workflow run [#9299922215](https://github.com/microsoft/mu_devops/actions/runs/9299922215) Signed-off-by: Project Mu UEFI Bot --- .azurepipelines/MuDevOpsWrapper.yml | 2 +- .github/workflows/auto-approve.yml | 2 +- .github/workflows/auto-merge.yml | 2 +- .github/workflows/issue-assignment.yml | 2 +- .github/workflows/label-issues.yml | 2 +- .github/workflows/label-sync.yml | 2 +- .github/workflows/release-draft.yml | 2 +- .github/workflows/stale.yml | 2 +- .github/workflows/triage-issues.yml | 2 +- 9 files changed, 9 insertions(+), 9 deletions(-) diff --git a/.azurepipelines/MuDevOpsWrapper.yml b/.azurepipelines/MuDevOpsWrapper.yml index 5950bd9308..e838283829 100644 --- a/.azurepipelines/MuDevOpsWrapper.yml +++ b/.azurepipelines/MuDevOpsWrapper.yml @@ -19,7 +19,7 @@ resources: type: github endpoint: microsoft name: microsoft/mu_devops - ref: refs/tags/v9.1.9 + ref: refs/tags/v10.0.0 parameters: - name: do_ci_build diff --git a/.github/workflows/auto-approve.yml b/.github/workflows/auto-approve.yml index 4d8c5ec178..23b9389ffe 100644 --- a/.github/workflows/auto-approve.yml +++ b/.github/workflows/auto-approve.yml @@ -29,5 +29,5 @@ jobs: if: | github.event.pull_request.user.login == 'dependabot[bot]' || github.event.pull_request.user.login == 'uefibot' - uses: microsoft/mu_devops/.github/workflows/AutoApprover.yml@v9.1.9 + uses: microsoft/mu_devops/.github/workflows/AutoApprover.yml@v10.0.0 secrets: inherit diff --git a/.github/workflows/auto-merge.yml b/.github/workflows/auto-merge.yml index 84cf27a116..4f37dd5f5a 100644 --- a/.github/workflows/auto-merge.yml +++ b/.github/workflows/auto-merge.yml @@ -32,5 +32,5 @@ jobs: if: | github.event.pull_request.user.login == 'dependabot[bot]' || github.event.pull_request.user.login == 'uefibot' - uses: microsoft/mu_devops/.github/workflows/AutoMerger.yml@v9.1.9 + uses: microsoft/mu_devops/.github/workflows/AutoMerger.yml@v10.0.0 secrets: inherit diff --git a/.github/workflows/issue-assignment.yml b/.github/workflows/issue-assignment.yml index 94735ebcdb..79196ea3b2 100644 --- a/.github/workflows/issue-assignment.yml +++ b/.github/workflows/issue-assignment.yml @@ -23,4 +23,4 @@ jobs: contents: read issues: write - uses: microsoft/mu_devops/.github/workflows/IssueAssignment.yml@v9.1.9 + uses: microsoft/mu_devops/.github/workflows/IssueAssignment.yml@v10.0.0 diff --git a/.github/workflows/label-issues.yml b/.github/workflows/label-issues.yml index dd78cb86be..ffad0ec08f 100644 --- a/.github/workflows/label-issues.yml +++ b/.github/workflows/label-issues.yml @@ -36,4 +36,4 @@ jobs: contents: read pull-requests: write - uses: microsoft/mu_devops/.github/workflows/Labeler.yml@v9.1.9 + uses: microsoft/mu_devops/.github/workflows/Labeler.yml@v10.0.0 diff --git a/.github/workflows/label-sync.yml b/.github/workflows/label-sync.yml index c8b8f2a427..c42746422d 100644 --- a/.github/workflows/label-sync.yml +++ b/.github/workflows/label-sync.yml @@ -28,4 +28,4 @@ jobs: permissions: issues: write - uses: microsoft/mu_devops/.github/workflows/LabelSyncer.yml@v9.1.9 + uses: microsoft/mu_devops/.github/workflows/LabelSyncer.yml@v10.0.0 diff --git a/.github/workflows/release-draft.yml b/.github/workflows/release-draft.yml index f171216053..94e45e70f0 100644 --- a/.github/workflows/release-draft.yml +++ b/.github/workflows/release-draft.yml @@ -32,5 +32,5 @@ jobs: contents: write pull-requests: write - uses: microsoft/mu_devops/.github/workflows/ReleaseDrafter.yml@v9.1.9 + uses: microsoft/mu_devops/.github/workflows/ReleaseDrafter.yml@v10.0.0 secrets: inherit diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml index fc34d6bf0a..5b94e82283 100644 --- a/.github/workflows/stale.yml +++ b/.github/workflows/stale.yml @@ -29,4 +29,4 @@ jobs: issues: write pull-requests: write - uses: microsoft/mu_devops/.github/workflows/Stale.yml@v9.1.9 + uses: microsoft/mu_devops/.github/workflows/Stale.yml@v10.0.0 diff --git a/.github/workflows/triage-issues.yml b/.github/workflows/triage-issues.yml index 3c68005d89..49780aaedb 100644 --- a/.github/workflows/triage-issues.yml +++ b/.github/workflows/triage-issues.yml @@ -23,4 +23,4 @@ jobs: permissions: issues: write - uses: microsoft/mu_devops/.github/workflows/IssueTriager.yml@v9.1.9 + uses: microsoft/mu_devops/.github/workflows/IssueTriager.yml@v10.0.0 From 3709a53fb5670158f2a40b3f477730d6c0993f2c Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Sun, 2 Jun 2024 20:24:39 -0700 Subject: [PATCH 8/8] pip: bump edk2-pytool-extensions from 0.27.4 to 0.27.5 (#491) Bumps [edk2-pytool-extensions](https://github.com/tianocore/edk2-pytool-extensions) from 0.27.4 to 0.27.5. Signed-off-by: dependabot[bot] Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> --- pip-requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pip-requirements.txt b/pip-requirements.txt index 3faaa65131..881a08c092 100644 --- a/pip-requirements.txt +++ b/pip-requirements.txt @@ -13,7 +13,7 @@ ## edk2-pytool-library==0.21.5 -edk2-pytool-extensions==0.27.4 +edk2-pytool-extensions==0.27.5 antlr4-python3-runtime==4.13.1 regex==2024.5.15 pygount==1.8.0