Promote discovery extension to stable version 1.0.1 - #10172
Merged
Ethan Yang (necusjz) merged 1 commit intoAug 4, 2026
Conversation
- Remove beta suffix from version (1.0.1b1 -> 1.0.1) - Update classifier to Production/Stable - Add HISTORY.rst entry Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
Member
|
/azp run |
Contributor
There was a problem hiding this comment.
🟢 Ready to approve
Changes are consistent with the PR description, limited in scope to version/metadata and history updates, and contain no apparent functional risk.
This review doesn't count toward merge requirements. Sign up for the private preview to control whether Copilot approvals count.
Pull request overview
This PR promotes the discovery Azure CLI extension from beta to a stable release by updating its package metadata and release notes to reflect version 1.0.1.
Changes:
- Bump extension version from
1.0.1b1to stable1.0.1. - Update PyPI classifier from Beta to Production/Stable.
- Add a
1.0.1entry toHISTORY.rstnoting the promotion to stable.
File summaries
| File | Description |
|---|---|
| src/discovery/setup.py | Updates version and development status classifier to reflect a stable 1.0.1 release. |
| src/discovery/HISTORY.rst | Adds release notes for 1.0.1 indicating promotion to stable. |
Review details
- Files reviewed: 2/2 changed files
- Comments generated: 0
- Review effort level: Lite
We're testing this review assessment. Please use 👍 or 👎 to tell us if it's correct.
|
Azure Pipelines: Successfully started running 2 pipeline(s). |
Collaborator
|
discovery |
Ethan Yang (necusjz)
approved these changes
Aug 4, 2026
Collaborator
|
[Release] Update index.json for extension [ discovery-1.0.1 ] : https://dev.azure.com/msazure/One/_build/results?buildId=175028455&view=results |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 PR Validation — ️✔️ All clear
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
az discoveryGeneral Guidelines
azdev style <YOUR_EXT>locally? (pip install azdevrequired)python scripts/ci/test_index.py -qlocally? (pip install azdevrequired)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.