Bump azure/CLI from 68f0d36771d0cba0ebbf26993275a8e0b74a541f to d88d5767d50cde2679128b45d287ec5b98df892e

[dependabot]

Bumps azure/CLI from 68f0d36771d0cba0ebbf26993275a8e0b74a541f to d88d5767d50cde2679128b45d287ec5b98df892e.

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)

• git tag -fa v1 -m "Update v1 tag"
• git push origin v1 --force

Commits

• d88d576 Add changes
• 6717244 Fix #103: Dealing with un-escaped environment variables by using args (#105)
• See full diff in compare view

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)

[github-actions]

This dependency update will be handled internally by our engineering team.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.