Skip to content

Align package metadata version with release tag for PyPI publish - #52

Draft
sfluegel05 with Copilot wants to merge 2 commits into
devfrom
copilot/fix-pypi-publish-job
Draft

Align package metadata version with release tag for PyPI publish#52
sfluegel05 with Copilot wants to merge 2 commits into
devfrom
copilot/fix-pypi-publish-job

Conversation

Copilot AI commented Sep 1, 2026

Copy link
Copy Markdown

The pypi-publish job failed on release v1.2.2 because the build still produced 1.2.1 artifacts, and PyPI rejected re-upload of previously used filenames. This change aligns package metadata with the published release version so generated filenames are new and valid.

  • Root cause

    • Release tag and pyproject.toml version drifted (v1.2.2 vs 1.2.1), causing upload of stale artifact names.
  • Change

    • Updated project version in pyproject.toml:
    [project]
    - version = "1.2.1"
    + version = "1.2.2"
  • Workflow impact

    • python -m build now emits chebai_graph-1.2.2* distributions, matching the release and avoiding PyPI filename reuse rejection.

Co-authored-by: sfluegel05 <43573433+sfluegel05@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix failing GitHub Actions job pypi-publish Align package metadata version with release tag for PyPI publish Sep 1, 2026
Copilot AI requested a review from sfluegel05 September 1, 2026 09:04
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