ci: disable auto-publish to pypi
Metadata
Current evaluation
Merged PR #390 as commit 01e800e, removing the PyPI auto-publish job because no PyPI token was configured in GitHub.
Resolution: closed resolved
Reason: PR #390 was approved and merged, deleting 13 lines from the release workflow. Commit 01e800e records the completed CI change.
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`?
-----
Disable pypi autopublishing. It hasn't worked anyways because there hasn't been a pypi token in github.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #390 as commit 01e800e, removing the PyPI auto-publish job because no PyPI token was configured in GitHub. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #390 disabled the unused PyPI auto-publish CI job because no PyPI token was configured; landed as commit 01e800e. | |
| qwen/qwen3.6-35b-a3b | — | closed resolved | Merged PR #390 to disable auto-publishing to PyPI in the CI workflow, as the feature was non-functional due to a missing PyPI token. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
canonical/craft-providers#725
(confidence 95%)
Later reintroduced tag-triggered PyPI publishing using Trusted Publishers in commit d58f9a8.
Related issues
No related issues found above the similarity threshold.