Skip to content

Releases: microsoft/mu_devops

v1.4.3

17 Jan 17:36
@github-actions github-actions
v1.4.3
6ce2faf
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v1.4.3

What's Changed

  • .sync/dependabot: Remove team reviewers @makubacki (#79)
    Change Details
      Removes the microsoft/project-mu-dependency-reviewers team from reviews to reduce messages with the automated workflow.

    Signed-off-by: Michael Kubacki michael.kubacki@microsoft.com



Full Changelog: v1.4.2...v1.4.3

Contributors

makubacki
Loading

v1.4.2

09 Jan 19:06
@github-actions github-actions
v1.4.2
a50cb30
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v1.4.2

What's Changed

  • Split approval and merge workflows @makubacki (#76)
    Change Details
      Split approval and merge workflows

    Splitting the workflows provides several benefits:

    1. Simplifies logic due to jobs being attached to separate triggers
      relevant for the specific job.
    2. Reduces number of status checks shown in PRs due to certain steps
      being skipped in irrelevant circumstances.
    3. Allows better workflow reuse.

    The reviewers are also dropped from dependabot PRs since the pending
    team reviewer is (1) not acted upon (2) can delay PR merging if the
    reviewer team has not reviewed the PR.

    The version is updated in anticipation of this change. It will be
    modified if the expected version changes before this PR is merged.

    Signed-off-by: Michael Kubacki michael.kubacki@microsoft.com



  • GitHub Action: Bump release-drafter/release-drafter from 5.21.1 to 5.22.0 @dependabot (#77)
    Change Details
      Bumps [release-drafter/release-drafter](https://github.com/release-drafter/release-drafter) from 5.21.1 to 5.22.0.
    Release notes

    Sourced from release-drafter/release-drafter's releases.

    v5.22.0

    What's Changed

    New

    Full Changelog: release-drafter/release-drafter@v5.21.1...v5.22.0

    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)

Full Changelog: v1.4.1...v1.4.2

Contributors

makubacki and dependabot
Loading

v1.4.1

05 Jan 22:37
@github-actions github-actions
v1.4.1
d469777
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v1.4.1

What's Changed

Read more

Contributors

makubacki and dependabot
Loading

v1.4.0

05 Jan 19:37
@github-actions github-actions
v1.4.0
109e86b
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v1.4.0

What's Changed

  • GitHub Action: Bump stefanbuck/github-issue-parser from 2 to 3 [Rebase \& FF] @dependabot (#69)
    Change Details
      Bumps [stefanbuck/github-issue-parser](https://github.com/stefanbuck/github-issue-parser) from 2 to 3.
    Release notes

    Sourced from stefanbuck/github-issue-parser's releases.

    v3.0.0

    3.0.0 (2022-10-19)

    Bug Fixes

    • deps: bump @​actions/core from 1.9.1 to 1.10.0 (284e5eb)
    • Ensure releases can be pinned to SHAs #23 (#39) (428eec3)

    Features

    • mitigating script injection attacks by passing issue body as env var (#42) (0b27d4a)

    BREAKING CHANGES

    • Add issue-body argument which is required from v3 onwards

    To mitigate script injection attacks, github-issue-parser v3 will require workflow authors to pass the issue body as an argument. By doing so you will follow GitHub's Good practices for mitigating script injection attacks 

    - uses: stefanbuck/github-issue-parser@v3
  id: issue-parser
  with:
    issue-body: ${{ github.event.issue.body }} # required
    template-path: .github/ISSUE_TEMPLATE/bug-report.yml # optional but recommended

    The previous checkbox output produced this:

     {
    "laravel": true,
    "svelte": true,
 }

    whereas the new output will be an array like this

    {
    "fav_frameworks": ["Laravel", "Svelte"]
}

    ... (truncated)

    Commits
    • 2e4d854 build
    • 55281d1 build(deps-dev): bump jest from 29.2.2 to 29.3.1
    • 3c9c1c3 build(deps-dev): bump jest from 29.1.2 to 29.2.2 (#49)
    • 741688b feat: add issue-body default (#47)
    • de423fc docs: Add migration section
    • 0b27d4a feat: mitigating script injection attacks by passing issue body as env var (#42)
    • 1d341cb feat: parse checkboxes (#21)
    • 284e5eb fix(deps): bump @​actions/core from 1.9.1 to 1.10.0
    • 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)

🚀 Features & ✨ Enhancements

  • Add auto approval for auto merge @makubacki (#68)
    Change Details
      The auto merge process needs two reviews to meet Project Mu branch protection policy requirements. This change auto approves dependency update pull requests so they can be auto merged.

    Signed-off-by: Michael Kubacki michael.kubacki@microsoft.com



Full Changelog: v1.3.1...v1.4.0

Contributors

makubacki and dependabot
Loading
0 Join discussion

v1.3.1

19 Dec 20:26
@github-actions github-actions
v1.3.1
665e97e
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v1.3.1

What's Changed

  • .sync/workflows: Add file sync notice to some files @makubacki (#67)
    Change Details
      These files were added without the notice in the copyright area that states the files should be updated in mu_devops.

    This change adds the notice.

    Signed-off-by: Michael Kubacki michael.kubacki@microsoft.com



  • .sync: Set recent workflows to a fixed version of mu\_devops @makubacki (#66)
    Change Details
      When some workflows were added recently, the reusable workflow file that the leaf files depend on in mu_devops did not exist yet.

    Therefore, those leaf files depended on the main branch instead
    of a mu_devops release tag as the files would be in the main
    branch as soon as the PR was merged.

    Now that all of the reusable workflows are in a tagged release
    (as of the v1.3.0 release), this change sets them to a fixed version
    of Mu DevOps as well.

    Signed-off-by: Michael Kubacki michael.kubacki@microsoft.com



📖 Documentation Updates

  • Add pull-request best practices guide @Erich-McMillan (#70)
    Change Details
      # Description

    Adds pull request best practices to CONTRIBUTING.md and references this document + pull request best practices in the pull_request_template.md so all contributors are confronted with this guide before they open a pull request rather than afterward by the bot.

    TODO:

    • ensure the relative path to CONTRIBUTING.md in pull_request_template.md is correct since dependent repos have different layout

Full Changelog: v1.3.0...v1.3.1

Contributors

Erich-McMillan and makubacki
Loading

v1.3.0

06 Dec 23:43
@github-actions github-actions
v1.3.0
03a10e5
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v1.3.0

What's Changed

🚀 Features & ✨ Enhancements

  • Add reusable Auto Merge workflow @makubacki (#60)
    Change Details
      Adds a new workflow that automatically merges pull requests in Project Mu repos under certain conditions.

    As automated bots pick up mundane tasks like syncing PIP module
    updates, submodules, files, and so on, an increasing number of
    pull requests can accumulate that essentially update dependencies
    we expect to be updated over time. In most cases, we simply care
    that the new update passes CI checks.

    This workflow is currently configured to automerge dependabot and
    uefibot pull requests.

    Files added:

    • .github/workflows/AutoMerger.yml - Reusable workflow to auto
      merge pull requests that meet given criteria.
    • .sync/workflows/leaf/auto-merge.yml - Leaf workflow file to
      auto merge pull requests in a given repo.

    Signed-off-by: Michael Kubacki michael.kubacki@microsoft.com



  • Add Issue Triage workflow @makubacki (#55)
    Change Details
      Closes #54

    Adds a new workflow and accompanying configuration files that
    apply labels to new issues based on options chosen by the submitter
    in an issue form.

    • .github/IssueTriager.yml - Single reusable workflow to apply
      labels to issues based on user input in issue forms.
    • .sync/workflows/config/triage-issues/advanced-issue-labeler.yml -
      Configures how labels are applied to issues based on issue form
      input.
    • .sync/workflows/leaf/triage-issues.yml - A leaf workflow that can
      be synced to repos to trigger the reusable workflow in Mu DevOps.

    This change also enables file syncing of this action to all repos
    that issue forms are currently being synced to.

    Signed-off-by: Michael Kubacki michael.kubacki@microsoft.com



Full Changelog: v1.2.0...v1.3.0

Contributors

makubacki
Loading
0 Join discussion

v1.2.0

06 Dec 23:23
@github-actions github-actions
v1.2.0
decf21f
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v1.2.0

What's Changed

🚀 Features & ✨ Enhancements

🐛 Bug Fixes

  • Fix incorrect changes to mu\_feature\_config custom Ubuntu-GCC5 pipeline @cfernald (#61)
    Change Details
      Fixes an incorrect change that resulted in an invalid pipeline file.

Full Changelog: v1.1.2...v1.2.0

Contributors

cfernald
Loading
0 Join discussion

v1.1.2

06 Dec 18:02
@github-actions github-actions
v1.1.2
f327f74
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v1.1.2

What's Changed

  • InstallMarkdownLint.yml: Update to markdownlint-cli 0.31.1 @makubacki (#15)
    Change Details
      Updates to the latest markdownlint-cli to stay current. 0.31.1 was released on 2/9/2022 per the version history:

    https://www.npmjs.com/package/markdownlint-cli

    Note: 0.32 introduces new failures in some repos that would need to be
    addressed before moving to 0.32.x. 0.32.2 was specifically tested.

    Signed-off-by: Michael Kubacki michael.kubacki@microsoft.com



🐛 Bug Fixes

  • .sync/azure-pipelines: Swap CLANGPDB VM image name @makubacki (#56)
    Change Details
      After this change: - `Ubuntu-CLANGPDB.yml` - Uses: `tool-chain-clangpdb-ubuntu-vm-image` - `Windows-CLANGPDB.yml` - Uses: `tool-chain-clangpdb-windows-vm-image`

    These were previously reversed.

    Signed-off-by: Michael Kubacki michael.kubacki@microsoft.com



Full Changelog: v1.1.1...v1.1.2

Contributors

makubacki
Loading

v1.1.1

03 Dec 00:12
@github-actions github-actions
v1.1.1
729de2b
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v1.1.1

What's Changed

🐛 Bug Fixes

  • label-issues: Invert functional impact label logic @makubacki (#48)
    Change Details
      Fixes #47

    The checkbox exposed to contributors in a PR to determine whether
    the PR has a functional impact states:

    "Impacts functionality?"

    This uses positive logic to simplify understanding by the user.

    Currently the impact:non-functional label is applied if the
    checkbox is checked.

    This change inverts the logic to apply the label as expected.

    Signed-off-by: Michael Kubacki michael.kubacki@microsoft.com



Full Changelog: v1.1.0...v1.1.1

Contributors

makubacki
Loading

v1.1.0

03 Dec 00:08
@github-actions github-actions
v1.1.0
960f5c0
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
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

Contributors

makubacki
Loading