-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[confcom] updating history version #6801
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
Conversation
updating history formatting and version number
️✔️Azure CLI Extensions Breaking Change Test
|
|
Hi @SethHollandsworth, |
|
Hi @SethHollandsworth, |
|
confcom |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
using smaller images for tests
|
[Release] Update index.json for extension [ confcom ] : https://dev.azure.com/azclitools/internal/_build/results?buildId=97476&view=results |
Updating history version for better formatting and having a release will update the extension to have the newest version of dmverity-vhd from hcsshim
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
az confcom
General Guidelines
azdev style <YOUR_EXT>locally? (pip install azdevrequired)python scripts/ci/test_index.py -qlocally?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.jsonautomatically.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.