Closed bhupeshbhatt1985 closed 2 days ago
Hi @bhupeshbhatt1985, 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.
Thank you for your contribution! We will review the pull request and get back to you soon.
Thank you for using our CodeGen tool. We value your feedback, and we would like to know how we can improve our product. Please take a few minutes to fill our codegen survey
For more info about extension versioning, please refer to Extension version schema
⚠️ Release Suggestions
Module: nsp
- ⚠️ Please update
VERSION
to be1.0.0b1
insrc/nsp/setup.py
Notes
- Stable/preview tag is inherited from last release. If needed, please add
stable
/preview
label to modify it.- Major/minor/patch/pre increment of version number is calculated by pull request code changes automatically. If needed, please add
major
/minor
/patch
/pre
label to adjust it.- For more info about extension versioning, please refer to Extension version schema
@bhupeshbhatt1985 please refer to this link for correcting module version update, thanks
⚠️ Release Suggestions
Module: nsp
- ⚠️ Please update
VERSION
to be1.0.0b1
insrc/nsp/setup.py
Notes
- Stable/preview tag is inherited from last release. If needed, please add
stable
/preview
label to modify it.- Major/minor/patch/pre increment of version number is calculated by pull request code changes automatically. If needed, please add
major
/minor
/patch
/pre
label to adjust it.- For more info about extension versioning, please refer to Extension version schema
@bhupeshbhatt1985 please refer to this link for correcting module version update, thanks
@AllyW updated to [1.0.0b1] as per suggestion and understanding from the document. Bot has removed the block tag after that but ci failing . please review and suggest if this is correct or not.
/azp run
[Release] Update index.json for extension [ nsp ] : https://dev.azure.com/azclitools/release/_build/results?buildId=168780&view=results
@kairu-ms Please don't release it. I need to make a fix.
@kairu-ms I raised another PR , fixing the issue. https://github.com/Azure/azure-cli-extensions/pull/7769 .
Description: Added support for service tag based perimeter access rule. Swagger updated to 2023-08-01-preview swagger changes . a
This checklist is used to make sure that common guidelines for a pull request are followed. aaz PR: https://github.com/Azure/aaz/pull/507
Related command
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
.