Skip to content

Update Release process doc #5159

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.

Sign up for GitHub

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

Merged
anrossi merged 7 commits into from
Jun 27, 2025
Merged

Update Release process doc #5159

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
e1cd44a
Update Release process doc
anrossi Jun 10, 2025
4bc9805
Update Release.md
anrossi Jun 10, 2025
f92d783
Update Release.md
anrossi Jun 10, 2025
70ad1ef
fix numbers
anrossi Jun 10, 2025
18c986c
Update Release.md
anrossi Jun 10, 2025
29e2231
Update Release.md
anrossi Jun 10, 2025
05f5812
Update Release.md
anrossi Jun 27, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions docs/Release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -141,6 +141,8 @@ The following are the complete (manual) steps for publishing the Rust crate.

## Synchronizing with Windows

1. Once the release branch is created, set the pipeline [here](https://mscodehub.visualstudio.com/msquic/_build?definitionId=1868) to ingest the release branch into Windows, and run it.
2. When the pipeline passes tests, it'll create a PR.
1. Once the release branch/tag is created, the undock pipeline should run automatically.
- If for some reason there's a problem, you may need to run the pipline manually by clicking on "Run Pipeline" [here](https://microsoft.visualstudio.com/undock/_build?definitionId=134439) (MSFT-only access required), scroll down to the **resources tab** and pick the MsQuic release tag of interest then run the pipeline.
- Another workaround to force a manual re-run by going [here](https://microsoft.visualstudio.com/undock/_git/msquic/tags) (MSFT-only access required) and deleting the tag, and then waiting for the [mirror pipeline](https://microsoft.visualstudio.com/undock/_build?definitionId=134727) (MSFT-only access required) to run automatically re-copy over the tag from GitHub.
2. Once the pipeline passes tests, get the VPACK ID from the "Create VPACK" stage, and create a PR to point [this file](https://microsoft.visualstudio.com/OS/_git/os.2020?path=/minio/netio/quic/msquic/msquic.man) (MSFT-only access required) to the VPACK created by the pipline run.
3. Review and merge the PR to complete the process.
Loading