What's Changed

Full Changelog: https://github.com/microsoft/mu_devops/compare/v11.0.2...v11.0.3

What's Changed

Full Changelog: https://github.com/microsoft/mu_devops/compare/v11.0.1...v11.0.2

What's Changed

There is a follow up item tracked in https://github.com/microsoft/mu_devops/issues/358 to make PR descriptions more consistently filled out so they appear as expected in release notes.

The cargo config file will be synced to Rust enabled
repos to apply the linker flags regardless of whether
the Rust code is compiled directly or through the
firmware build system.

Full Changelog: https://github.com/microsoft/mu_devops/compare/v11.0.0...v11.0.1

What's Changed

⚠️ Breaking Changes

🚀 Features & ✨ Enhancements

🐛 Bug Fixes

  </blockquote>
  <hr>
</details>

Full Changelog: https://github.com/microsoft/mu_devops/compare/v10.1.1...v11.0.0

What's Changed

Full Changelog: https://github.com/microsoft/mu_devops/compare/v10.1.0...v10.1.1

What's Changed

This change sets up file syncing to the repo and adds the repo to the
GitHub notebooks.

This is needed so that "make" does not complain about the clang install path has space in it.

This change sets up file syncing to the repo and adds the repo to the
GitHub notebooks.

🚀 Features & ✨ Enhancements

This change follows the pattern of depending on platforms to specify
their default architecture for the build.

Full Changelog: https://github.com/microsoft/mu_devops/compare/v10.0.0...v10.1.0

What's Changed

⚠️ Breaking Changes

Full Changelog: https://github.com/microsoft/mu_devops/compare/v9.2.0...v10.0.0

What's Changed

🚀 Features & ✨ Enhancements

See https://git-scm.com/docs/gitattributes for background.

This was previously accomplished solely by instructing users to set
core.autocrlf to false. However, that does not translate to pipelines
and setting in a pipeline requires the system level git configuration
to be modified prior to checkout. Git configs cannot be checked into
to a repo and automatically used for security reasons.

This is a simple way to check the change into the repo so it applies
for all users including pipelines to prevent line ending conversion.

This allows plugins like LineEndingCheck to produce similar results
in pipelines on Linux and Windows agents.

Full Changelog: https://github.com/microsoft/mu_devops/compare/v9.1.10...v9.2.0

What's Changed

Full Changelog: https://github.com/microsoft/mu_devops/compare/v9.1.9...v9.1.10

What's Changed

General release info: https://github.com/microsoft/mu_devops/releases

This change is needed to finishing syncing the Rust version update change.

• https://blog.rust-lang.org/2024/02/08/Rust-1.76.0.html

Tested builds in Rust repos with 1.76.0.

Full Changelog: https://github.com/microsoft/mu_devops/compare/v9.1.8...v9.1.9

What's Changed

Since this is a pipeline run, we have no need to update rustup, and can rely on the version provided by the runner. By disabling the self update, the file conflict The process cannot access the file because it is being used by another process no longer appears as seen in this test PR: https://dev.azure.com/projectmu/mu/_build/results?buildId=65795&view=results

Full Changelog: https://github.com/microsoft/mu_devops/compare/v9.1.7...v9.1.8

What's Changed

Sets the target via the expected way, TARGET=DEBUG.

General release info: https://github.com/microsoft/mu_devops/releases

Includes:

• Sync RustSetupSteps.yml to use cargo-binstall to install cargo binary tools (#320)
• Update RustSetupSteps.yml (#321)
• Repo File Sync: synced file(s) with microsoft/mu_devops (#322)
• .sync/workflows/codeql: Use Version.njk cargo-make version (#323)

In particular, including #320 in this tag allows downstream repos to use the changes.

Full Changelog: https://github.com/microsoft/mu_devops/compare/v9.1.6...v9.1.7

What's Changed

Note: We can consider using cargo binstall in the future but right now
only cargo-make is needed, and it is simple to directly cache that binary
as-is with existing code.

Full Changelog: https://github.com/microsoft/mu_devops/compare/v9.1.5...v9.1.6

What's Changed

https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/nuget-authenticate-v0?view=azure-pipelines
https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/nuget-authenticate-v1?view=azure-pipelines

Fixes #289

Adds .tgz (short for .tar.gz) support to the DownloadCargoBinaryFromGitHub.py script. Also fixes a logic error in the conditional that decides which assets to download.

See successful pipeline run: https://dev.azure.com/projectmu/mu/_build/results?buildId=64211&view=logs&j=402df595-8a03-57d0-41e1-0654a1932349

Full Changelog: https://github.com/microsoft/mu_devops/compare/v9.1.4...v9.1.5

What's Changed

.sync/workflows/codeql-platform: Update irrelevant plugin removal dir

Updates the directory used for irrelevant plugin removal in this
workflow to match codeql.yml which using the pytool directory rather
than the directory the CodeQL plugin is found in.

This is important because the CodeQL plugin moved from .pytool to
BaseTools in Mu release 202311 so the plugin dir needs to be fixed
rather than relative to the CodeQL plugin location.

.sync/workflows/codeql: Add more inline documentation

Updates and adds some additional comments to the CodeQL workflow
files to give better context.

Full Changelog: https://github.com/microsoft/mu_devops/compare/v9.1.3...v9.1.4

What's Changed

extra_install_steps can be used to pass a call to another stuart_update to include the --codeql parameter.

Full Changelog: https://github.com/microsoft/mu_devops/compare/v9.1.2...v9.1.3

What's Changed

Also updates references to 202302 throughout the repo to prevent the
examples from getting too stale over time.

Full Changelog: https://github.com/microsoft/mu_devops/compare/v9.1.1...v9.1.2

What's Changed

🔐 Security Impacting

With MU_BASECORE's Settings -> Code and automation -> Actions -> General -> Workflow permissions set to "Read repository contents and packages permissions" selected, I had no failures, with the following tested:

.github/workflows

• AutoMerger.yml - Untested
• FileSyncer.yml - Tested
• IssueAssignment.yml - Tested
• IssueTriager.yml - Tested
• LabelSyncer.yml - Tested
• Labeler.yml - Tested
• ReleaseDrafter.yml - Tested

.sync/workflows/leaf

• auto-approve.yml - Untested
• auto-merge.yml - Untested
• issue-assignment.yml - Tested through IssueAssignment.yml
• label-issues.yml - Tested through Labeler.yml
• label-sync.yml - Tested through LabelSyncer.yml
• pull-request-formatting-validator.yml - Tested Directly
• release-draft.yml - Tested through ReleaseDrafter.yml
• scheduled-maintenance.yml - Tested Directly
• stale.yml - Tested Directly
• submodule-release-update.yml - Untested
• triage-issues.yml - Tested
  
  

Full Changelog: https://github.com/microsoft/mu_devops/compare/v9.1.0...v9.1.1

What's Changed

🚀 Features & ✨ Enhancements

Eventually, the .pytool fallback can be removed.

Issue to track removal of the fallback: https://github.com/microsoft/mu_devops/issues/300

🐛 Bug Fixes

That change didn't take into account how all branches from release/202302 and older have the .pytool/Plugin version of CodeQL and was deleting all plugins in .pytool besides CompilerPlugin. This change excludes the CodeQL plugin if it exists as well.

Full Changelog: https://github.com/microsoft/mu_devops/compare/v9.0.6...v9.1.0

What's Changed

setting the variable FEATURES will translate to passing --features <features> to the underlying build command.

Full Changelog: https://github.com/microsoft/mu_devops/compare/v9.0.5...v9.0.6