From 5888f6eb7f7b49b6cfa794ab448e3169f790af9c Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Wed, 1 Apr 2026 22:22:51 +0200 Subject: [PATCH] Chore(deps): Bump azure/cli from 2 to 3 (#46562) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Bumps [azure/cli](https://github.com/azure/cli) from 2 to 3.
Release notes

Sourced from azure/cli's releases.

GitHub Action for Azure CLI v3

What's Changed

Full Changelog: https://github.com/Azure/cli/compare/v2.2.0...v3

GitHub Action for Azure CLI v3.0.0

What's Changed

Full Changelog: https://github.com/Azure/cli/compare/v2.2.0...v3.0.0

GitHub Action for Azure CLI v2.2.0

What's Changed

New Contributors

Full Changelog: https://github.com/Azure/cli/compare/v2.1.0...v2.2.0

GitHub Action for Azure CLI v2.1.0

What's Changed

New Contributors

Full Changelog: https://github.com/Azure/cli/compare/v2.0.0...v2.1.0

Changelog

Sourced from azure/cli's changelog.

Releasing a new version

Semanting versioning is used to release different versions of the action. Following steps are to be followed :

  1. Create a new branch for every major version.
    Example, releases/v1, releases/v2.
  2. For every minor and patch release for a major version, update the corresponding release branch.
    Example, for releasing v1.1.1, update releases/v1.
  3. Create tags for every new release (major/minor/patch).
    Example,v1.0.0. , v1.0.1, v2.0.1, etc. and also have tags like v1, v2 for every major version release.
  4. On releasing minor and patch versions, update the tag of the corresponding major version.
    Example, for releasing v1.0.1, update the v1 tag to point to the ref of the current release.
    The following commands are to be run on the release\v1 branch so that it picks the latest commit and updates the v1 tag accordingly : (Ensure that you are on same commit locally as you want to release)
Commits

[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=azure/cli&package-manager=github_actions&previous-version=2&new-version=3)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) ---
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 show ignore conditions` will show all of the ignore conditions of the specified dependency - `@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)
Signed-off-by: dependabot[bot] Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> --- .github/workflows/msstore-submissions.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/msstore-submissions.yml b/.github/workflows/msstore-submissions.yml index 36dfc4d785..85d758df12 100644 --- a/.github/workflows/msstore-submissions.yml +++ b/.github/workflows/msstore-submissions.yml @@ -47,7 +47,7 @@ jobs: - uses: microsoft/setup-msstore-cli@v1 - name: Fetch Store Credential - uses: azure/cli@v2 + uses: azure/cli@v3 with: azcliversion: latest inlineScript: |-