Skip to content

docs: update release process guide - #4502

Merged
mnriem merged 4 commits into
github:mainfrom
philo-x:docs/4501-update-release-process-guide
Sep 17, 2026
Merged

mnriem merged 4 commits into
github:mainfrom
philo-x:docs/4501-update-release-process-guide

Conversation

@philo-x

@philo-x philo-x commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Description

RELEASE-PROCESS.md still described the removed per-agent ZIP pipeline and omitted the manual PyPI publisher. This updates the guide to match the current three-workflow release process, documents the development-version bump, and adds recovery guidance for independently incomplete GitHub and PyPI publication.

Closes #4501

Testing

  • git diff --check
  • Markdownlint v0.41.1 checked the full .github/workflows/RELEASE-PROCESS.md content with the repository rule configuration (0 issues).

AI Disclosure

  • I did not use AI assistance for this contribution
  • I did use AI assistance (described below)

Codex (models: GPT-5 and GPT-6) inspected the current workflows, drafted and refined the documentation update, addressed review feedback including the latest revision, and ran validation autonomously on behalf of @philo-x.

Document the separate PyPI workflow, remove obsolete per-agent ZIP steps, and add recovery guidance for incomplete releases.

Closes github#4501

Assisted-by: Codex (model: GPT-5, autonomous)
@philo-x
philo-x requested a review from mnriem as a code owner September 10, 2026 01:05
@mnriem mnriem added the triage-nice-to-have Verdict: evidence-backed fix or greenlit feature — land after review label Sep 10, 2026
@mnriem
mnriem requested a balanced review from Copilot September 10, 2026 14:06

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

Recovery coverage is incomplete, and version-mismatch guidance conflicts with the documented development bump.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Updates release documentation to reflect the current GitHub Release and PyPI workflows.

Changes:

  • Documents the three-workflow release process.
  • Adds development-version bump details.
  • Adds incomplete-release recovery guidance.
File summaries
File Description
.github/workflows/RELEASE-PROCESS.md Aligns release instructions with current workflows.
Review details

Suppressed comments (1)

.github/workflows/RELEASE-PROCESS.md:202

  • The recovery table does not satisfy #4501's requested completion model: it never covers the release branch/PR and collapses the wheel and sdist into a single “PyPI version” or “some distributions” state. Maintainers therefore still cannot verify and recover each of the four outputs independently. Add explicit status/recovery entries (or columns) for the release branch/tag, GitHub Release, wheel, and sdist.
| State | Recovery |
  • Files reviewed: 1/1 changed files
  • Comments generated: 1
  • Review effort level: Balanced

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread .github/workflows/RELEASE-PROCESS.md
@mnriem mnriem added the author-awaiting Waiting on author response label Sep 10, 2026
@mnriem

mnriem commented Sep 10, 2026

Copy link
Copy Markdown
Collaborator

Thanks @philo-x — useful refresh of the release docs. One open item from the review before this lands: documenting the development-version bump makes the existing "Version Mismatch" section (lines ~217–222) contradictory — once the release PR merges, main is intentionally on the next .dev0, so that guidance now needs to say that's expected, not a mismatch to fix. Could you reconcile those two sections so they agree?

Assisted-by: Codex (model: GPT-6, autonomous)
@philo-x

philo-x commented Sep 10, 2026

Copy link
Copy Markdown
Contributor Author

Posted on behalf of @philo-x by Codex; this review follow-up was authored and validated by the agent.

Commit 4dae159 clarifies that the release tag must match the package version at the tagged commit, while the merged release PR intentionally advances main to the next patch development version. It also adds recovery guidance for an incomplete release branch/PR and separate missing-wheel and missing-sdist states, including the limits of rerunning the current PyPI workflow after a partial upload.

Validation passed: git diff --check and markdownlint-cli2 v0.23.2 on .github/workflows/RELEASE-PROCESS.md (0 issues, using the locally cached CLI). No workflow behavior changed. @mnriem, please review this follow-up.

@philo-x

philo-x commented Sep 11, 2026

Copy link
Copy Markdown
Contributor Author

Posted on behalf of @philo-x by Codex; this follow-up and its validation were produced by the agent.

Commit cab314ea refines partial-release recovery: retry the failed publish job with the original dist artifact when available, allowing uv publish to skip identical files already on PyPI and upload missing files. Full workflow reruns rebuild the artifacts and require exact matches for already-published files. The guide now also keeps a valid intended tag during recovery, covers a pushed release branch with a missing tag, and describes GitHub Release creation and the development bump/PR as independent paths.

Validation passed: git diff --check and markdownlint-cli2 v0.23.2 on .github/workflows/RELEASE-PROCESS.md (0 issues). No workflow behavior changed.

@mnriem, please review the updated documentation.

@mnriem

mnriem commented Sep 14, 2026

Copy link
Copy Markdown
Collaborator

Thanks @philo-x — the version-mismatch correction and expanded recovery guidance address the earlier feedback. The distinction between the tagged release version and the next development version on main is now clear, as is recovery using the original publishing artifacts.

One disclosure detail remains: the PR description names GPT-5, while a follow-up commit names GPT-6. Please update the disclosure to cover the models used across the follow-up work, including the latest revision. The autonomous mode and extent are already documented.

No further documentation changes requested from this pass. The next maintainer step is checks and review on the current head.

Drafted for @mnriem by GitHub Copilot (model: GPT-6 Astra).

@mnriem mnriem added the author-needs-disclosure AI use, or the agent/model/settings behind it, not disclosed per CONTRIBUTING label Sep 14, 2026
@mnriem
mnriem requested a balanced review from Copilot September 14, 2026 19:20

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The documented partial-PyPI recovery relies on an artifact that becomes inaccessible during a job rerun.

Get a fresh assessment by requesting another Copilot review.

Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 1
  • Review effort level: Balanced

Comment thread .github/workflows/RELEASE-PROCESS.md Outdated
Preserve and verify original distributions before authorized publication, and document verified rebuild recovery when artifacts are unavailable.

Assisted-by: Codex (model: GPT-6, autonomous)
@philo-x

philo-x commented Sep 15, 2026

Copy link
Copy Markdown
Contributor Author

Posted on behalf of @philo-x by Codex (model: GPT-6, autonomous).

Commit 921d829a4228cde36c13be61855582cb3e747178 replaces the failed-job rerun recovery instructions with preservation of the original distributions, SHA-256 comparison against published files, and publication by an authorized maintainer. It also describes verified rebuild recovery when the original artifact is unavailable and clarifies the current workflow's input and credential limits. The PR disclosure now covers GPT-5 and GPT-6 across the follow-up work.

Validation passed: git diff HEAD^ HEAD --check and Markdownlint v0.41.1 via its API over the complete guide with the repository rule configuration (0 issues).

@mnriem, please review the updated head and approve the pending workflows. Please request a fresh Copilot review as well; the current author UI does not expose that control.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The documentation accurately reflects the workflow implementations and addresses issue #4501.

Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 0 new
  • Review effort level: Balanced

@mnriem
mnriem merged commit 180f8f3 into github:main Sep 17, 2026
15 checks passed
@mnriem

mnriem commented Sep 17, 2026

Copy link
Copy Markdown
Collaborator

Thank you!

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

Labels

author-awaiting Waiting on author response author-needs-disclosure AI use, or the agent/model/settings behind it, not disclosed per CONTRIBUTING triage-nice-to-have Verdict: evidence-backed fix or greenlit feature — land after review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Release process guide describes old ZIP variants and omits PyPI publishing

4 participants