Test: SDK customization workflow for spec PR #41879#5
Closed
samvaity wants to merge 1 commit into
Closed
Conversation
TypeSpec version gating restored for Azure Machine Learning, causing SDK generation changes and potential customization drift in Java SDK. Ref: Azure/azure-rest-api-specs#41879 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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
1 participant
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.
Test PR for skill validation
This PR simulates the scenario from Azure/azure-rest-api-specs#41879 where TypeSpec version gating changes cause SDK build failures in the Java SDK.
Context
What to test
Comment @copilot fix the build errors caused by the spec changes\ to see if the \generate-sdk-locally\ skill is triggered and invokes \�zure-sdk-mcp:azsdk_customized_code_update.
Skill under test