-
Notifications
You must be signed in to change notification settings - Fork 227
Added spec for 'package updater' tools #12563
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
Conversation
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 introduces a comprehensive specification for "package updater" tools in the Azure SDK CLI workflow. The spec formalizes Stage 6 of SDK preparation—the housekeeping tasks performed after code generation and validation but before creating release PRs. It defines four composable CLI and MCP tools (CI Update, Changelog Update, Version Update, Metadata Update) that standardize metadata and documentation updates across all supported SDK languages.
Key Changes:
- Defines four discrete, composable tools with structured JSON outputs for deterministic orchestration
- Establishes explicit behavioral differences between management-plane and data-plane SDK workflows
- Specifies PowerShell-based script interfaces with standardized parameters and error handling conventions
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
Copilot reviewed 1 out of 1 changed files in this pull request and generated 5 comments.
timovv
left a comment
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.
Overall looks fine to me
richardpark-msft
left a comment
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.
Looks great, I'm sure we'll find out more when we implement it but the outline looks fine.
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.
Minor comments, Lgtm 🎉
|
|
||
| Execution Steps (Data-Plane): | ||
|
|
||
| 1. Return `noop` result advising manual edit and future version bump timing. |
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.
I believe every language would at least have formats with content headers and specifications that need to be in the Readme, we can/should link to that.
weidongxu-microsoft
left a comment
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.
If Haoling has change request, feel free to make a follow-up PR.
|
@raych1 Thanks for adding the configuration and example. It is very helpful for language to do integration! |
Ported the original docs specs into the new spec layout.
Added new content and clarifications to match the updated format.
See issue Spec: package metadata and docs update #11827 for scope and follow-ups.