docs: clarify release process followups - #5232
Open
iscai-msft wants to merge 5 commits into
Open
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
iscai-msft
requested review from
Mark Cowlishaw (markcowl),
Timothee Guerin (timotheeguerin) and
Jeff Fisher (xirzec)
as code owners
August 14, 2026 16:17
Contributor
|
No changes needing a change description found. |
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: a9c5f8c1-6e8f-44a4-887f-ce06c121eacc
Contributor
|
You can try these changes here
|
| 5. After update PRs have been merged, review any remaining reported vulnerabilities in both the Repos' `Security` tabs and initiate a discussion on the `Engineering` channel regarding potential mitigations. `Security` tab links: [typespec](https://github.com/microsoft/typespec/security) and [typespec-azure](https://github.com/Azure/typespec-azure/security). | ||
| 2. Merge the `typespec-next` changes into the `RPSaasMaster` branch for the `-pr` repository. | ||
| 3. Reset `typespec-next` to `main` after completing the upgrades. | ||
| 4. Send an email to the `TypeSpec Partners` group announcing the release and link to the TypeSpec and TypeSpec Azure release notes. Include highlights when appropriate rather than duplicating the complete release notes. |
Member
There was a problem hiding this comment.
I'd like to receive these emails when it's not my turn to release, how about we also mention adding the TypeSpec Team in cc?
|
|
||
| ### Open questions and TODOs | ||
|
|
||
| 1. Determine whether the [data-plane linter-rule coverage guidance](https://github.com/Azure/azure-rest-api-specs/blob/main/.github/skills/azure-api-review/references/data-plane-linter-rule-coverage.md#-landing----merged-upstream-not-yet-running-here) must be updated after a newly added rule causes CI failures while upgrading package versions. |
Member
There was a problem hiding this comment.
I would like to find a solution where folks can add skills that rely on TypeSpec but which does not require us to include all their skills in our updates. In this particular case, the specs repo had some testing that failed on the update, so I think we need to investigate how to make the skills robust to typespec changes so that their owners have a couple of days to update after a tsp library version update
| 1. Determine whether the [data-plane linter-rule coverage guidance](https://github.com/Azure/azure-rest-api-specs/blob/main/.github/skills/azure-api-review/references/data-plane-linter-rule-coverage.md#-landing----merged-upstream-not-yet-running-here) must be updated after a newly added rule causes CI failures while upgrading package versions. | ||
| 2. Define a safe process for updating specification files in the specification repositories without overwriting changes merged to `main` while the update PR is being prepared. | ||
| 3. Confirm with Mark and Timothee which files should be updated after running `pnpm upgrade --latest -r -i`, including whether to prefer broader or narrower dependency updates. | ||
| 4. Automate bidirectional synchronization between `typespec-next` and `main` in `azure-rest-api-specs`. |
Member
There was a problem hiding this comment.
+1 to this, seems like something we should be able to automate
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: a9c5f8c1-6e8f-44a4-887f-ce06c121eacc
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
TODO
typespec-nextandmaininazure-rest-api-specs.Testing