### Packages impacted by this PR
- `@azure/keyvault-common`
### Describe the problem that is addressed by this PR
Caught this while doing pre-release checks. `@azure/core-util@^1.10.1`
has not released yet
### Packages impacted by this PR
- @azure/maps-common
### Issues associated with this PR
- #31338
### 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/keyvault-common`
- `@azure/keyvault-admin`
- `@azure/keyvault-certificates`
- `@azure/keyvault-keys`
- `@azure/keyvault-secrets`
Preparing for release of CAE support + ESM migration.
### 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/notification-hubs
### Issues associated with this PR
- #30439
- #30697
### Describe the problem that is addressed by this PR
Releasing fixes for `@azure/notification-hubs` plus new features.
### 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
Resolves#31325
### Describe the problem that is addressed by this PR
In order to automate as much as possible, we're introducing a set of
codemods to dev-tool's migrate-package command which can be added to by anyone.
These codemods will run in sequence and commit their work in stages for ease
of reviewing
### Packages impacted by this PR
### Issues associated with this PR
Resolves#30578
### Describe the problem that is addressed by this PR
While simple settings like `test-timeout` and `hook-timeout` are often
defined in package.json scripts, there are
other settings that are specified in the vitest.config.ts of the target
package.
Our existing setup uses the default vitest template which does not work
for libraries that use customized config.
This PR improves that experience by creating a 3-way-merge of:
1. The base config
2. The template config (which specifies the test patterns)
3. The package's config
Only done for node right now. If you need it for browser, you now have a
path forward
### 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?
There are some gotchas here:
1. testTimeout is defined in package.json which takes precedence over
any config files I believe - it may be surprising that your testTimeout
does not take (note that this is somewhat the case today)
2. The package's config adds files under `test/**/*.spec.ts` to the
include pattern. This is fine, because the min/max tests are placed
under `test/public` so that pattern will not match anything
I really want to clean up min/max - but this is not the time
### Packages impacted by this PR
@azure/eventgrid
### Issues associated with this PR
NA
### Describe the problem that is addressed by this PR
This PR consists of the following changes:
- A new property `onBehalfOfCallee` is added to the
`AcsIncomingCallEventData` interface.
- The property `serializedName` has been removed from
`MediaJobOutputProgressEventData` & `MediaJobScheduledEventData` models.
### 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?
There are no specific/complex design scenarios for this task. It is a
straightforward regenerate and some standard changes to the custom layer
of the code.
### Are there test cases added in this PR? _(If not, why?)_
No. This item is standard and we need not add test cases for every new
events. The existing cases would be sufficient.
### Provide a list of related PRs _(if any)_
- https://github.com/Azure/azure-sdk-for-js/pull/28513 (This is the PR
that adds similar events to the SDK in the 5.2.0 release)
- https://github.com/Azure/azure-sdk-for-js/pull/28891 (This is the PR
that adds similar events to the SDK in the 5.3.0 release)
- https://github.com/Azure/azure-sdk-for-js/pull/29035 (This is the PR
that adds similar events to the SDK in the 5.4.0 release)
- https://github.com/Azure/azure-sdk-for-js/pull/29872 (This is the PR
that adds similar events to the SDK in the 5.5.0 release)
- https://github.com/Azure/azure-sdk-for-js/pull/30811 (This is the PR
that adds similar events to the SDK in the 5.6.0 release)
- https://github.com/Azure/azure-sdk-for-js/pull/31186 (This is the PR
that adds similar events to the SDK in the 5.7.0 release)
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
```autorest --typescript swagger\README.md```
### 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
monitor-opentelemetry
### Describe the problem that is addressed by this PR
This PR adds support for document filtering in live metrics.
### Are there test cases added in this PR? _(If not, why?)_
Modifications were made to existing unit tests to test documents
functionality, as much of the new code added uses existing filtering
functionality. Also, many cases for documents were manually tested E2E,
such as the single/multi session cases for applying filters to documents
and metrics & confirming that SDK conforms to any configuration sent to
it by the service.
### 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)
* Add CompatibleConvertFrom-Yaml to common Package-Helpers
* Add CI artifact parsing to Save-Package-Properties, now each individual packageinfo.json file contains the relevant ci artifact lines for the package. This short circuits needing to re-parse this information in common checks.
---------
Co-authored-by: Scott Beddall <scbedd@microsoft.com>
- apply the result of `dev-tool admin migrate-package --package-name
@azure/service-bus`
without removing chai usages in tests because it is causing crash when
running
the command
- work around compilation error from "long" with `"skipLibCheck": true`
- fix assert/chai/etc.
- replace sinon usage with vi
### Packages impacted by this PR
- `@azure-rest/core-client`
### Describe the problem that is addressed by this PR
Preparing for out of band patch release to fix regression (#31349).
### Packages impacted by this PR
@azure/monitor-opentelemetry-exporter
### Describe the problem that is addressed by this PR
We should follow the spec regarding which status codes should cause
statsbeat to shutdown and fail silently.
We should also align with other languages on the environment variable
used to disable statsbeat.
### 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-rest/core-client`
### Issues associated with this PR
- Fix https://github.com/Azure/azure-sdk-for-js/issues/31349
### Describe the problem that is addressed by this PR
We generate RLCs that allow for path parameters to be `number`. The
change for `allowReserved` assumed that path parameters could only be
`string`, causing number parameters to not be serialized properly. This
PR fixes that assumption.
### 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?)_
Added a test to check for a number path parameter
### Provide a list of related PRs _(if any)_
- #31058
### Packages impacted by this PR
`
@azure/microsoft-playwright-testing`
### Issues associated with this PR
Made browser name optional.
### 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/monitor-opentelemetry-exporter
### Describe the problem that is addressed by this PR
We should collect non-essential statsbeat about disk retry.
### Are there test cases added in this PR? _(If not, why?)_
Yes
### 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/keyvault-keys
### Issues associated with this PR
Resolves#30822
### Describe the problem that is addressed by this PR
Migrate keyvault-keys to ESM and tshy
### Packages impacted by this PR
@azure/identity
### Issues associated with this PR
Resolves#31307
### Describe the problem that is addressed by this PR
It is not clear from our documentation that @azure/identity is optimized
for the "pass a credential to another client library" use-case and that
refreshing / caching / etc. are implementation details without proper API support and
documentation.
This PR attempts to provide additional information regarding when to use
something like MSAL directly.
---------
Co-authored-by: Scott Addie <10702007+scottaddie@users.noreply.github.com>
### Packages impacted by this PR
@azure/event-hubs
### Issues associated with this PR
https://github.com/Azure/azure-sdk-for-js/issues/31067
### Describe the problem that is addressed by this PR
This PR adds runtime validation to the input message structure. This is
needed so that strict receivers that follow the AMQP spec don't reject
non-compliant messages.
### 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)_
https://github.com/Azure/azure-sdk-for-js/pull/31330
### 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/monitor-opentelemetry
### 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/cosmos
### Issues associated with this PR
#31119
### Describe the problem that is addressed by this PR
1. "http:" protocol now works properly
2. Unhandled errors in tests now properly include stack trace in STDERR
### 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?
We could possibly have done a further bifurcation of the logic for http:
vs https:. I chose this design because it was a minimal change and
maintains the original intent.
### Are there test cases added in this PR? _(If not, why?)_
No. There's not currently a good means to test http: against Cosmos DB,
but that's a WIP.
### Provide a list of related PRs _(if any)_
N/A
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
N/A
### 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)_ - N/A
- [ ] Added a changelog (if necessary) - N/A
---------
Co-authored-by: Chris Anderson <andersonc@microsoft.com>
Praven Kuttappan
Deyaaeldeen Almahallawi
Timo van Veenendaal
Matthew Podwysocki
Azure SDK Bot
Scott Addie
EmmaZhu-MSFT
ZiWei Chen
Wes Haggard
Minh-Anh Phan
Jeff Fisher
Jeremy Meng
Maor Leger
Sarangan Rajamanickam
Harsimar Kaur
Jackson Weber
Kashish Gupta
Christopher Anderson