After we bump the version of template package, rush/pnpm now pulls
@azure/template@1.0.11 from npm. That is a very old version that depends
on
core-http@1.2.6 whose dependency `xml2js` caused a security alert.
This PR updates the perf-template package to depend on the version of
`@azure/template` in the repo, then `rush update --full` gets rid of
those
outdated dependencies.
### Packages impacted by this PR
- @azure-rest/ai-content-safety
### Issues associated with this PR
- https://github.com/Azure/azure-sdk-for-js/issues/31338
### Describe the problem that is addressed by this PR
Migrates the `@azure-rest/ai-content-safety` package to ESM/vitest using
code automation.
### 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`
### Describe the problem that is addressed by this PR
This PR introduces `dev-tool check`, a command which can be used to run
pass/fail checks on SDK packages. It also introduces a few checks to get
us started.
### What is a check?
A check consists of a combination of metadata (name, description,
"hasFix", tags, severity) and a _check function_. When a check is run,
the check function is called with arguments providing information about
the package being checked. If the check function runs to completion, the
check passes; otherwise if an error is thrown then the check fails. A
helper function, `check`, is provided which throws an error if a boolean
condition is not met.
Checks are defined in files under the `src/checks` directory in
dev-tool. The check runner automatically discovers files in the
directory. Each export from a file in the `src/checks` directory is
expected to be a check. When running checks, the output is grouped by
file, and then the name of the check. The name of the check, unless
overridden in the metadata, is the name it is exported under.
### Check metadata
Checks can have this metadata, all optional:
- `name`: the name of the check; if unspecified the name will be
inferred from the name of the export
- `description`: an extended description of the check which is shown if
the check fails
- `hasFix`: see "Fix mode", below; defaults to `false`, but if set to
`true` indicates to the runner that the check is able to attempt to fix
itself
- `tags`: a list of "tags" which can be used to specify in what contexts
the check should be run. If none are specified, the check will be run in
all contexts. See "Tags" below.
- `severity`: either "warning" or "error". Defaults to "error". If the
severity is "error", the check failing will cause a failure exit code,
but if the severity is only "warning" then a message will be output if
the check fails but it will not cause a failure exit code.
- `enable`: an optional additional function alongside the main check
function. The check will only be run if the `enable` function returns
`true` for the given project. This is useful for making checks that only
run on ESM packages, for example.
### Fix mode and `hasFix`
A check can specify `hasFix: true` in its metadata to signal that the
check is able to fix itself. If a check is fixable, running `dev-tool
check` with `--fix` will pass `fix: true` to the check function. If this
is passed, the check function is responsible for writing changes that
fix the check to the filesystem.
### Tags
Not all checks need to be run all the time. For example, you might not
want to run lengthy release checks like the package installability check
locally every time you run `dev-tool check`. For this purpose, checks
can specify "tags" in their metadata which govern when the check should
be run. The `--tag` option can be passed in to the check command to
specify which tag of check you want to run. By default, `dev-tool check`
will only run checks which do not have a tag.
Currently available tags are:
- `local`: the check is intended to be run locally before you push your
work
- `ci`: the check is intended to be run as part of the CI pipeline
(e.g., format)
- `release`: the check is intended to be run as a final step before
releasing the package (e.g., checking if the package is installable)
- if the `tags` field is left empty, the check will run all the time
regardless of the value of the `--tag` argument. This is intended for
quick checks that don't take long to run.
Not sure if the current setup with the tags and its default behavior is
the best, it's just something that felt okay to me when I have been
testing the tool out. Definitely open to ideas for how we could handle
this problem better.
### Building blocks for checks
Many checks follow common patterns so I have written some helper
functions which can be used to create checks more easily. You can see
them in action in the checks I created for this PR. What I have so far
is:
- `scriptCheck`: creates a check which runs the given CLI command
`checkCommand` and passes or fails based on the exit code of the
command. An optional `fixCommand` can also be specified which will be
run in fix mode.
- `packageJsonCheck`: creates a check which can make assertions about
the package.json file. This is intended to replace the package.json
eslint rules we already have. Checks created with `packageJsonCheck` are
passed the serialized package.json file. The check can make assertions
about the serialized file. It can also mutate the serialized object; any
material changes as a result of the mutation will cause the check to
fail. If hasFix is set to true, the mutated package.json will be written
to disk in fix mode.
- `workingTreeUnchangedCheck`: can wrap an existing check or a fix
command. The check or fix command will be run in fix mode always, and
any changes to the working tree as a result of running the check will
cause the check to fail. After the check is run, any working tree
changes will be reverted, unless the check was run in fix mode.
### Checks added in this PR
I created a few checks to get us started
- package.json checks -- porting over most of the package.json rules in
the ESLint plugin
- release checks
- a check that attempts to pack and install the package. This verifies
that all of the dependencies are published to npm
- a check which runs [are the types
wrong](https://github.com/arethetypeswrong/arethetypeswrong.github.io)
on the package to make sure the types are good
- checks which run scripts
- format
- lint
- node tests
- browser tests
### Future work
Some ideas:
- more checks
- running `dev-tool check` in the pipelines
- better reporting and more options (e.g. an option to run a specific
check only)
---------
Co-authored-by: Jeremy Meng <yumeng@microsoft.com>
### Packages impacted by this PR
- @azure-rest/ai-document-translator
### Issues associated with this PR
- https://github.com/Azure/azure-sdk-for-js/issues/31338
### Describe the problem that is addressed by this PR
Migrates the `@azure-rest/ai-document-translator` package to ESM/vitest
using code automation.
### 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-rest/load-testing
### Issues associated with this PR
- https://github.com/Azure/azure-sdk-for-js/issues/31338
### Describe the problem that is addressed by this PR
Migrates @azure-rest/load-testing to ESM/vitest via dev-tool automation.
### 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-rest/purview-sharing
### Issues associated with this PR
- https://github.com/Azure/azure-sdk-for-js/issues/31338
### Describe the problem that is addressed by this PR
Migrates the @azure-rest/purview-sharing package to ESM/vitest via
automation.
### 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-rest/purview-administration
### Issues associated with this PR
- https://github.com/Azure/azure-sdk-for-js/issues/31338
### Describe the problem that is addressed by this PR
Migrates @azure-rest/purview-administration to ESM/vitest via
automation.
### 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-rest/purview-workflow
### Issues associated with this PR
- https://github.com/Azure/azure-sdk-for-js/issues/31338
### Describe the problem that is addressed by this PR
Migrates the @azure-rest/purview-workflow package to ESM/vitest via
automation.
### 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-rest/purview-datamap
### Issues associated with this PR
- https://github.com/Azure/azure-sdk-for-js/issues/31338
### Describe the problem that is addressed by this PR
Migrates the @azure-rest/purview-datamap package to ESM/vitest via
automation. Note there is one skipped test @qiaozha due to a missing
recording.
### 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-rest/purview-catalog
### Issues associated with this PR
- https://github.com/Azure/azure-sdk-for-js/issues/31338
### Describe the problem that is addressed by this PR
Migrates the @azure-rest/purview-catalog package to ESM/vitest via
automation.
### 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-rest/purview-scanning
### Issues associated with this PR
- https://github.com/Azure/azure-sdk-for-js/issues/31338
### Describe the problem that is addressed by this PR
Migrates the @azure-rest/purview-scanning package to ESM/vitest via
automation.
### 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/iot-modelrepository
### Issues associated with this PR
- https://github.com/Azure/azure-sdk-for-js/issues/31338
### Describe the problem that is addressed by this PR
Migrates the @azure/iot-modelrepository package via automation to
ESM/vitest.
### 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-rest/synapse-access-control
### Issues associated with this PR
- https://github.com/Azure/azure-sdk-for-js/issues/31338
### Describe the problem that is addressed by this PR
Using the migration tool, migrates the
@azure-rest/synapse-access-control project to ESM/vitest.
### 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/synapse-access-control
### Issues associated with this PR
- https://github.com/Azure/azure-sdk-for-js/issues/31338
### Describe the problem that is addressed by this PR
Using the migration tool, moves the @azure/synapse-access-control
package to ESM/vitest
### 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/synapse-managed-private-endpoints
### Issues associated with this PR
- https://github.com/Azure/azure-sdk-for-js/issues/31338
### Describe the problem that is addressed by this PR
Migrates using the migration tool for
@azure/synapse-managed-private-endpoints to ESM/vitest
### 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/synapse-monitoring
### Issues associated with this PR
- https://github.com/Azure/azure-sdk-for-js/issues/31338
### Describe the problem that is addressed by this PR
Migrates the auto generated @azure/synapse-monitoring project to
ESM/vitest
### 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/synapse-spark
### Issues associated with this PR
- https://github.com/Azure/azure-sdk-for-js/issues/31338
### Describe the problem that is addressed by this PR
Moves auto-generated @azure/synapse-spark to ESM/vitest.
### 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/synapse-artifacts
### Issues associated with this PR
- https://github.com/Azure/azure-sdk-for-js/issues/31338
### Describe the problem that is addressed by this PR
Migrates using the migration tool for @azure/synapse-artifacts to
ESM/vitest
### 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)
We have a check for when asking for any session, i.e., not providing a
session id), but not receiving a link having a session id. However, the
check is `if (!this._providedSessionId && !receivedSessionId)` which
also evaluates to `true` for session id of empty string, which is valid
session id.
This PR changes it to check for `undefined` so that session id of empty
string doesn't lead to error being thrown.
Behind the scene, TSHY rewrites tsconfig.json to build the source code
of the library but it ignores tests and samples. This PR breaks the
monolith tsconfig.json into three ones, one for building the source, one
for the tests, and one for the samples. It utilizes [Project
References](https://www.typescriptlang.org/docs/handbook/project-references.html)
to create a TS project each. This setup makes sure type errors are
adequately caught in each of those projects.
Additionally, the PR disables rolling up d.ts files and fixes a type
error in tests.
### Packages impacted by this PR
- @azure/web-pubsub
### Issues associated with this PR
- https://github.com/Azure/azure-sdk-for-js/issues/31338
### Describe the problem that is addressed by this PR
Using the migration tool, moves @azure/web-pubsub to ESM/vitest.
### 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>
### 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)
- Add a test util to parse JWT token payload to validate audience
- Add more tests for AAD
- Fix mismatched DTO field when calling generateClientToken
---------
Co-authored-by: tomnguyen <chuongnguyen@microsoft.com>
### Packages impacted by this PR
- @azure/template-dpg
### Issues associated with this PR
- https://github.com/Azure/azure-sdk-for-js/issues/31338
### Describe the problem that is addressed by this PR
Upgrades @azure/template-dpg to ESM/vitest
### 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>
### Packages impacted by this PR
- @azure/identity
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Bumps the `hookTimeout` and `testTimeout` for @azure/identity tests.
### 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/communication-rooms
### Issues associated with this PR
- https://github.com/Azure/azure-sdk-for-js/issues/31338
### Describe the problem that is addressed by this PR
Migrates @azure/communication-rooms using our migration tool to
ESM/vitest
### 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/cosmos
### Describe the problem that is addressed by this PR
In this PR we are adding three optional parameters in the Indexing
Policy in the vector Index to support partitioned DiskANN. The three
optional parameters are:
quantizationByteSize : The number of bytes used in product quantization
of the vectors.This is an optional parameter and applies to index types
DiskANN and quantizedFlat. The allowed range for this parameter is
between 1 and 200.
vectorIndexShardKey : The list of string containing the shard keys used
for partitioning the vector indexes. This is an optional parameter and
applies to index types DiskANN and quantizedFlat.
indexingSearchListSize : The size of the candidate list of approximate
neighbors stored while building the diskANN index as part of the
optimization processes.This is an optional parameter and applies to
index type DiskANN only. The allowed range is between 25 and 500.
The changes have been tested using a Test account, since as of now the
backend changes aren't live yet.
### 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
- [ ] 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: Ujjwal Soni <soniujjwal@microsoft.com>
Co-authored-by: Manik Khandelwal <mkhandelwal@microsoft.com>
### Packages impacted by this PR
- @azure/opentelemetry-instrumentation-azure-sdk
- @azure/monitor-opentelemetry
- @azure/monitor-opentelemetry-exporter
- @azure/monitor-query
### Issues associated with this PR
- #31807
- #31808
- #31809
### 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: Jackson Weber <jacksonweber@microsoft.com>
### Packages impacted by this PR
@azure/cosmos
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Update changeLog for release.
### 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?)_
N/A
### 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)
Jeremy Meng
Matthew Podwysocki
Timo van Veenendaal
Praven Kuttappan
Daniel Getu
KarishmaGhiya
Azure SDK Bot
ZiWei Chen
Deyaaeldeen Almahallawi
EmmaZhu-MSFT
cqnguy23
Manik Khandelwal
Wes Haggard
Aman Rao
Ujjwal Soni