Skip to content

FIX PR docs builds and queues - #2864

Merged
Roman Lutz (romanlutz) merged 6 commits into
microsoft:mainfrom
romanlutz:romanlutz-documentation-ci-correctness
Oct 2, 2026
Merged

Roman Lutz (romanlutz) merged 6 commits into
microsoft:mainfrom
romanlutz:romanlutz-documentation-ci-correctness

Conversation

@romanlutz

Copy link
Copy Markdown
Contributor

Description

A green docs check could validate unrelated main and release content instead of the PR being tested. PR builds also shared the production Pages queue, making them wait behind unrelated builds and publishing.

  • Build ordinary PRs from their immutable tested merge SHA, including PRs targeting release branches. This reduces ordinary PRs from six version builds to one. Composition-input changes still build all configured versions and exercise composition through the existing helpers.
  • Give each PR its own cancellable queue. Keep the entire production build, composition, and deployment pipeline in the existing non-cancelling pages group so a slow build cannot overtake another production deployment.
  • Separate read-only composition from privileged deployment. Only main push/manual runs can publish; release and non-main manual runs remain validation-only. Listed release refs validate their own tested commit, while unlisted release/manual refs validate under latest without removing historical outputs.
  • Key rendered caches by the tested workflow hash, version slug, and actual checked-out SHA, without partial-key fallbacks. Cover dependency, packaging, and asset inputs in PR filters, and publish Markdown-only docs changes after merging.

Full publication keeps every configured version, default/stable redirects, page manifests, the version picker, and each release's own build scripts and frozen dependencies. No Pages settings or branch protection changes are included. Live CI speedup has not been measured.

Tests and Documentation

101 focused tests passed, covering ordinary/composition PR selection, real Git merge and moving-ref scenarios, listed/unlisted release and manual refs, workflow permissions/concurrency/cache contracts, and composition/manifests/picker behavior. Ruff formatting/lint, type checks on changed Python files, actionlint 1.7.12, documentation structure validation, and applicable commit hooks passed.

Documented the CI behavior in the release guide. Validation ran on Windows with uv-managed Python 3.14.4; CI uses Python 3.13. No full Jupyter Book render, Jupytext execution, live workflow dispatch, or deployment was run.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Integrate microsoft/PyRIT main at 5ffd01a without conflicts.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Integrate microsoft/PyRIT main at 9bc882c without conflicts.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Integrate microsoft/PyRIT main at 83e2b79, preserving upstream release guidance and the docs CI validation changes.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Integrate microsoft/PyRIT main at ab1c6c8 without conflicts, preserving all prior feature work and upstream configuration.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Comment thread doc/contributing/10_release_process.md
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@romanlutz
Roman Lutz (romanlutz) added this pull request to the merge queue Oct 2, 2026
Merged via the queue into microsoft:main with commit 38d7e11 Oct 2, 2026
53 checks passed
@romanlutz
Roman Lutz (romanlutz) deleted the romanlutz-documentation-ci-correctness branch October 2, 2026 12:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants