-
Notifications
You must be signed in to change notification settings - Fork 183
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
Correct the name of JS package folder #7569
Conversation
The following pipelines have been queued for testing: |
The following pipelines have been queued for testing: |
The following pipelines have been queued for testing: |
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.
Let's switch to using the package info properties instead of duplicating logic.
@weshaggard , switched to rely on the package info. This is the test run result. |
The following pipelines have been queued for testing: |
Sync eng/common directory with azure-sdk-tools for PR Azure/azure-sdk-tools#7569 See [eng/common workflow](https://github.com/Azure/azure-sdk-tools/blob/main/eng/common/README.md#workflow) --------- Co-authored-by: Ray Chen <raychen@microsoft.com>
This PR is to add back the spec location validation back to the release pipeline. Here is the original PR which was reverted by an issue of the JS package path. #28303 Here is the PR of the fix of common script that has been merged: Azure/azure-sdk-tools#7569 This is the [test run result](https://dev.azure.com/azure-sdk/internal/_build/results?buildId=3433518&view=logs&j=7bb69cc7-6f52-585e-8b13-5bae7c4a9fa4&t=7abbbe6b-d005-5c95-feb6-99ffe4e699e1) in JS repo. @weshaggard @jeremymeng , please review.
There are two cases for the naming of JS package folder:
The changes include:
The pipeline test run of JS template package release with same script change looks good.