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 1 to 2 #71

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 18, 2024

Bumps azure/CLI from 1 to 2.

Release notes

Sourced from azure/CLI's releases.

GitHub Action for Azure CLI v2

What's Changed

New Contributors

Full Changelog: Azure/cli@v1.0.9...v2

GitHub Action for Azure CLI v1.0.9

  • Set action failure on a non-Linux-based OS (#123)

GitHub Action for Azure CLI v1.0.8

  • Fix #103: Dealing with un-escaped environment variables which cause escalation of privilege (#105)

GitHub Action for Azure CLI v1.0.7

  • Upgraded action to use node 16 instead of node 12
  • Upgrade @​actions/core to ^1.10.0
  • Resolved other minor issues like Azure/cli#87 and Azure/cli#84

GitHub Action for Azure CLI v1.0.6

Resolved customer issue: Error: /bin/sh: 1: az: not found in v1.0.5 Azure/cli#62

GitHub Action for Azure CLI v1.0.5

Resolved compatibility issues between az cli version on agent and container.

[email protected]

  1. Adding support for using env. variables via GITHUB_ENV
  2. Security vulnerability fix

GitHub Action for Azure CLI v1.0.3

User-defined environment variables present in the workflow are now accessible while execution of Azure CLI script.

GitHub Action for Azure CLI v1.0.2

Default environment variables provided by GitHub are now accessible while execution of Azure CLI script. Environment variables with prefix GITHUB_* are accessible during the script execution.

GitHub Action for Azure CLI v1.0.1

GITHUB_SHA default environment variable is available to use in the script.

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

Dependabot compatibility score

You can trigger a rebase of this PR 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

Bumps [azure/CLI](https://github.com/azure/cli) from 1 to 2.
- [Release notes](https://github.com/azure/cli/releases)
- [Changelog](https://github.com/Azure/cli/blob/master/ReleaseProcess.md)
- [Commits](Azure/cli@v1...v2)

---
updated-dependencies:
- dependency-name: azure/CLI
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Mar 18, 2024
@zwolf
Copy link
Member

zwolf commented Jul 1, 2024

@dependabot rebase

Copy link
Contributor Author

dependabot bot commented on behalf of github Jul 1, 2024

Looks like azure/CLI is up-to-date now, so this is no longer needed.

@dependabot dependabot bot closed this Jul 1, 2024
@dependabot dependabot bot deleted the dependabot/github_actions/azure/CLI-2 branch July 1, 2024 18:06
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant