-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Sync fork #9507
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sync fork #9507
Conversation
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
|
Validation for Breaking Change Starting...
Thanks for your contribution! |
|
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>
|
|
Hi @saifaldin14
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR updates the migrate extension to version 2.0.1b1, marking it as a preview/experimental release. The changes transition the extension from the stable 2.0.0 release to a beta version with appropriate metadata flags.
Key Changes
- Version updated from "2.0.0" to "2.0.1b1" to indicate beta status
- Preview flag added to metadata to mark the extension as experimental
- Release history updated to document the transition
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| src/migrate/setup.py | Updates VERSION constant to "2.0.1b1" to reflect beta release |
| src/migrate/azext_migrate/azext_metadata.json | Adds "azext.isPreview": true to mark extension as preview |
| src/migrate/HISTORY.rst | Documents version 2.0.1b1 release with note about experimental version |
| 2.0.1b1 | ||
| +++++++++++++++ | ||
| * Switch to experimental version. |
Copilot
AI
Jan 7, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The version entry "2.0.1b1" should be placed at the top of the Release History section, not at the bottom. In HISTORY.rst files, versions are listed in reverse chronological order with the newest version first. Since "2.0.1b1" is the most recent version, it should appear above "2.0.0" in the file.
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.