ci(release): verify a release tag matches the declared version - #2
Draft
a7vinx wants to merge 1 commit into
Draft
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
Two files declare the version and nothing compared them to the tag. PyPI refuses to replace an uploaded version, so a tag naming one version while the package declares another cannot be corrected in place — only yanked and re-cut under a version number that is then spent. A tag build now checks all three agree before anything is built, naming the files that disagree. The README says how to install unreleased work: pip builds any branch or commit straight from the repository, which is what someone trying the latest actually needs. No pre-release is published. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
a7vinx
force-pushed
the
feat/preview-release
branch
from
954565d to
4c3a0c6
Compare
August 8, 2026 14:29
a7vinx
marked this pull request as draft
August 8, 2026 14:59
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.
Summary
The package version is declared in pyproject.toml and in src/pine_assistant/__init__.py, and a release tag names it a third time. Nothing compared them.
PyPI does not permit a version to be replaced once uploaded. A tag naming one version while the package declares another publishes the package under a name nobody was given, and the only remedy is to yank and re-cut under a version number that is then spent.
Changes
A tag build verifies all three agree before anything is built, and identifies the files that disagree when they do not. RELEASING.md documents the guard alongside the release steps.
The README documents how to install unreleased work:
pip install "git+https://github.com/19PINE-AI/pine-assistant-python@main"pip builds any branch or commit directly from the repository.
Not included
No pre-release publishing. An earlier revision added a manual trigger that stamped a .dev version and published a preview to PyPI; it was removed. Installing from the repository serves the same purpose without consuming version numbers, which on PyPI can be yanked but never deleted or reused.
Verification
🤖 Generated with Claude Code