Skip to content

Clarify retention of old preview artifacts - #5666

Draft
Jianing Wang (MSFT) (jianingwang123) with Copilot wants to merge 2 commits into
mainfrom
copilot/clarify-preview-after-preview-guidance
Draft

Jianing Wang (MSFT) (jianingwang123) with Copilot wants to merge 2 commits into
mainfrom
copilot/clarify-preview-after-preview-guidance

Conversation

Copilot AI commented Oct 10, 2026 •

Copy link
Copy Markdown
Contributor

Removing an older preview from active TypeSpec versioning does not automatically require deleting its generated OpenAPI or examples. The guidance now makes retention the default and reserves removal for confirmed retirement or when the artifacts are no longer needed.

  • Default: Keep old preview artifacts if they’re still needed or the team is unsure.
  • Optional cleanup: After confirming retirement or no ARM registration/RPaaS live-validation need, remove artifacts in a separate follow-up PR.

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
1 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

Co-authored-by: jianingwang123 <141212663+jianingwang123@users.noreply.github.com>
@microsoft-github-policy-service microsoft-github-policy-service Bot added the meta:website TypeSpec.io updates label Oct 10, 2026
Copilot AI changed the title [WIP] Clarify preview-after-preview guidance for OpenAPI retention Clarify retention of old preview artifacts Oct 10, 2026

This branch has not been deployed

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

Labels

meta:website TypeSpec.io updates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants