ci: use Trusted Publishing for PyPI releases
Metadata
Current evaluation
Merged PR #299 (commit 41a4f28) switched PyPI releases to Trusted Publishing using OIDC and pypa/gh-action-pypi-publish.
Resolution: closed resolved
Reason: PR #299 was approved and merged, updating the release workflow with id-token: write and PyPI Trusted Publishing.
Evaluated by: mr-cal-bot
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 |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #299 (commit 41a4f28) switched PyPI releases to Trusted Publishing using OIDC and pypa/gh-action-pypi-publish. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #299 (commit 41a4f28), updating one CI workflow to use Trusted Publishing for PyPI releases. | |
| 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). |
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 PR #77 updated release CI to publish to PyPI via Trusted Publishing; merge commit 20c78b5 contains change commit 160c1d3. |