Skip to content

Sync eng/common directory with azure-sdk-tools for PR 13693 #9591

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.

Sign up for GitHub

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

Merged
azure-sdk merged 3 commits into from
Jan 30, 2026
+11 −1
Merged

Sync eng/common directory with azure-sdk-tools for PR 13693 #9591

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
972507e
Add instruction to normalize package name
smw-ms Jan 23, 2026
0a9dda9
Add javascript validation
smw-ms Jan 29, 2026
72f3bbc
Add examples
smw-ms Jan 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion eng/common/instructions/azsdk-tools/sdk-details-in-release-plan.instructions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ description: 'Identify languages configured in the TypeSpec project and add it t
- For Java and Python, use `emitter-output-dir` for package name if it exists. Otherwise use `package-dir` to get the package name as fallback approach.
- For .NET, use namespace property to get package name.
- For JavaScript, use `packagedetails:name` property to get package name.
- For Go, use module name and remove `github.com/Azure/azure-sdk-for-go/` to get package name
- For Go, use module name and remove `github.com/Azure/azure-sdk-for-go/` to get package name.
3. Map the language name in emitter to one of the following in Pascal case(except .NET):
- .NET
- Java
Expand Down Expand Up @@ -36,6 +36,16 @@ description: 'Identify languages configured in the TypeSpec project and add it t
**Success Criteria**: Release plan exists or user informed to create one.

# Step 3: Update Release Plan with SDK Information
> **(MANDATORY - DO NOT SKIP) ALWAYS validate all package names against the format rules AND the examples table before calling any update tool, even if the user provides SDK details directly. Auto-correct and inform the user of invalid package names.**
> - **JavaScript**: Must start with `@azure/`
> - **Go**: Must start with `sdk/`
>
> **Valid package name examples (compare against these to catch invalid formats):**
> | Language | Valid | Invalid |
> |----------|-------|---------|
> | JavaScript | `@azure/arm-compute` | `arm-compute`, `azure/arm-compute`,`@azure-arm-compute` |
> | Go (management plane) | `sdk/resourcemanager/compute/armcompute` | `sdk/armcompute`, `/sdk/compute`, `github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/compute` |

**Goal**: Update the release plan with the languages and package names identified in Step 1.
1. Use `azsdk_update_sdk_details_in_release_plan` to update the release plan work item with the JSON object created in Step 1.
2. Confirm successful update of the release plan with the SDK information and summary of languages and package names.
Expand Down
Loading