-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[az vm repair] version 1.0.0b1 #7113
Conversation
️✔️Azure CLI Extensions Breaking Change Test
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
azdev style check passes locally |
src/vm-repair/setup.py
Outdated
@@ -8,7 +8,7 @@ | |||
from codecs import open | |||
from setuptools import setup, find_packages | |||
|
|||
VERSION = "0.5.9" | |||
VERSION = "0.5.10" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use version 1.0.0b1
as preview version instead since we should never use 0.x.x
as versioning now. See more details in https://github.com/Azure/azure-cli/blob/dev/doc/extensions/versioning_guidelines.md
@jsntcy The azdev style check is failing but not sure what the error is. |
[Release] Update index.json for extension [ vm-repair ] : https://dev.azure.com/azclitools/internal/_build/results?buildId=119526&view=results |
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
az vm repair run
Bug fix for invoking az vm repair run on windows
General Guidelines
azdev style <YOUR_EXT>
locally? (pip install azdev
required)python scripts/ci/test_index.py -q
locally? (pip install wheel==0.30.0
required)For new extensions:
About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update
src/index.json
automatically.You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify
src/index.json
.