Sourced from azure/CLI's releases.
GitHub Action for Azure CLI v2
What's Changed
- Update Action to use Node.js v20 by
@eikooc
in Azure/cli#126- Bump dependencies to the latest versions by
@MoChilia
in Azure/cli#135New Contributors
@eikooc
made their first contribution in Azure/cli#126Full Changelog: https://github.com/Azure/cli/compare/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
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#62GitHub Action for Azure CLI v1.0.5
Resolved compatibility issues between az cli version on agent and container.
cli@v1.0.4
- Adding support for using env. variables via GITHUB_ENV
- 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.
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 :
- Create a new branch for every major version.
Example, releases/v1, releases/v2.- For every minor and patch release for a major version, update the corresponding release branch.
Example, for releasing v1.1.1, update releases/v1.- 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.- 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
965c8d7
Release v24343bca
update readme for v2 (#140)0150783
Add changes4b557fa
Use process.env
instead of core.exportvariable
to set env (#138)12aaf8e
remove env for integration test (#137)09e9174
Add changesbf9d5ac
Bump dependencies to the latest versions (#135)f3881a6
{Automation} Add CI tests (#136)3994327
Update action node version from v16 to v20(#126)9849316
add permission block (#130)