Releases: Azure/azure-sdk-for-js
Releases · Azure/azure-sdk-for-js
@azure/schema-registry-json_1.0.0
Add communications TFV ownership (#31128)
@azure/openai_1.0.0-beta.13
1.0.0-beta.13 (2024-09-17)
Other Changes
- Deprecation notice: The Azure OpenAI client library for JavaScript beta will be retired on January 14th, 2025. Please migrate to the stable OpenAI SDK for JavaScript using the migration guide before that date.
@azure/openai-assistants_1.0.0-beta.6
1.0.0-beta.6 (2024-09-17)
Other Changes
- Deprecation notice: The Azure OpenAI Assistants client library for JavaScript beta will be retired on January 14th, 2025. Please migrate to the stable OpenAI SDK for JavaScript using the migration guide before that date.
@azure/identity_4.5.0-beta.3
[Identity] update changelog for beta release (#31144)
@azure/schema-registry_1.3.0
[sample][image-analysis] update the dependency package version in pac… …kage.json (#30301) Fixes [#28746](https://github.com/Azure/azure-sdk-for-js/issues/28746) @joheredi and @dargilco for notification.
@azure/microsoft-playwright-testing_1.0.0-beta.3
1.0.0-beta.3 (2024-09-16)
This release provides better error messaging and error handling by improving logging.
Bugs Fixed
- Optimized test result publishing by reusing the Sas uri till it's expiry.
- Fixed unexpected process termination by improving error handling of API used to publish test results.
@azure/monitor-opentelemetry_1.7.1
[notification-hubs] Separate broadcast from send operations (#31102) ### 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)
@azure/monitor-opentelemetry-exporter_1.0.0-beta.26
[notification-hubs] Separate broadcast from send operations (#31102) ### 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)
@azure/core-util_1.10.0
fix(playwrighttesting): Updated error handling for reporting (#31090) ### 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)
@azure/core-rest-pipeline_1.17.0
fix(playwrighttesting): Updated error handling for reporting (#31090) ### 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)