ci: add workflow to release to PyPI
Metadata
Current evaluation
Merged a CI workflow to automate PyPI releases. Adapted from Starbase, the change configures self-hosted runners and targets Python 3.10. Approved by two reviewers, the update adds 60 lines to a single workflow file.
Suggested action: —
No scores available.
Issue body
This workflow file is a copy of Starbase's, with the modification to run on self-hosted runners (and to use Python 3.10 instead of 3.11).
- [ ] Have you followed the guidelines for contributing?
- [ ] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [ ] Have you successfully run `tox`?
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Merged a CI workflow to automate PyPI releases. Adapted from Starbase, the change configures self-hosted runners and targets Python 3.10. Approved by two reviewers, the update adds 60 lines to a single workflow file. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged a CI workflow to automate PyPI releases. Adapted from Starbase, the configuration runs on self-hosted runners using Python 3.10. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #224 ci: update Release workflow | starbase | merged | Merged update to the CI Release workflow. Replaced default GitHub runners with self-hosted jammy machines and swapped PYPI_API_TOKEN for PyPI Trusted Publishers. Constrained release artifacts. Approved by two reviewers. | |
| #2144 ci: use starbase release workflows | charmcraft | merged | Merged. Replaced the tox-based publishing workflow with starbase release workflows. Approved by two reviewers, updating three files (+88/-33 lines). |