Guard Canonical PyPI Artifact Naming - #849
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a regression test to prevent drift in the canonical PyPI build artifact stem (pypi-build-) across the repository’s workflow contracts and default publishing surfaces, and to ensure the legacy pypilibrary-build- stem does not reappear in tracked content.
Changes:
- Add a unit test that asserts key contracts/docs/action content contains
pypi-build-. - Add a repository-wide
git grepcheck in the test suite that fails ifpypilibrary-build-appears in tracked files.
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Uh oh!
There was an error while loading. Please reload this page.
ptr727
marked this pull request as ready for review
August 19, 2026 18:59
Uh oh!
There was an error while loading. Please reload this page.
Merged
ptr727 added a commit
that referenced
this pull request
Aug 19, 2026
## Summary - Promote fail-closed release validation and audit path discovery. - Promote explicit Bash labels for executable audit commands. - Promote the canonical PyPI artifact-name regression guard. - Promote the executable Python entry point for the release-guard test. - Promote the internally consistent missing-job audit fixture. ## Source - #844 (`a08713a`) - #847 (`af2c8ff`) - #848 (`1cd5b84`) - #849 (`87c3960`) - #850 (`9b6c01f`) - #851 (`bb4d603`) ## Validation - 730 Python tests - audit self-tests and spec validation - ruff, mypy, and coverage - actionlint, markdownlint, EditorConfig, CSpell, ShellCheck, and PSScriptAnalyzer - Copilot full-diff review on each feature pull request Closes#842Closes#843Closes#845
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
pypi-build-artifact stem in both carried contractspypilibrary-build-stem anywhere in tracked contentRoot Cause
The artifact rename in #821 aligned the existing contracts and implementations, but no automated check bound those surfaces together. A later edit could therefore recreate the contradiction reported by #845.
Impact
Contract drift between the hub and downstream PyPI workflows fails in the unit-test gate before it can be carried into another repository.
Verification
python3 -m unittest scripts.tests.test_release_guardspython3 -m unittest discover -s scripts/tests(730 tests)uvx ruff@latest check scripts/tests/test_release_guards.pyuvx ruff@latest format --check scripts/tests/test_release_guards.pygit diff --checkCloses#845