[CosmosDB] 2024-12-01-preview release package versioning.#8441
[CosmosDB] 2024-12-01-preview release package versioning.#8441evelyn-ys merged 2 commits intoAzure:mainfrom
Conversation
️✔️Azure CLI Extensions Breaking Change Test
|
|
Hi @pjohari-ms, |
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR. Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
|
@evelyn-ys this is a followup PR to #8323 that adds the package versioning. |
|
|
This is 1.2.0b1 and not 1.1.0b2 because we have added a new feature. |
cc @AllyW for the version issue |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
@evelyn-ys @AllyW if there are no versioning issues, can we merge this PR and release the package? |
|
[Release] Update index.json for extension [ cosmosdb-preview-1.2.0b1 ] : https://dev.azure.com/msazure/One/_build/results?buildId=114430075&view=results |
* Added versioning * Added release version in setup.py
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
General Guidelines
azdev style <YOUR_EXT>locally? (pip install azdevrequired)python scripts/ci/test_index.py -qlocally? (pip install wheel==0.30.0required)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.