Releases 0.27.0

[v-soujanya]

---

This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
• My extension version conforms to the Extension version schema

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

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.

[azure-client-tools-bot-prd]

️✔️Azure CLI Extensions Breaking Change Test

️✔️Non Breaking Changes

[azure-client-tools-bot-prd]

Hi @v-soujanya,
Since the current milestone time is less than 7 days, this pr will be reviewed in the next milestone.

[azure-client-tools-bot-prd]

Hi @v-soujanya,
Please write the description of changes which can be perceived by customers into HISTORY.rst.
If you want to release a new extension version, please update the version in setup.py as well.

[yonzhan]

Thank you for your contribution! We will review the pull request and get back to you soon.

[v-soujanya]

Hi Team, we tried multiple attempts but verify extension index check is continuously failing, we need your assistance here. From our end we have published the latest version with 0.27.0 & we are able to download the whl file.
Release link:
https://github.com/Azure/azure-devops-cli-extension/releases
Whl file link:
https://github.com/Azure/azure-devops-cli-extension/releases/download/20240129.4/azure_devops-0.27.0-py2.py3-none-any.whl
Below is the error we are seeing in the pipeline url
https://dev.azure.com/azclitools/public/_build/results?buildId=125766&view=logs&j=b121d099-c3c0-52ad-95f1-31c1567c9ad4&t=ca40adef-e63f-5fd5-f30e-e39a0bf0e914

Error:

Traceback (most recent call last):
File "/mnt/vss/_work/1/s/./scripts/ci/test_index.py", line 208, in test_metadata
self.assertDictEqual(metadata, item['metadata'],
AssertionError: {'aze[835 chars]3.0)', 'distro==1.3.0']}], 'summary': 'Tools f[43 chars]7.0'} != {'aze[835 chars]3.0)']}], 'summary': 'Tools for managing Azure[26 chars]7.0'}
Diff is 1423 characters long. Set self.maxDiff to None to see it. : Metadata for azure_devops-0.27.0-py2.py3-none-any.whl in index doesn't match the expected of:

[v-soujanya]

@jsntcy could you please help on this??

[jsntcy]

I'm curious why you update the entry for 0.26.0, usually we need add a new item for 0.27.0.

[v-soujanya]

@jsntcy This was the new release version we published on devops extension. Below is the last PR we made changes as same to release new version.
#5803

[v-soujanya]

@jsntcy any update on this??

[jsntcy]

You should not overwrite metadata of 0.26.0 for new version 0.27.0, because if you did like that, cx cannot install 0.26.0 any longer once you release 0.27.0. You should add a new entry for 0.27.0 like all other extensions did, an example: 5ce810e.

You can see that many previous versions are not available for cx now because you overwrite the metadata of previous versions before, that's not the correct behavior for cx.

[jsntcy]

BTW,
Now we support new versioning for extension and 0.x.x is not recommended any longer. The version will start from 1.0.0 (stable) or 1.0.0b1 (preview). You can find more details in https://github.com/Azure/azure-cli/blob/dev/doc/extensions/versioning_guidelines.md.
Please use the correct version next time: 1.0.0 (stable) or 1.0.0b1 (preview).

[v-soujanya]

HI @jsntcy, our new version is 0.27.0 as per the new version guidelines we are making it as 1.27.0. Please confirm is it okay?? post your confirmation I will create a new entry with the new version.

[v-anvashist]

Hi @jsntcy Any suggestions on above ask by Soujanya from your end? We need to do some more changes with the new rule conventions so taking suggestions here first.

[jsntcy]

HI @jsntcy, our new version is 0.27.0 as per the new version guidelines we are making it as 1.27.0. Please confirm is it okay?? post your confirmation I will create a new entry with the new version.

If it's stable version, we recommend you use version 1.0.0 as it's first version from1.x.x.