ci: use Trusted Publishing for PyPI releases
Metadata
Current evaluation
Merged changes to update CI configuration for PyPI releases using Trusted Publishing. Approved by one reviewer with a single file modification (+6/-2 lines).
Suggested action: —
No scores available.
Issue body
- [ ] 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 changes to update CI configuration for PyPI releases using Trusted Publishing. Approved by one reviewer with a single file modification (+6/-2 lines). | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged a pull request updating the CI workflow to use Trusted Publishing for PyPI releases, streamlining authentication and removing manual token management. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #77 ci: use Trusted Publishing for PyPI releases | craft-grammar | merged | Merged a single-file CI update implementing Trusted Publishing for PyPI releases. Approved by two reviewers with zero unresolved comments and passing checks. | |
| #223 ci: update permissions for publishing to pypi | craft-store | merged | Merged after two approvals and passing CI. Updates CI permissions to resolve a failing job when publishing to PyPI. The change adds a single line to one file. | |
| #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. |