Repository navigation
Conversation
Update the CLI SDK pin to the pending 1.36.0 release that includes typed Fabric Spark attachment support. Existing attach, detach, show, and list commands need no handler changes. Authored-by: GitHub Copilot CLI v1.0.88 Model: GPT-6 Sol (gpt-6-sol) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 31c47880-d3a1-4cc6-a893-ab264315c7db
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
microsoft-github-policy-service
Bot
requested review from
ZelinWang (wangzelin007) and
Yong Zhang (yonzhan)
October 12, 2026 22:03
Contributor
|
Thank you for your contribution vaibhj! We will review the pull request and get back to you soon. |
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
The pinned SDK version is unpublished and its upstream implementation remains blocked.
0 open findings
What changed in this PR
Updates the ML extension’s SDK dependency to enable FabricSpark compute support through existing CLI handlers.
Changes:
- Pins
azure-ai-mlto1.36.0.
| File | Description |
|---|---|
src/machinelearningservices/azext_mlv2/manual/requirements.txt |
Updates the Azure ML SDK dependency. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Member
|
/azp run |
|
Azure Pipelines: Successfully started running 2 pipeline(s). |
Collaborator
|
Please fix CI issues |
Author
|
SDK / CLI team will do this at the time of release Benno Evers (@lava) Kumar Repala |
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.
Background and defect
The v2 az ml extension pins azure-ai-ml==1.35.1, which deserializes FabricSpark compute as unsupported. Its existing compute attach (YAML), detach, show, and list handlers already delegate to the SDK, so no new CLI handlers are required.
Change and compatibility
Pin azure-ai-ml==1.36.0, the version currently under development in the SDK repository. That SDK adds FabricSpark ARM models and entity conversion for the existing CLI commands. The change is limited to one dependency declaration and does not change handlers or any other compute behavior. Do not ship until this SDK version has been released with the FabricSpark changes.
Dependencies and merge order
Blocked on Azure/azure-sdk-for-python#49501 merging AND an azure-ai-ml 1.36.0 package containing that commit being published. If the SDK ships under another version, update this pin and revalidate before merge. SDK release first, CLI extension second.
Validation
SDK compute tests: 42 passed, 1 skipped. CLI CI fails during installation because azure-ai-ml==1.36.0 is not published; lint, integration, and version checks are blocked by that pin. This PR is available for review but must not merge or ship until the published SDK includes FabricSpark. Update the pin if its release version changes, then rerun CLI checks. No live detach was attempted.