Skip to content

Reorganize versioning docs out of ARM subdirectory#4217

Open
Copilot wants to merge 7 commits intomainfrom
copilot/reorganize-versioning-documents
Open

Reorganize versioning docs out of ARM subdirectory#4217
Copilot wants to merge 7 commits intomainfrom
copilot/reorganize-versioning-documents

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Apr 8, 2026

  • Rebase on latest main to ensure no merge conflicts and clean commit history
  • Add redirect entries to website/astro.config.mjs for all moved/renamed/deleted docs
  • Fix formatting of 01-about-versioning.md
  • Verify all PR files pass prettier formatting
  • Verify only versioning doc changes are in the PR diff (no unrelated files)
  • Move versioning links to end of 01-about-versioning.md under new "Additional Information on TypeSpec Versioning" heading
  • Apply text suggestion on line 31 of 01-about-versioning.md
  • Promote Uncommon Scenarios to ## heading in 01-about-versioning.md
  • Move Note to ARM example section in 06-evolving-apis.md
  • Pull latest from main, verify formatting and clean diff

Copy link
Copy Markdown
Member

@markcowl markcowl left a comment

Choose a reason for hiding this comment

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

In addition to the changes outlined in my review, look through the documents looking for examples, and, in each case where there is an example that would be significantly different for ARM versus data-plane (operations are significantly different for ARM versus data-plane APIs, for example)

Once changes are made, ensure that all files are correctly formatted, there are no misspellings, and no merge issues with main after you pull the latest changes.

Comment thread website/src/content/docs/docs/howtos/Versioning/01-about-versioning.md Outdated
Comment thread website/src/content/docs/docs/howtos/Versioning/01-about-versioning.md Outdated
Comment thread website/src/content/docs/docs/howtos/Versioning/01-about-versioning.md Outdated
Comment thread website/src/content/docs/docs/howtos/Versioning/01-about-versioning.md Outdated
Comment thread website/src/content/docs/docs/howtos/Versioning/01-about-versioning.md Outdated
Comment thread website/src/content/docs/docs/howtos/Versioning/01-about-versioning.md Outdated
Comment thread website/src/content/docs/docs/howtos/Versioning/01-about-versioning.md Outdated
Comment thread website/src/content/docs/docs/howtos/Versioning/01-about-versioning.md Outdated
Copy link
Copy Markdown
Contributor Author

Copilot AI commented Apr 8, 2026

In addition to the changes outlined in my review, look through the documents looking for examples, and, in each case where there is an example that would be significantly different for ARM versus data...

Reviewed all documents for ARM vs data-plane differences. Added data-plane equivalents alongside ARM operation examples in:

  • 06-evolving-apis.md — all operation examples (Simple Scenarios, Complex Scenarios, and Versioning Decorators sections) now show both ARM and data-plane patterns
  • getstarted/versioning.md — version declaration and all operation examples now show both ARM and data-plane patterns

Model-level examples (adding/removing properties, renaming, etc.) are unchanged since they work identically for both ARM and data-plane.

All files checked with codespell — no spelling issues. Merge with main verified clean. Done in c6aa80b.

Copilot AI requested a review from markcowl April 8, 2026 22:04
@markcowl
Copy link
Copy Markdown
Member

markcowl commented Apr 8, 2026

/azp run typspec-azure - PR Tools

@azure-pipelines
Copy link
Copy Markdown

No pipelines are associated with this pull request.

@markcowl
Copy link
Copy Markdown
Member

markcowl commented Apr 9, 2026

/azp run typespec-azure - PR Tools

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@azure-sdk
Copy link
Copy Markdown
Collaborator

No changes needing a change description found.

@azure-sdk
Copy link
Copy Markdown
Collaborator

azure-sdk commented Apr 9, 2026

You can try these changes here

🛝 Playground 🌐 Website

@markcowl
Copy link
Copy Markdown
Member

@copilot please pull the latest from main, ensure there are no merge issues, and verify that only your changes are in the PR

Copilot AI force-pushed the copilot/reorganize-versioning-documents branch from c6aa80b to 31077eb Compare April 13, 2026 23:49
Copy link
Copy Markdown
Contributor Author

Copilot AI commented Apr 13, 2026

@copilot please pull the latest from main, ensure there are no merge issues, and verify that only your changes are in the PR

Rebased on latest main in 31077eb — no merge conflicts. Verified that only my documentation changes are in the PR (11 files, all under website/src/content/docs/).

Copy link
Copy Markdown
Member

@markcowl markcowl left a comment

Choose a reason for hiding this comment

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

Make these changes, pull the latest from main, ensure that there are no merge conflicts, all files are correctly formatted, and the pr contains only your changes

Comment thread website/src/content/docs/docs/getstarted/versioning.md Outdated
Comment thread website/src/content/docs/docs/howtos/Versioning/03-stable-after-preview.md Outdated
Comment thread website/src/content/docs/docs/howtos/Versioning/06-evolving-apis.md Outdated
Comment thread website/src/content/docs/docs/howtos/Versioning/06-evolving-apis.md Outdated
Comment thread website/src/content/docs/docs/howtos/Versioning/06-evolving-apis.md Outdated
Comment thread website/src/content/docs/docs/howtos/Versioning/06-evolving-apis.md
Copy link
Copy Markdown
Contributor Author

Copilot AI commented Apr 14, 2026

Make these changes, pull the latest from main, ensure that there are no merge conflicts, all files are correctly formatted, and the pr contains only your changes

All changes applied, rebased on latest main with no conflicts, verified only documentation changes are in the PR. Done in 2e94dc2.


- [How to manage a single active preview if your service always has some features in preview (ARM only)](./uncommon-scenarios/02-perpetual-preview.md)

## Should I Retain the OpenAPI for an Old Preview API (ARM Only)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I believe data-plane is doing this as well, at the very least I dont believe anybody is going back and removing old preview swaggers for dp either

Copy link
Copy Markdown
Member

@markcowl markcowl Apr 20, 2026

Choose a reason for hiding this comment

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

They will actually be prevented from doing this by TypeSpec Validation, so my guess is that by and large they are not.

I just ran into a PR for a data plane that decided they needed to do this for no good reason because the documentation was there. I would really like to discourage everyone from leaving their old preview specs around, but for some ARM specs, doing so is potentially catastrophic

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Is this a relatively new addition to typespec validation? I havent seen this enforced in any pr I've run across. This is an older spec on TypeSpec that has several older previews checked in, but only has the current stable versions in versioning enum: https://github.com/Azure/azure-rest-api-specs/blob/main/specification/cognitiveservices/ContentSafety/main.tsp

Another older service with this same issue: https://github.com/Azure/azure-rest-api-specs/blob/main/specification/ai/DocumentIntelligence/main.tsp

This service is in a slightly different boat because it still specifies all the previews in the api version enum: https://github.com/Azure/azure-rest-api-specs/blob/main/specification/ai/Face/main.tsp

so just wanted to call out that this doesnt seem to be enforced

Copy link
Copy Markdown
Member

@markcowl markcowl left a comment

Choose a reason for hiding this comment

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

Make these changes, pull the latest from main, validate that all files are correctly formateed and only your changes are in the PR

Comment thread website/src/content/docs/docs/howtos/Versioning/01-about-versioning.md Outdated
Comment thread website/src/content/docs/docs/howtos/Versioning/01-about-versioning.md Outdated
Comment thread website/src/content/docs/docs/howtos/Versioning/01-about-versioning.md Outdated
Comment thread website/src/content/docs/docs/howtos/Versioning/06-evolving-apis.md
Copilot AI and others added 7 commits April 21, 2026 00:31
…ntroductions, update links

Agent-Logs-Url: https://github.com/Azure/typespec-azure/sessions/e3f6341b-5c80-4f75-8fe5-e8b9a30074e8

Co-authored-by: markcowl <1054056+markcowl@users.noreply.github.com>
…e examples, update headings

Agent-Logs-Url: https://github.com/Azure/typespec-azure/sessions/83ebf765-92d4-4c47-8eab-eb4aa807c173

Co-authored-by: markcowl <1054056+markcowl@users.noreply.github.com>
…Required section, apply suggestions, remove data-plane examples

Agent-Logs-Url: https://github.com/Azure/typespec-azure/sessions/56c71242-0384-4237-b485-c9d866377d88

Co-authored-by: markcowl <1054056+markcowl@users.noreply.github.com>
…tion, move Note to ARM section

Agent-Logs-Url: https://github.com/Azure/typespec-azure/sessions/557330e7-cce9-4916-94ca-12a9636bc60c

Co-authored-by: markcowl <1054056+markcowl@users.noreply.github.com>
Copilot AI force-pushed the copilot/reorganize-versioning-documents branch from 637db28 to 9282536 Compare April 21, 2026 00:33
Copy link
Copy Markdown
Contributor Author

Copilot AI commented Apr 21, 2026

Make these changes, pull the latest from main, validate that all files are correctly formateed and only your changes are in the PR

All review changes applied, rebased on latest main, all files pass prettier formatting, and only versioning doc changes are in the PR diff. Done in 9282536.

Copilot AI requested a review from markcowl April 21, 2026 00:34
@markcowl
Copy link
Copy Markdown
Member

/azp run typespec-azure - PR Tools

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@markcowl markcowl marked this pull request as ready for review April 21, 2026 00:41
Copy link
Copy Markdown
Member

@catalinaperalta catalinaperalta left a comment

Choose a reason for hiding this comment

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

dp additions lgtm :)

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

Labels

eng meta:website TypeSpec.io updates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants