Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump azure-cli from 2.61.0 to 2.69.0 #325

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 17, 2025

Bumps azure-cli from 2.61.0 to 2.69.0.

Release notes

Sourced from azure-cli's releases.

Azure CLI 2.69.0

https://github.com/MicrosoftDocs/azure-docs-cli/blob/main/docs-ref-conceptual/release-notes-azure-cli.md

SHA256 hashes of the release artifacts

509e1e42184b36649a97256cc9f059cd5efa95ae2c7677411becac9e1870d03d  azure-cli-2.69.0-x64.msi
4748680e5a3806940b41b30175ddc088c4ec24b1c4b136e2a6b255510242500a  azure-cli-2.69.0-x64.zip
9aec25a2dee61060c69bebb04ac2e353889ead6b5a6b58d20f3108383ae89afb  azure-cli-2.69.0.msi

Azure CLI 2.68.0

https://github.com/MicrosoftDocs/azure-docs-cli/blob/main/docs-ref-conceptual/release-notes-azure-cli.md

SHA256 hashes of the release artifacts

ce472c48311d5ee414e07e160a7b3c76028665e8fd3d5e3bb6dd3713b0ebe5e9  azure-cli-2.68.0.msi
258beffe05ebe8faee9b7eb7b8db4fb875a4a38a60cb766a743304668b6a0c96  azure-cli-2.68.0-x64.msi
edd857baa5e3c87423d197f7dc3f5246f022b23f5308f1c03c3a9f2ead340570  azure-cli-2.68.0-x64.zip

Azure CLI 2.67.0

https://github.com/MicrosoftDocs/azure-docs-cli/blob/main/docs-ref-conceptual/release-notes-azure-cli.md

SHA256 hashes of the release artifacts

723cf2ac1d252ee086841dece0fff10538e15926d2c7ed1085d02c0f82b7393e  azure-cli-2.67.0-x64.msi
b8b31530939d8016ff23da4d2196a4286e9db6477117733c770b805b6fa64162  azure-cli-2.67.0-x64.zip
c4cdd13157968052bc2ffeecb4459d466de95d4b9ab8194963ab601d9f613c44  azure-cli-2.67.0.msi

Azure CLI 2.66.0

https://github.com/MicrosoftDocs/azure-docs-cli/blob/main/docs-ref-conceptual/release-notes-azure-cli.md

Azure CLI 2.65.0

https://github.com/MicrosoftDocs/azure-docs-cli/blob/main/docs-ref-conceptual/release-notes-azure-cli.md

Azure CLI 2.64.0

https://github.com/MicrosoftDocs/azure-docs-cli/blob/main/docs-ref-conceptual/release-notes-azure-cli.md

Azure CLI 2.63.0

https://github.com/MicrosoftDocs/azure-docs-cli/blob/main/docs-ref-conceptual/release-notes-azure-cli.md

Azure CLI 2.62.0

https://github.com/MicrosoftDocs/azure-docs-cli/blob/main/docs-ref-conceptual/release-notes-azure-cli.md

Changelog

Sourced from azure-cli's changelog.

How to introduce Breaking Changes in service command

Azure CLI has bi-annual breaking change releases coinciding with Microsoft Build and Ignite. Limiting breaking changes to twice a year provides a stable experience for customers while being able to keep up to date with the latest versions of Azure CLI and plan accordingly for announced breaking changes.

Breaking Changes in Azure CLI

A breaking change refers to a modification that disrupts backward compatibility with previous versions. The breaking changes could cause a customer's script or automation written in a previous version to fail.

The common examples of breaking changes include:

  • Modifying the names of parameters/commands.
  • Modifying the input logic of parameters.
  • Modifying the format or properties of result output.
  • Modifying the current behavior model.
  • Adding additional verification that changes CLI behavior.

To mitigate the impact of breaking changes, Azure CLI delays breaking changes and coordinates half-yearly Breaking Change Releases that bundle multiple breaking changes together. This approach helps users plan ahead and adapt to the modifications effectively.

Breaking Change Window

The breaking change window is a designated sprint that permits the merging of service command breaking changes. Any Pull Request merged during this sprint will be included in the subsequent Breaking Change Release.

The timing of the breaking change window in Azure CLI aligns with Microsoft Build and Microsoft Ignite. It normally occurs in May for Build and November for Ignite. So please prepare beforehand to align command breaking changes with Azure CLI team accordingly.

You could find the next Breaking Change Release plan in our milestones.

It's highlighted that the introduction of breaking changes is typically prohibited within non-breaking-change window, based on what we stated above for consistency and stable tooling experience.

Exceptions to this policy may be considered under extraordinary circumstances. We understand and would like to help out. There would be high-graded justifications required to provide the info Azure CLI can access.

Please note that providing the required info for assessment does not mean it will be assured to be green-lighted for breaking changes. Team will still make the decision based on the overall impact.

Pre-announce Breaking Changes

All breaking changes must be pre-announced two sprints ahead Release. It give users the buffer time ahead to mitigate for better command experience. There are two approaches to inform both interactive users and automatic users about the breaking changes.

  1. (Mandatory) Breaking Changes must be pre-announced through Warning Log while executing.
  2. (Automatic) Breaking Changes would be collected automatically and listed in Upcoming Breaking Change Document.

Workflow

Overview

  • CLI Owned Module
    • Service Team should create an Issue that requests CLI Team to create the pre-announcement several sprints ahead Breaking Change Window. The issue should include the label Breaking Change. The CLI team will look at the issue and evaluate if it will be accepted in the next breaking change release.
      • Please ensure sufficient time for CLI Team to finish the pre-announcement.
    • The pre-announcement should be released ahead of Breaking Change Window.
  • Service Owned Module
    • Service Team should create a Pull Request that create the pre-announcement several sprints ahead Breaking Change Window.
    • The pre-announcement should be released ahead of Breaking Change Window.
  • After releasing the pre-announcement, a pipeline would be triggered, and the Upcoming Breaking Change Documentation would be updated.

... (truncated)

Commits
  • cf83ff0 {Eventgrid} Fix az eventgrid domain topic event-subscription delete LRO issue...
  • fcb7bd7 {Release} Upgrade to Azure CLI 2.69.0 (#30758)
  • 54ff034 [App Config] az appconfig export: Update export help message for environmen...
  • 2f02ad0 [Network] az network virtual-appliance reimage: Allow reimage of virtual ma...
  • 05a5d8f {core} Fixed generic update issue. (#30703)
  • d60b5a8 {Core} Bump MSAL to 1.31.2b1 (#30727)
  • ac6f490 {IoT} az iot hub policy renew-key: Service-side HIS renewal of IoT Hub poli...
  • eddc651 [AppConfig] appconfig kv restore/show/list, appconfig revision list: Update...
  • aeb9a42 [Backup] az backup: Add support for new AFS Vault Standard Policies (#30531)
  • eb4feac add git hook notice (#30706)
  • Additional commits viewable 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 show <dependency name> 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)

Summary by Sourcery

Chores:

  • Update the azure-cli version to 2.69.0

Bumps [azure-cli](https://github.com/Azure/azure-cli) from 2.61.0 to 2.69.0.
- [Release notes](https://github.com/Azure/azure-cli/releases)
- [Changelog](https://github.com/Azure/azure-cli/blob/dev/doc/how_to_introduce_breaking_changes.md)
- [Commits](Azure/azure-cli@azure-cli-2.61.0...azure-cli-2.69.0)

---
updated-dependencies:
- dependency-name: azure-cli
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file python Pull requests that update Python code labels Feb 17, 2025
Copy link

gitstream-cm bot commented Feb 17, 2025

🚨 gitStream Monthly Automation Limit Reached 🚨

Your organization has exceeded the number of pull requests allowed for automation with gitStream.
Monthly PRs automated: 253/250

To continue automating your PR workflows and unlock additional features, please contact LinearB.

Copy link

sourcery-ai bot commented Feb 17, 2025

Reviewer's Guide by Sourcery

This pull request bumps the Azure CLI version in the dind environment from 2.61.0 to 2.69.0 by modifying the requirements.txt file.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change Details Files
The pull request upgrades the Azure CLI version used in the dind (Docker in Docker) environment.
  • Updated the azure-cli version from 2.61.0 to 2.69.0 in the requirements.txt file.
dind/requirements.txt

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!
  • Generate a plan of action for an issue: Comment @sourcery-ai plan on
    an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have skipped reviewing this pull request. Here's why:

  • It seems to have been created by a bot (hey, dependabot[bot]!). We assume it knows what it's doing!
  • We don't review packaging changes - Let us know if you'd like us to change this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file python Pull requests that update Python code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants