v1.1.0

What's Changed

🚀 Features & ✨ Enhancements

• Add Semantic Versioning Release workflow [Rebase \& FF] @makubacki (#49)
  
  Change Details

    Closes #50

  Adds a new workflow and accompanying configuration files that allow
  releases to automatically be drafted in repos as pull requests are
  completed.

  Semantic versioning is automatically determined based on the standard
  set of Project Mu labels associated with the pull request.

  The types of changes (e.g. bug fix, new feature, etc.) are
  automatically categorized in the pull request based on the labels as
  well.

  This makes tracking the new Semantic Version based on the type of
  changes automatic and a release is always ready. In between releases,
  the draft is a nice way to see a high-level delta since the last
  release.

  • .github/ReleaseDrafter.yml - Single reusable workflow to maintain
    a release draft as pull requests complete.
  • .github/ReleaseDraft.yml - Configuration file for the
    ReleaseDrafter workflow. Defines label meanings for releases and
    how releases should be drafted.
  • .sync/workflows/leaf/release-draft.yml - A leaf workflow that can
    be synced to repos to trigger the reusable workflow in Mu DevOps.

  Project Mu repos can easily opt into consistent release drafting by
  including this leaf workflow via file sync.

  ---

  I decided to allow dependabot changes into release and just not include
  file sync changes since those are dev ops related and already tracked in
  the mu_devops releases where they're more relevant.
  

  
  

  ---

  
  

Full Changelog: v1.0.0...v1.1.0

v1.0.0

About This Release

This release is incrementing the major version to baseline the version before moving to a model that will update releases as pull requests are submitted.

The main functional change since v0.1.0 in this release was setting the dependencies in Project Mu repos to a fixed version of this repo.

What's Changed

• ReadMe.rst: Add file sync status badge by @makubacki in #43
• Fix Mu DevOps Version Used on Release Version [Rebase & FF] by @makubacki in #45
• Repo File Sync: Synced file(s) with microsoft/mu_devops by @uefibot in #46

Full Changelog: v0.1.0...v1.0.0

v0.1.0

About This Release

This is the first Mu DevOps release 🎉

Currently, Mu DevOps serves common build content across Project Mu repos. The goal is to centralize most of the CI and build related files needed to manage the repos.

One of these components are Azure Pipelines files (see Jobs and Steps). The actual Project Mu repos have very minimal wrappers around these templates and they access the templates via a repository resource.

This is done as follows:

resources:
  repositories:
    - repository: mu_devops
      type: github
      endpoint: microsoft
      name: microsoft/mu_devops
      ref: main

A key reason to label this repo is to control fixed updates by setting ref to the release tag (v0.1.0 for this release) instead of main. Because main is a "floating" dependency, it provides rapid adoption of changes, but we'd prefer to update in fixed increments after the repo absorbing the new mu_devops update can test the change in a pull request (that updates the ref value).

Releases can be useful for other purposes as well. The version follows Semantic Versioning and the plan is to increment the major version on any backward incompatible change to:

1. An Azure Pipelines template file
   • Files presently in the Jobs or Steps directory of this repo
2. A GitHub reusable workflow file
   • Files presently in the .github/workflows directory of this repo

These are the two main sources of dependencies on the content of this repo from external files at this time. The cause of major version changes in the future may change as new files and features are introduced to the repo.

What's Changed

• Add initial content by @makubacki in #1
• Steps/PrGate.yml: Add pkg_count condition to build steps by @makubacki in #3
• PrGate.yml: Add do_pr_eval template parameter by @makubacki in #2
• Jobs/PrGate.yml: Pass do_pr_eval value to step template by @makubacki in #4
• Add CodeQL reusable GitHub workflow by @makubacki in #5
• Add Project Mu status notebooks by @makubacki in #6
• Add initial support for containers in PrGate job by @cfernald in #9
• ApplyAdoBranchNameWorkaround.yml: Add file by @makubacki in #10
• Steps/ApplyAdoBranchNameWorkaround.yml: Fix error from conflict resolution by @makubacki in #11
• Allow additional build artifacts to be upload for platform build by @cfernald in #12
• Fix PR gates for CI and platform build by @cfernald in #13
• SetNodeVersion.yml: Use Node.js 19.x by @makubacki in #14
• Steps/PrGate.yml: Add extra install step parameter by @makubacki in #17
• PrGate.yml: Add support for publishing code coverage results by @makubacki in #16
• Simplify job names by @makubacki in #18
• Fix PR Eval typo (present since 201911) by @makubacki in #19
• Update code to align with previous isOutput bug behavior by @makubacki in #20
• Add support for platform build using containers by @cfernald in #21
• Revert container updates in 5f3c041 by @makubacki in #22
• Switch to simple boolean for using container build by @cfernald in #24
• SetupPythonPreReqs.yml: Upgrade pip and install wheel and setuptools by @makubacki in #25
• Add reusable Stale GitHub workflow by @makubacki in #27
• Add reusable GitHub Label Sync workflow by @makubacki in #30
• Update Project Mu GitHub Automation [Rebase & FF] by @makubacki in #32
• FileSyncer.yml: Add microsoft prefix to review team by @makubacki in #36
• CONTRIBUTING.md: Fix long line for markdownlint by @makubacki in #37
• Repo File Sync: Synced file(s) with microsoft/mu_devops by @uefibot in #35
• .sync/markdownlint.yaml: Templatize allowed HTML elements by @makubacki in #38
• .sync/markdownlint.yaml: Update brace syntax by @makubacki in #41

New Contributors

• @makubacki made their first contribution in #1
• @cfernald made their first contribution in #9
• @uefibot made their first contribution in #35

Full Changelog: https://github.com/microsoft/mu_devops/commits/v0.1.0