Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Restore automatic PyPI Docker checks after the 1.2.0 release

未关闭
  • 哪里不对？
#3,007 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
docker, github-actions, python
领域
ci-cd, documentation, testing

调研方向

Start with docker_build.yml and tests/unit/infra/test_docker_ci.py; review the workflow conditions and event cases described in the issue. After 1.2.0 is published, validate the wheel and run the specified PyPI checks before restoring automatic runs. Update the Docker CI and release documentation, and confirm a main push runs the checks while PRs, merge-queue runs, and release-branch pushes remain skipped.

由索引模型根据 Issue 内容生成。

描述

Context

Follow-up to #2969 and Hannah's review comment.

The PyPI Docker lane is being temporarily restricted to manual workflow dispatches. The latest published release, 1.1.0, predates the compatibility mechanism introduced in #2829. Its wheel includes a frontend but lacks pyrit/_compatibility.py, pyrit/_compatibility.json, and pyrit/backend/frontend/compatibility.json, so the production image predictably fails after building the devcontainer and installing the package.

The pause avoids repeating that expensive failure on every main push. It must not become a permanent loss of automatic published-release coverage.

After publishing 1.2.0

  • Verify the actual published 1.2.0 wheel contains the compatibility module, Python stamp, packaged frontend, and matching frontend stamp from one clean source commit. Do not generate replacement stamps during Docker installation.
  • Manually run docker_build.yml with pypiVersion=1.2.0 and confirm the PyPI production image, import, GUI, and Jupyter checks pass with the production compatibility guard enabled.
  • Run the workflow without an override and confirm it selects and exercises the latest stable, non-yanked published release successfully.
  • Restore github.ref == 'refs/heads/main' || github.event_name == 'workflow_dispatch' on build-and-test-pypi. Restore the same eligibility condition inside always() on all four pypi-*-check jobs.
  • Update PYPI_CONDITION and the event cases in tests/unit/infra/test_docker_ci.py: main pushes and manual dispatches enable the PyPI lane; PRs, merge-queue runs, and release-branch pushes remain intentionally skipped.
  • Update the Docker CI and release documentation to remove the temporary manual-only guidance, and verify a main push runs the restored checks.

Keep automatic latest-release selection, independent local/PyPI jobs, named fail-closed gates, source isolation, compatibility/auth enforcement, and no-publish behavior unchanged. If the published artifacts still fail validation, keep this issue open and fix the release prerequisite rather than bypassing the guard or selecting a different release silently.

This is a post-release follow-up. Merging #2969 should not close it.

主要语言
Python
星标
4.6k
派生
924
平均合并
2 天 18 小时
30 天内合并 PR
251

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

microsoft/PyRIT 的其他 Issue

查看 microsoft/PyRIT 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。