Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DO NOT MERGE] Beta5 Changes #38400

Draft
wants to merge 67 commits into
base: main
Choose a base branch
from
Draft

Conversation

v-vdharmaraj
Copy link
Member

Description

Please add an informative description that covers that changes made by the pull request and link all relevant issues.

If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.

All SDK Contribution checklist:

  • The pull request does not introduce [breaking changes]
  • CHANGELOG is updated for new features, bug fixes or other significant changes.
  • I have read the contribution guidelines.

General Guidelines and Best Practices

  • Title of the pull request is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

  • Pull request includes test coverage for the included changes.

v-vdharmaraj and others added 30 commits May 10, 2024 13:00
* adding transcription changes

* updating the transcription changes

* updating the transcription changes
…and recognize media (#35692)

* updating changes for play prompts

* adding the support for play prompt list

* adding test for multipe prompts
* Added live test Media streaming and Transcription

* updating the live tests for media streaming and transcription

---------

Co-authored-by: Vinothini Dharmaraj <v-vdharmaraj@microsoft.com>
scbedd and others added 25 commits July 15, 2024 11:45
* pin setuptools to 69.2.0
* use virtualenv for our virtual environment creation instead of default venv
* source the virtual environment just before build steps, versus prepending path which was working unreliably
* remove venv use from test phase, as it wasn't actually having the effect we originally expected
* use a venv for test steps
* fix issue with language-specific certificate trust

* enable test proxy so we have a good test
* address the breaking release phase by using newer python version for tasks
* move usage of python version to as early as possible in build, analyze, build_extended, and test jobs
* during test phase, don't auto-prepend the path with the new venv location
* address issue with ensure service coverage
* Added CreateCallFailed event.

* Adding the changelog and version

* updating the release date

* Update CHANGELOG.md

---------

Co-authored-by: Vinothini Dharmaraj <v-vdharmaraj@microsoft.com>
Co-authored-by: Vinothini Dharmaraj <146493756+v-vdharmaraj@users.noreply.github.com>
@azure-sdk
Copy link
Collaborator

API change check

APIView has identified API level changes in this PR and created following API reviews.

azure-communication-callautomation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants