### Packages impacted by this PR
@azure/app-configuration
### Issues associated with this PR
#31010
### Describe the problem that is addressed by this PR
- Move away from nock mocking because of unexpected behavior change from
Node 22.7 and above.
- Update samples to avoid duplicate key error when the samples are run
in parallel
### Packages impacted by this PR
@azure/identity
### Issues associated with this PR
#30557
### Describe the problem that is addressed by this PR
Looks like we missed one place where we need to read the
AZURE_AUTHORITY_HOST env var when porting logic over to msalClient.
This PR addresses the issue and allows for environment variable to be read
when needed.
To have ClientAssertionCredentialOptions implement
ISupportsTokenCachePersistenceOptions. As a consumer of Identity, Azure
PowerShell is dependent on the Azure Identity library for .NET. Now the
client assertion workflow has increasing usage, so the ask should have
higher priority.
Business Impact:
In the client assertion auth flow, Azure PowerShell customers acquire
the access token with the federated token. The access token must be used
by the subsequent Azure PowerShell cmdlets. We depend on Azure.Identity
to save the tokens to the MSAL cache. As the federated token has a short
lifetime, it's impossible to cache the federated token and
reauthenticate every time a cmdlet is run.
### Packages impacted by this PR
@azure/microsoft-playwright-testing
### 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/microsoft-playwright-testing
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Any API failure in post test result API call would terminate the node
process immediately. This PR swallows the exception and allows the
execution to proceed.
### 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/ai-inference
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Add tool sample with streaming chat completion
### 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>
### Packages impacted by this PR
@azure/identity
### Issues associated with this PR
#30187
### Describe the problem that is addressed by this PR
Now that core-util is published with a `calculateRetryDelay` helper, we
can use that instead of duplicating the logic from core-rest-pipeline
### Are there test cases added in this PR? _(If not, why?)_
There's an existing test suite for this policy, and this should be
considered a pure refactor now
### Packages impacted by this PR
@azure/core-rest-pipeline
### Issues associated with this PR
#30187
### Describe the problem that is addressed by this PR
Now that core-util is published with a `calculateRetryDelay` helper, we
can use that instead of duplicating the logic from core-rest-pipeline
### Packages impacted by this PR
@azure-tools/test-utils
### Describe the problem that is addressed by this PR
I noticed that the hotfix changes from 1.x branch were not listed in the
CHANGELOG on main. This PR just ports those over so they are listed in
chronological order
### 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/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/microsoft-playwright-testing`
### Issues associated with this PR
Improved Sas uri expiry logic.
### 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-certificates`
### Issues associated with this PR
- Fix#31012
### Describe the problem that is addressed by this PR
1. Minmax tests are not run in the package directory (they are instead
run in `test/public`). This PR updates the path for some static test
resource files to be relative to the test file itself instead of
relative to the working directory.
2. Stop using instanceof for a couple of tests where we are testing the
type of the error. The name of the error should be enough. I think this
might have been causing failures maybe due to a dual-package hazard kind
of interaction?
### Packages impacted by this PR
`
@azure/microsoft-playwright-testing`
### Issues associated with this PR
Display informational messages to the user in case of errors at the end
of test.
### 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
monitor-opentelemetry
### Issues associated with this PR
https://github.com/Azure/azure-sdk-for-js/issues/30970
### Describe the problem that is addressed by this PR
This PR addresses the issue where the live metrics component of the SDK
was re-emitting old documents at every time interval along with the new
documents.
Testing was manually done by including the app insights sdk in a test
application & checking the documents that appear on the documents pane
on the live metrics page.
### 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)
Chrome-based browsers are more error-tolerant when the XML
namespace ("xmlns:...") was set via attribute, but that doesn't work on
Firefox,
which requires using of `createElementNS()` to create element with XML
namespace.
This PR adds special handling of the "xmlns" attribute.
-------
### Packages impacted by this PR
@azure/core-xml
### Issues associated with this PR
https://github.com/Azure/azure-sdk-for-js/issues/11655https://github.com/Azure/azure-sdk-for-js/issues/30979
### Packages impacted by this PR
- @azure/core-rest-pipeline
### Issues associated with this PR
- #31026
### Describe the problem that is addressed by this PR
Removes excess listeners for streams to ensure that we're not adding
listeners to check for done and then not removing them.
### 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/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/microsoft-playwright-testing
### 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: Vansh Vardhan Singh <vanshsingh@microsoft.com>
### Packages impacted by this PR
@azure/microsoft-playwright-testing
### 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/microsoft-playwright-testing
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Fetching and setting access token was a one time operation in reporting.
Thus, when the token was rotated, it was not picked up by the reporter
worker resulting in expired token calls.
### 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)
Azure SDK Bot
microsoft-github-policy-service[bot]
EmmaZhu-MSFT
KarishmaGhiya
Minh-Anh Phan
sorrego-msft
Maor Leger
Weiyang Ding(MSFT)
Kashish Gupta
Siddharth Singha Roy
Glenn Harper
Wes Haggard
Matthew Podwysocki
Harsimar Kaur
Ben Broderick Phillips
Timo van Veenendaal
Haopeng Wang
Mary Gao
Hector Hernandez
Jeremy Meng