chore(ci): bump build-and-inspect-python-package v2 -> v3.0.1 - #19
Merged
Conversation
The release build broke on main: hatchling now emits
`Metadata-Version: 2.5`, and the Twine bundled in the action's v2 rejects
it with
InvalidDistribution: Invalid distribution metadata:
'2.5' is not a valid metadata version
v3.0.0 ships Twine 7, which adds metadata 2.5 support (and PEP 794).
Not caused by the recently added LICENSE file: the commit before it,
without any LICENSE, already builds Metadata-Version 2.5. The trigger is
the PEP 639 `license = "<SPDX>"` field plus a newer hatchling, so every
hatchling package in this stack is affected on its next release.
Pinned to `@v3.0.1` rather than `@v3`: upstream deliberately stopped
force-tagging minor/micro releases in v3, so no moving `@v3` tag exists.
Interface is unchanged - same inputs, same `artifact-name` output, and the
uploaded artifact is still named `Packages`, so the download steps in this
workflow keep working.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Problem
The release workflow fails on
mainbefore uploading anything:Hatchling now emits
Metadata-Version: 2.5, and the Twine bundled inhynek/build-and-inspect-python-package@v2does not know that version.This is not the LICENSE commit
Worth stating explicitly, since the failure first showed up right after the
licensing PRs landed. It is unrelated — building the commit before the LICENSE
was added, with no
LICENSEfile in the tree at all, already produces:The trigger is the PEP 639
license = "<SPDX>"field plus a newer hatchling. TheLICENSE file only added a
License-File:line. Every hatchling package in thisstack hits this on its next release build, which is why the same bump is going
out across all of them.
Fix
Bump to
v3.0.1, whose release notes name exactly this: "Twine 7 that addssupport for packaging metadata 2.5 and PEP 794".
Pinned to the full version rather than
@v3on purpose — upstream stoppedforce-tagging minor/micro releases in v3, so there is no moving
@v3tag.Compatibility checked
Interface is identical between v2 and v3.0.1: same
inputs, sameartifact-nameoutput, and the artifact is still named
Packages(echo "name=Packages${BAIPP_INPUTS_UPLOAD_NAME_SUFFIX}"is byte-identical in both
action.ymlfiles), so thedownload-artifactstepslater in this workflow keep working unchanged.
🤖 Generated with Claude Code