Repository navigation
Ci: Publish to PyPI when a GitHub Release is published, not on a tag push - #67
Merged
Merged
Conversation
…push Standardized across the repositories by the ecosystem lead. PyPI never accepts the same version twice, so publishing has to be a deliberate act: a v* tag trigger would fire on a stray `git push --tags`, while a Release records the tag and its notes together. publish-pypi.yml now runs on `release: published` and checks the Release's tag (github.event.release.tag_name) against pyproject.toml. The `pypi` environment keeps its v* tag policy, since a Release runs on its tag's ref. AGENTS.md section 15, SPEC S1.1 and PROJECT.md describe the step: publish a GitHub Release tagged v<version> (an alpha marked pre-release) after the maintainer approves; a bare tag push publishes nothing. ci: publish trigger. documentation corrected: AGENTS.md 15, SPEC S1.1, PROJECT.md. The YAML parses; tests unchanged (the version check script is the same). Refs #66
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes #66
publish-pypi.ymlnow triggers onrelease: publishedand checksgithub.event.release.tag_nameagainst pyproject. A baregit push --tagsno longer publishes; a version can't be re-uploaded to PyPI, so publishing stays deliberate. Thepypienvironment keeps itsv*tag policy. AGENTS §15, SPEC S1.1 and PROJECT.md are updated. Tests are unchanged.