Skip to content

Fix release gate tooling sync#113

Merged
zacharyr0th merged 1 commit into
mainfrom
codex/docpull-release-gate
Jul 16, 2026
Merged

Fix release gate tooling sync#113
zacharyr0th merged 1 commit into
mainfrom
codex/docpull-release-gate

Conversation

@zacharyr0th

Copy link
Copy Markdown
Contributor

What changed

  • install the pinned release tool requirements into the release-gate virtual environment
  • keep the existing locked project and extras sync unchanged

Why

The v6.3.0 publish run built the distributions successfully, but the A+ scorecard launched scripts/build_release.py and twine from .venv, where neither package had been installed. That made package_build and twine_check fail and skipped trusted publishing.

Validation

  • parsed .github/workflows/publish.yml with PyYAML
  • installed requirements-release.txt into .venv with the exact workflow command
  • imported build==1.5.0 and twine==6.2.0 from that environment
  • git diff --check
  • commit-time gitleaks scan

@admin-raintree
admin-raintree force-pushed the codex/docpull-release-gate branch from 1bc234b to bf8ea6b Compare July 16, 2026 20:14

@admin-raintree admin-raintree 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.

Release-gate dependency fix verified against the pinned tool requirements; all required checks pass.

@zacharyr0th
zacharyr0th enabled auto-merge (squash) July 16, 2026 20:18
@zacharyr0th
zacharyr0th merged commit d915215 into main Jul 16, 2026
19 checks passed
@zacharyr0th
zacharyr0th deleted the codex/docpull-release-gate branch July 16, 2026 20:19
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