### Packages impacted by this PR
@azure/monitor-opentelemetry
Updated the metric export example to a sample app that properly exports
metrics to Azure Monitor.
### 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 @azure/monitor-opentelemetry-exporter
### 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)
Node made a breaking change in a security release for 18/20 where `spawn()` no longer loads `.cmd` files by default. nodejs/node#52554.
This PR sets the `shell: true` option when running vendored command on Windows.
also remove dependency on `@microsoft/api-extractor` as we already move to
`dev-tool run extract-api` which calls api-extractor Api instead.
***NO_CI***
### Packages impacted by this PR
@azure/monitor-opentelemetry
### 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)
---------
Co-authored-by: Hector Hernandez <39923391+hectorhdzg@users.noreply.github.com>
The smoke-tests pipeline has been disabled but I still cleaned up to
smoke tests to remove usages of sub-config-azure-cloud-test-resources
and try to use a service connection. When we decide to re-enable the
smoke tests pipeline we will want to update the deployment to use
federated auth as well.
@xirzec you disabled this pipeline 1/10/2023. Do you have any plans to
try and re-enable it? If not perhaps we just delete this instead.
### Packages impacted by this PR
N/A
### Issues associated with this PR
N/A
### Describe the problem that is addressed by this PR
Release Azure Communication Chat Version 1.5.3
### 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
### Packages impacted by this PR
@azure-rest/communication-messages
### Issues associated with this PR
### Describe the problem that is addressed by this PR
- New Models: We’ve introduced ImageNotificationContent,
AudioNotificationContent, DocumentNotificationContent, and
VideoNotificationContent, each with relevant fields like mediaUri,
caption, and fileName for their respective media types.
- MediaNotificationContent: To avoid a breaking change, we’ve retained
it. It is now marked as being deprecated starting from version
2024-08-30. As of this version, it will use image_v0 for
CommunicationMessageKind, and for earlier versions, it will continue to
use image .
### 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)
### Packages impacted by this PR
@azure/monitor-opentelemetry-exporter
### Describe the problem that is addressed by this PR
Exceptions should only be emitted from top level spans or those with a
remote parent.
### 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, tests are updated.
### 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/communication-signaling
### Describe the problem that is addressed by this PR
This PR is used for retrieving Trouter Config from Chat GW rather than
hardcode it in signaling client.
There are 2 main changes.
1.Remove the "environment" from SignalingClientOptions as it should be
retrieved from Chat GW;
2.Declare a TrouterConfigClientOptions and pass it to Signaling Client
constructor since this is needed for signaling client to make http call
to Chat Gateway.
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [Yes] Added impacted package name to the issue description
- [No] 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)_
- [TODO] Added a changelog (if necessary)
### Packages impacted by this PR
- `@azure-rest/core-client`
### Describe the problem that is addressed by this PR
Simplify `isCredential` helper used in getClient.ts. This change was
already made in the unbranded package but not in Azure core.
No change in the Unbranded diff report for this PR because I made the
change and updated the diff as part of #31487, just forgot to check in
this particular change. The unbranded diff check is currently reporting
a failure on main and this change should fix that.
### Packages impacted by this PR
update change log
### Issues associated with this PR
### Describe the problem that is addressed by this PR
update change log
### 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/attestation
### Issues associated with this PR
#31338
### Describe the problem that is addressed by this PR
Migrates `@azure/attestation` to ESM and tshy.
Co-authored-by: Deyaaeldeen Almahallawi <dealmaha@microsoft.com>
### Packages impacted by this PR
- `@typespec/ts-http-runtime`
### Describe the problem that is addressed by this PR
Updating the unbranded Core package with some recent changes in Core
that didn't make it over.
### Packages impacted by this PR
- `@typespec/ts-http-runtime`
### Describe the problem that is addressed by this PR
We have had issues with the unbranded Core package becoming out of sync
with the Azure packages. This PR adds a report which is a diff between
the Azure Core packages and the unbranded package and causes the lint
step to fail if there are any differences between Azure and unbranded
that do not appear in the report. Running the `lint:fix` script will
update the diff report. This will mean that:
- Making an Azure Core change without a corresponding change to
unbranded package, either in the source code or in the diff report, will
result in a CI failure
- Changes to the diff report can be reviewed so that any differences
between Azure and unbranded implementations of a feature can be easily
compared
Why use the lint script (and lint:fix)? This is already run by CI, so by
using it we don't need to make any changes to pipeline steps to get this
working. This script is a one-off and so I just want to do the bare
minimum to get things working 😄
Azure SDK Bot
ZiWei Chen
Praven Kuttappan
Jeremy Meng
Jackson Weber
Jiao Di (MSFT)
angellan-msft
Wes Haggard
Arif Ibrahim Mohamed
Timo van Veenendaal
Howie Leung
Maor Leger