DOC: Add Release Readiness step to release process docs#1450
Merged
rlundeen2 merged 3 commits intomicrosoft:mainfrom Mar 13, 2026
Merged
Conversation
Add a new step 1 (Release Readiness) to the release process that includes pre-release checks: verifying pending changes with maintainers, confirming CI pipelines pass, ensuring pyrit-internal is up to date, and updating scorer metrics. Renumber all subsequent steps accordingly. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
rlundeen2
force-pushed
the
users/rlundeen/2026_03_10_release_process_update
branch
from
240601a to
749cbcb
Compare
ValbuenaVC
approved these changes
Mar 10, 2026
romanlutz
reviewed
Mar 10, 2026
riyosha
pushed a commit
to riyosha/PyRIT
that referenced
this pull request
Mar 24, 2026
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Victor Valbuena <50061128+ValbuenaVC@users.noreply.github.com>
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
3 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.
Adds a new Step 1: Release Readiness to the release process documentation with pre-release checks that should be completed before starting a release:
evaluate_scorers.pyand commit results to keep scorer metrics currentAll subsequent steps are renumbered (now 1–10 instead of 1–9) and internal cross-references are updated.