### Packages impacted by this PR
- @azure/dev-tool
- @azure/abort-controller
- @azure/core-amqp
- @azure/core-auth
- @azure/core-client
- @azure-rest/core-client
- @azure/core-http-compat
- @azure/core-lro
- @azure/core-paging
- @azure/core-rest-pipeline
- @azure/core-tracing
- @azure/core-util
- @azure/core-xml
- @azure/logger
- @typespec/ts-http-runtime
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Adds snippets extraction to core.
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
### Provide a list of related PRs _(if any)_
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [ ] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
This PR creates a merged api.json file from individual api.json files of
subpath exports. The `ApiModel` type from api-extractor-model already
allows multiple `EntryPoint` but so far only one is added.
With this new file, we can also attach more information to the
`metadata` properties. Even though they are not loaded by `ApiModel`, we
could still read that information from the file directly. This saves us
from having to upload multiple files to ApiView.
### Describe the problem that is addressed by this PR
The current overrides for the browser specific files only replace them
if they are under "src" directory. This PR adds the "test" directory for
test coverage
### Packages impacted by this PR
- @azure/dev-tool
### Issues associated with this PR
### Describe the problem that is addressed by this PR
This PR implements a new dev-tool command: `dev-tool run
update-snippets`.
This command looks for code fences in markdown files and JSDoc comments,
and updates them with the contents of test methods in a file named
`snippets.spec.ts`.
For example, the following fence indicates that the contents of a test
named "new_configurationclient" should be used:
````
```js snippet:new_configurationclient
```
````
After running `dev-tool run update-snippets`, the contents of the
snippet will be populated:
````
```js snippet:new_configurationclient
import { ConfigurationClient } from "@azure/template";
import { DefaultAzureCredential } from "@azure/identity";
const client = new ConfigurationClient(
"<app configuration endpoint>",
new DefaultAzureCredential()
);
```
````
To accomplish this, the command uses the TypeScript compiler API to
extract and transpile snippets from `snippets.spec.ts`. Snippets are the
contents of calls to the `it` function. If syntax with the shape
`it(<literal string>, <function with block>)` appears in
`snippets.spec.ts`, it will be considered a snippet that is valid for
injection.
("Function with block" means either a `function () { ... }` expression
or an arrow function with a block on the arrow side (`() => { ... }`).
An arrow function that has an expression on the right hand side (`() =>
(...)`) will not be recognized.)
For example:
```ts
it("new_configurationclient", function () {
// @ts-ignore
const client = new ConfigurationClient(
process.env.ENDPOINT ?? "<app configuration endpoint>",
new DefaultAzureCredential()
);
});
```
The transpiler automatically "cleans" and validates the snippet using
similar techniques as the sample transpiler. As a result, it enforces
the same syntactic rules that the sample transpiler does. In addition to
those, it removes references to `process.env` (if an alternative is
specified), removes compiler pragmas like `// @ts-ignore`, and
automatically inserts imports for symbols that the snippet uses. So in
the above snippet, imports for `ConfigurationClient` and
`DefaultAzureCredential` are required, automatically detected, and
injected into the resulting snippet.
Snippets without `snippet:${name}` tags are _errors_ when using this
command, so a package must be fully migrated to use it.
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
### Provide a list of related PRs _(if any)_
- #24536
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [ ] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
***NO_CI***
- replace version to "~5.6.2"
- rush update
- add `"skipLibCheck": true` for several packages that are affected by https://github.com/vitest-dev/vitest/issues/4688
- [formrecognizer] help TypeScript to understand with more explicit type
- [schema-registry-{avro,json}] skip lib check due to lru-cache issue with the Iterator TReturn change
https://github.com/isaacs/node-lru-cache/issues/348
### Packages impacted by this PR
- @azure/notification-hubs
### Issues associated with this PR
- #30140
### Describe the problem that is addressed by this PR
Separates the broadcast send and broadcast scheduled send into their own
methods instead of having in the base `sendNotification` and
`scheduleNotification` respectively. Creates two methods of
`sendBroadcastNotification` and `scheduleBroadcastNotification` for each
scenario.
cc @gunzip
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
This allows us to keep required fields for either devices or tag based
expressions for mainline sends and tag based for scheduled sends in the
main methods and only separate the broadcast parts which are less used.
### Are there test cases added in this PR? _(If not, why?)_
### Provide a list of related PRs _(if any)_
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [x] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [x] Added a changelog (if necessary)
### Packages impacted by this PR
- @azure/web-pubsub-client-protobuf
### Issues associated with this PR
Fixes build issues associated with #30988
### Describe the problem that is addressed by this PR
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
### Provide a list of related PRs _(if any)_
- #30988
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [ ] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
### Packages impacted by this PR
@azure/monitor-opentelemetry
@azure/monitor-opentelemetry-exporter
@azure/monitor-query
@azure/opentelemetry-instrumentation-azure-sdk
Updates OpenTelemetry dependencies.
### Checklists
- [x] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [x] Added a changelog (if necessary)
There's some change in `typescript-eslint` that breaks some eslint test
cases.
Previously when running tests, in a rule's `create()` method, we get a
relative
path for `context.filename`, and when we pass a setting of `{ main:
"src/test.ts" }` in rule tester option, the two were considered the same
file,
therefore the following condition check failed, and we continue to
report error
for default exports.
6dd8b582e2/common/tools/eslint-plugin-azure-sdk/src/rules/ts-modules-only-named.ts (L31)
After the upgrade, `context.filename` now contains the full path, the
file
`src/test.ts` in our test fixture has a full path of
`/.../common/tools/eslint-plugin-azure-sdk/tests/fixture/src/test.ts`.
It is not
considered the same file as the passed settings implies
`/.../common/tools/eslint-plugin-azure-sdk/src/test.ts` when we run the
tests.
So we return earlier instead of going to check for default exports.
This is not an issue in real scenario where we have settings of `{ main:
"src/index.ts" }`, which would match the full path of the file we are
linting
when we run `eslint` from a package directory.
This PR fixes the test by passing `tests/fixture/src/test.ts` in the
settings so
that it matches the full path of `context.filename` we get in
`create()`.
- [eslint-plugin] github-source-headers rule should use "MIT License".
This change updates our linter rule and the whole repository to have consistent
license header.
***NO_CI***
- remove "All rights reserved." from header
- "MIT license" => "MIT License"
In our current setup, tshy won't build test and samples-dev folder even
they are
included in tsconfig.json. This PR adds a command that does the
type-checking
for all files included in tsconfig.json, and allow additional files to
be passed
in as well.
to be consistent with `eslint` version.
Also removed the eslint plugin helper. It was added to help
vscode-eslint
extension to resolve plugin packages. With flat config it is no longer
needed.
- adjust options passed `RuleTester` constructor
- remove `recommended` property that no longer exists
- use `output` of array to indicate multi-pass fixes with overlapping
range
- temporarily disable two test cases of ts-modules-only-named suite.
***NO_CI***
- bump typescript-eslint dependencies version to ~8.2.0
- [eslint-plugin] suppress new linting errors appearing with v8
- [eslint-plugin] react to removed typescript-eslint property
related PR https://github.com/typescript-eslint/typescript-eslint/pull/9025
- [eslint-plugin] turn off @typescript-eslint/no-unused-expressions
as no-unused-expressions is already reported by eslint
- [dev-tool] fix new linting errors
- Remove @typescript-eslint/ban-types that no longer exists
and replace with more specific rules wherever applicable.
- [cosmosdb] combine the test eslint config with the main one
- delete catch expression when caught error is not used
- fix or suppress linting errors in code files
### Packages impacted by this PR
@azure/keyvault-certificates
### Issues associated with this PR
N/A
### Describe the problem that is addressed by this PR
Migrates keyvault-certificates to ESM and tshy
### Packages impacted by this PR
@azure/microsoft-playwright-testing
@azure/create-microsoft-playwright-testing
### Issues associated with this PR
### Describe the problem that is addressed by this PR
- Onboard 2 packages
- @azure/microsoft-playwright-testing: Client library used to integrate
Playwright OSS with Microsoft Playwright Testing service
- @azure/create-microsoft-playwright-testing: Utility library to setup
@azure/microsoft-playwright-testing
#### What does the package do
- Playwright OSS client connects to the service-hosted browsers using
the API provided by Playwright OSS. The package provides an abstraction
over this interaction
- Test results are published from the machine running the tests to the
service.
To integrate the service with a Playwright project, users will need to
install a package along with Playwright OSS package. The package is
tightly coupled with Playwright OSS package and also is responsible for
entra id authentication.
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
Yes
### Provide a list of related PRs _(if any)_
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [x] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [x] Added a changelog (if necessary)
---------
Co-authored-by: Vansh Vardhan Singh <vanshvsingh@gmail.com>
Add a configuration to turn off all `eslint-plugin-n` rules for browser
code files.
Also remove the redundant `plugins` block in `nCustomization` because
the
plugin's "flat/recommended" config already does that
e5e758ea0c/lib/index.js (L87)
-------
### Packages impacted by this PR
eslint-plugin-azure-sdk
- Regeneration done
- Tests in sync with latest src
- Live tests ✅
- Migrated to ESM and vitest
- Added new tests for the new features
- Added custom code to support
- the "completed" poller status for batch analysis
`/documentModels/{modelId}:analyzeBatch`
- getting operation id from the poller
- and the new `/documentModels/{modelId}/analyzeResults/{resultId}/pdf`
and
`/documentModels/{modelId}/analyzeResults/{resultId}/figures/{figureId}`
methods
### Packages impacted by this PR
@azure/keyvault-common
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Migrates keyvault-common to ESM and tshy
### Packages impacted by this PR
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Add live test pipeline for OpenAI service
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
### Provide a list of related PRs _(if any)_
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [ ] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
---------
Co-authored-by: Deyaaeldeen Almahallawi <dealmaha@microsoft.com>
- add a config in eslint-plugin-azure-sdk for linting with type
information
- remove .eslint* and replace with eslint.config.mjs
- remove --ext from linting NPM scripts
- fix linting error: URL is now available in global scope on our
supported platforms.
***NO_CI***
- add one flat config file for perf tests
- update NPM scripts of these packages to use that flat config for perf tests
As eslint v8 still not switched to flat config by default, this change
temporarily uses `cross-env` to set `ESLINT_USE_FLAT_CONFIG=true`
Once we moved to eslint v9 the env var can be removed.
### Packages impacted by this PR
@azure/keyvault-admin
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Migrates keyvault-admin to ESM and tshy
and replacing them with eslint.config.mjs so that both command line
eslint and
the vscode eslint extension can use the same config.
- since vite-plugin-browser-test-map doesn't depend on
eslint-plugin-azure-sdk, add linter dev dependencies and a flat config
to it.
- add an internal flat config to our eslint plugin. use it in added flat
config for test utility packages
### Packages impacted by this PR
- @azure-tools/test-utils-vitest
### Issues associated with this PR
- https://github.com/Azure/azure-sdk-for-js/issues/29287
### Describe the problem that is addressed by this PR
Adding in the tracing support and moving the matrix to a new module
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
### Provide a list of related PRs _(if any)_
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [ ] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
---------
Co-authored-by: Jeremy Meng <jeremy.ymeng@gmail.com>
Co-authored-by: Deyaaeldeen Almahallawi <dealmaha@microsoft.com>
### Packages impacted by this PR
@azure-rest/batch
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Add @azure-rest/batch package
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
### Provide a list of related PRs _(if any)_
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [x] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
---------
Co-authored-by: NickKouds <nickouds@hotmail.com>
### Packages impacted by this PR
test-credential
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Update the `createTestCredential` to use Azure Pipeline Credential when
in the Dev Ops env
### Packages impacted by this PR
- @azure/core-amqp
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Removes the polyfills for vite and instead injects the given polyfills
for process and Buffer.
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
### Provide a list of related PRs _(if any)_
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [ ] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
### Packages impacted by this PR
@azure/core-sse
### Issues associated with this PR
https://github.com/Azure/azure-sdk-for-js/issues/30414
### Describe the problem that is addressed by this PR
In NodeJS, when the response stream is exhausted and the server closes
the connection, the underlying socket gets set to null. This is
problematic because core-sse is misled by the type of
`http.IncomingMessage.socket` that stipulates the socket is always a
valid object. This PR checks first if the socket is defined before it
closes it.
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
N/A
### Are there test cases added in this PR? _(If not, why?)_
Yes!
### Provide a list of related PRs _(if any)_
N/A
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [x] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [x] Added a changelog (if necessary)
so that VS Code prettier extension can import it via the "prettier" key
in most of our packages' package.json:
```
"prettier": "@azure/eslint-plugin-azure-sdk/prettier.json",
```
### Packages impacted by this PR
eslint-plugin-azure-sdk
This allows us to remove usage of the outdated and now archived
`eslint-plugin-node`. This PR
- adds `eslint-plugin-n` and its customization into our `eslint-plugin-azure-sdk`
- updates monitor-opentelemetry* packages to remove dev dependency on the old plugin
### Packages impacted by this PR
- eslint-plugin-azure-sdk
### Packages impacted by this PR
@Azure/communication-chat
### Describe the problem that is addressed by this PR
- Update the dependency @azure/communication-signaling package version
to fix the regressions in real time notification support in React
Native.
-
- Update the dependency @azure/core-rest-pipeline package version to fix
the regressions in client response support in React Native.
### Checklists
- [x] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [x] Added a changelog (if necessary)
### Packages impacted by this PR
@azure/eventhubs-checkpointstore-blob
### Issues associated with this PR
N/A
### Describe the problem that is addressed by this PR
- migrates to use TSHY and vitest
- uses storage endpoint instead of storage connection string in the
tests
- enables browser testing
- updates test-resources.json accordingly
- fixes a behavior where an error is being wrapped in another
Live tests run:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4018408&view=results
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
N/A
### Are there test cases added in this PR? _(If not, why?)_
N/A
### Provide a list of related PRs _(if any)_
N/A
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [x] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
### Packages impacted by this PR
@azure/event-hubs
### Issues associated with this PR
N/A
### Describe the problem that is addressed by this PR
This PR does the following:
- migrates Event Hubs client library to the new world of using TSHY for
building the library and using vitest as the test runner
- consolidates client building in a single module and uses fully
qualified name spaces and token credentials to build clients instead of
using connection strings
- runs mock-hub once instead of in every test module
- disables min/max testing and samples testing because they're not
playing well with TSHY and vitest at the moment. I'll open an issue to
track turning them back on once the testing pipelines have been
upgraded.
Live Tests are passing:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4000037&view=results
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
N/A
### Are there test cases added in this PR? _(If not, why?)_
N/A
### Provide a list of related PRs _(if any)_
N/A
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [x] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
### Packages impacted by this PR
### Issues associated with this PR
### Describe the problem that is addressed by this PR
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
### Provide a list of related PRs _(if any)_
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [ ] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
### Packages impacted by this PR
This PR includes the JavaScript/Typescript SDK for health deid service.
It includes:
- tests
- samples
- Readme
### Issues associated with this PR
### Describe the problem that is addressed by this PR
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
### Provide a list of related PRs _(if any)_
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [ ] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
---------
Co-authored-by: Harsha Nalluru <sanallur@microsoft.com>
There's some behavior change that adds parentheses for nullish coalescing in
ternary. So we will need to re-format our code base.
- remove prettier from packages that don't need them since we run the vendored
version via dev-tool
It helps old JS runtimes that only support ES 5 but we moved to ES 6
long time ago
and now moved to ES2017. Most of our packages don't have this option.
This PR
removes its usage.
### Packages impacted by this PR
@azure/-tools/vite-plugin-browser-test-map
### Issues associated with this PR
N/A
### Describe the problem that is addressed by this PR
The type declaration file wasn't set in package.json and the return type
of the plugin function was too permissive causing type errors when
imported.
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
N/A
### Are there test cases added in this PR? _(If not, why?)_
N/A
### Provide a list of related PRs _(if any)_
N/A
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [x] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
### Packages impacted by this PR
@azure/monitor-opentelemetry
### Describe the problem that is addressed by this PR
Updates the @microsoft/applicationinsights-web-snippet package to the
latest version.
### Checklists
- [x] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [x] Added a changelog (if necessary)
### Packages impacted by this PR
1. @azure/eventgrid-namespaces
2. @azure/eventgrid
### Issues associated with this PR
https://github.com/Azure/azure-sdk-for-js/issues/29699
### Describe the problem that is addressed by this PR
This PR has been created to move the eventgrid packages away from Local
Authentication. The migration guide has been used for reference.
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
No special design consideration.
### Are there test cases added in this PR? _(If not, why?)_
NA. Existing test cases are sufficient.
### Provide a list of related PRs _(if any)_
1. https://github.com/Azure/azure-sdk-for-js/issues/29699
2. https://github.com/Azure/azure-sdk-for-js/pull/30209
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [X] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
Update tsp-location.yaml to point to a commit from main in the spec repo
and regenerate. The previous commit hash was from a branch never merged,
blocking the attempt to release the sdk
After regenerating from latest tsp main, those were the changes
introduced:
* EnvionmentType name was updated to readonly (later fix added on the
typespec)
* PollingHelper and lro packages got updated (updated by code gen). Live
test for the LRO operations was executed and no issue was detected.
Previous PR for current sdk:
https://github.com/Azure/azure-sdk-for-js/pull/29512
APIView: [@azure-rest/developer-devcenter -
apiview.dev](https://apiview.dev/Assemblies/Review/e17096012eb7466a8aab7c74742c6bff?revisionId=b4d2f5f84d98499dacfcc5e7cdd15d52)
---------
Co-authored-by: Mary Gao <yanmeigao1210@gmail.com>
Previously it was checking the existence of .tshy directory. Now that we
removed
all .tshy the code is broken. This PR updates to check the package.json
instead.
### Packages impacted by this PR
### Issues associated with this PR
### Describe the problem that is addressed by this PR
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
### Provide a list of related PRs _(if any)_
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [ ] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
### Packages impacted by this PR
@azure/ai-inference
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Initial release of @azure/ai-inference SDK
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
### Provide a list of related PRs _(if any)_
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [ ] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
### Packages impacted by this PR
- @azure/dev-tool
### Issues associated with this PR
- #30160
### Describe the problem that is addressed by this PR
Updates to latest ts-morph package.
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
### Provide a list of related PRs _(if any)_
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [ ] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
### Packages impacted by this PR
- @azure/dev-tool
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Adds the following:
- Global regex replace for context replacements
- Changes sinon spy to `vi.spyOn`
- Adds node specifiers to node imports
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
### Provide a list of related PRs _(if any)_
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [ ] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
### Packages impacted by this PR
- @azure/dev-tool
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Fixed the `beforeEach` statements to get rid of the Mocha `Context` and
replace with `vitest` context and fixes the test-recorder creation.
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
### Provide a list of related PRs _(if any)_
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [ ] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
to fix broken nightly pipelines where we update `@azure` package
versions to
nightly versions and dependency versions to a range for their nightly
versions.
Versino `^3.0.0` would not get updated because of the following chech in
`set-dev.js` then `rush install` would fail to find matching one and
report error.
9488fe4bd7/eng/tools/versioning/set-dev.js (L80)
### Packages impacted by this PR
@azure-tools/test-credentials
### Issues associated with this PR
### Describe the problem that is addressed by this PR
- Exclude Managed Identity from DAC so that we can run live test
pipeline successfully. The 4 credentials that we try is: Powershell,
Cli, Developer Cli, Environment Credential in listed order. See [the migration
guide](https://dev.azure.com/azure-sdk/internal/_wiki/wikis/internal.wiki/1080/Secret-auth-migration)
- Increase the default timeout for vitest to our default timeout (18000
ms)
Co-authored-by: Harsha Nalluru <sanallur@microsoft.com>
### Packages impacted by this PR
- @azure/dev-tool
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Adds updates for the following:
- Changes assert to only use `vitest` for now and not sure the
`@azure-tools/test-utils`
- Any utility in the `/test` folders will be updated to use `vitest` for
assertions
- Add `beforeEach`, `afterEach`, `vi` and `expect` to any test class
using `sinon` for easy replacement
- Fix pathing issue so that `import { foo } from "..";` is translated to
`import { foo } from "../index.js";`
- Removes `source-map-support` as we're not using Karma.
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
### Provide a list of related PRs _(if any)_
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [ ] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
Matthew Podwysocki
ZiWei Chen
Daniel Getu
Jeremy Meng
Minh-Anh Phan
Azure SDK Bot
Jackson Weber
Jeremy Meng
Maor Leger
Siddharth Singha Roy
Harsha Nalluru
Deyaaeldeen Almahallawi
Haopeng Wang
EmmaZhu-MSFT
luc
danielszaniszlo
Hector Hernandez
Sarangan Rajamanickam
Driele Neves Ribeiro
hamshavathimunibyraiah
Glenn Harper
Jana R