ci: release to pypi
Metadata
Current evaluation
Merged PR #725 in commit d58f9a8, adding a tag-triggered CI workflow to build Python artifacts and publish releases to PyPI.
Resolution: closed resolved
Reason: PR #725 was approved by two reviewers and merged as commit d58f9a8. It introduced the PyPI release workflow ported from starbase.
Evaluated by: mr-cal-bot
No scores available.
Issue body
- [x] Have you followed the guidelines for contributing?
- [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [x] Have you successfully run `tox`?
-----
Pulled directly from starbase to allow for releases to Pypi.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #725 in commit d58f9a8, adding a tag-triggered CI workflow to build Python artifacts and publish releases to PyPI. | |
| qwen/qwen3.6-35b-a3b | — | closed resolved | Added CI workflow for PyPI releases, pulled from starbase project. Approved by 2 reviewers and merged. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #259 ci: add workflow to release to PyPI | craft-cli | merged | Merged PR #259 in commit 6d95a8d, adding a PyPI release workflow adapted from Starbase for self-hosted runners using Python 3.10. | |
| #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. | |
| #77 ci: use Trusted Publishing for PyPI releases | craft-grammar | merged | Merged PR #77 updated release CI to publish to PyPI via Trusted Publishing; merge commit 20c78b5 contains change commit 160c1d3. | |
| #224 ci: update Release workflow | starbase | merged | Merged PR #224 in commit 3f3b5f6, updating release CI to use self-hosted Jammy runners, PyPI Trusted Publishing, and constrained GitHub release artifacts. |