Closed Netyyyy closed 3 months ago
Hi @Netyyyy, 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
Please fix CI issues.
Please fix CI issues.
Fixed
@zhoxing-ms @yonzhan @yanzhudd , please help take a review, and The failed CI is warning about the original code. Let us keep this PR clean for the new feature and we commit the incremental code passed all CI check.
@yanzhudd do not know why pipeline failed after updating HISTORY.md and do not have a re-run permission, please help take a look
/azp run
Hi @yanzhudd please help approve and merge, thanks
[Release] Update index.json for extension [ spring ] : https://dev.azure.com/azclitools/release/_build/results?buildId=169315&view=results
Verify that
artifact-path
andsource-path
exist before all steps inaz spring app deploy
,az spring app deployment create
andaz spring job deploy
commands.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
.