Skip to content

Conversation

@seilorjunior
Copy link

The swagger file has a new version (3.2)

The swagger file has a new version
@prmerger-automator
Copy link
Contributor

@seilorjunior : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit d18bcc9:

✅ Validation status: passed

File Status Preview URL Details
articles/ai-services/speech-service/swagger-documentation.md ✅Succeeded

For more details, please refer to the build report.

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

Updates the Speech service Swagger specification documentation to reference the latest version 3.2 instead of the previous version 3.1.

  • Updated the URL in the Swagger specification link to point to version 3.2
  • Updated the documentation text to reflect the new version

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

## Generating code from the Swagger specification

The [Swagger specification](https://github.com/Azure/azure-rest-api-specs/blob/master/specification/cognitiveservices/data-plane/Speech/SpeechToText/stable/v3.1/speechtotext.json) has options that allow you to quickly test for various paths. However, sometimes it's desirable to generate code for all paths, creating a single library of calls that you can base future solutions on. Let's take a look at the process to generate a Python library for the Speech to text REST API version 3.1.
The [Swagger specification](https://github.com/Azure/azure-rest-api-specs/blob/master/specification/cognitiveservices/data-plane/Speech/SpeechToText/stable/v3.2/speechtotext.json) has options that allow you to quickly test for various paths. However, sometimes it's desirable to generate code for all paths, creating a single library of calls that you can base future solutions on. Let's take a look at the process to generate a Python library for the Speech to text REST API version 3.1.
Copy link

Copilot AI Sep 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The text mentions generating a Python library for 'Speech to text REST API version 3.1' but the URL now points to v3.2. This creates inconsistency in the documentation. The version reference should be updated to 3.2 to match the updated URL.

Copilot uses AI. Check for mistakes.
@v-dirichards
Copy link
Contributor

@PatrickFarley

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged C+L Pull Request Review Team label label Sep 30, 2025
@github-actions
Copy link

This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions.
Get Help
Docs Support Teams Channel
Resolve Merge Conflict

@github-actions github-actions bot added the inactive This PR is inactive for more than 14 days label Oct 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

aq-pr-triaged C+L Pull Request Review Team label azure-ai-speech/svc Change sent to author do-not-merge inactive This PR is inactive for more than 14 days

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants