Tag & release to pypi
Metadata
Current evaluation
PyPI tagging and releases were implemented through the Starbase-based release publisher in PR #35 (commit 96e04a1).
Resolution: closed resolved
Reason: PR #35 updated the release publisher from Starbase, and the repository's release workflow now builds and publishes a PyPI package. No closing comment was recorded on #8, making #35 the strongest implementation evidence.
Evaluated by: mr-cal-bot
No scores available.
Issue body
No description provided.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | PyPI tagging and releases were implemented through the Starbase-based release publisher in PR #35 (commit 96e04a1). | |
| stealth/space-bunny-alpha | — | closed resolved | PyPI tagging and publishing was added in PR #103 (commit 6363b31), which introduced the release workflow used to publish the package. | |
| qwen/qwen3.6-35b-a3b | — | closed stale | Issue closed without resolution or discussion; no body or comments provided. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
canonical/craft-platforms#35
(confidence 78%)
Commit 96e04a1 updated the release publisher and added the automation needed to publish releases to PyPI.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #361 Auto-publish to pypi | craft-providers | closed | PR #384 (commit 9cb2ccd) added the starbase-style release workflow, automating PyPI publishing for tagged releases. | |
| #384 ci: add release publishing workflow | craft-providers | merged | Merged PR #384 as commit 9cb2ccd, adding Starbase’s release-publishing workflow to automate PyPI releases and resolving #361. |