Skip to content

Conversation

@rsinghal26
Copy link
Member

@rsinghal26 rsinghal26 commented Oct 29, 2025


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:

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.

Copilot AI review requested due to automatic review settings October 29, 2025 12:24
@azure-client-tools-bot-prd
Copy link

Hi @rsinghal26,
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.

@azure-client-tools-bot-prd
Copy link

Validation for Breaking Change Starting...

Thanks for your contribution!

@yonzhan
Copy link
Collaborator

yonzhan commented Oct 29, 2025

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

@github-actions
Copy link

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).
After that please run the following commands to enable git hooks:

pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>

@github-actions
Copy link

CodeGen Tools Feedback Collection

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

@github-actions
Copy link

github-actions bot commented Oct 29, 2025

Hi @rsinghal26

Release Suggestions

Module: neon

  • Update VERSION to 1.0.1b2 in src/neon/setup.py

Notes

Copy link
Contributor

Copilot AI left a 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 introduces breaking change notifications for the Azure Neon CLI extension, announcing its deprecation and end-of-life date. The implementation adds proper deprecation warnings to inform users about the service sunset and provides migration guidance.

  • Registers the 'az neon' command group as deprecated
  • Adds a detailed deprecation notice with EOL date and migration documentation link

register_command_group_deprecate('az neon')

message = """Deprecation Notice: The Neon Azure Native Integration is being deprecated and will
reach end of life on January 31, 2026. Transfer your projects to a Neon managed organization
Copy link

Copilot AI Oct 29, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nitpick] The deprecation message should include information about when the deprecation was announced or when the warning period started. This helps users understand the timeline and urgency of the migration.

Suggested change
reach end of life on January 31, 2026. Transfer your projects to a Neon managed organization
reach end of life on January 31, 2026. Deprecation announced on June 1, 2024. Transfer your projects to a Neon managed organization

Copilot uses AI. Check for mistakes.
Comment on lines +5 to +11
register_command_group_deprecate('az neon')

message = """Deprecation Notice: The Neon Azure Native Integration is being deprecated and will
reach end of life on January 31, 2026. Transfer your projects to a Neon managed organization
today. Migration documentation is available at https://neon.com/docs/import/migrate-from-azure-native"""

register_other_breaking_change('az neon', message)
Copy link

Copilot AI Oct 29, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nitpick] Consider defining the command group name 'az neon' as a constant (e.g., COMMAND_GROUP = 'az neon') to avoid duplication on lines 5 and 11, improving maintainability if the command group name needs to change.

Suggested change
register_command_group_deprecate('az neon')
message = """Deprecation Notice: The Neon Azure Native Integration is being deprecated and will
reach end of life on January 31, 2026. Transfer your projects to a Neon managed organization
today. Migration documentation is available at https://neon.com/docs/import/migrate-from-azure-native"""
register_other_breaking_change('az neon', message)
COMMAND_GROUP = 'az neon'
register_command_group_deprecate(COMMAND_GROUP)
message = """Deprecation Notice: The Neon Azure Native Integration is being deprecated and will
reach end of life on January 31, 2026. Transfer your projects to a Neon managed organization
today. Migration documentation is available at https://neon.com/docs/import/migrate-from-azure-native"""
register_other_breaking_change(COMMAND_GROUP, message)

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants