ci: add release publishing workflow
Metadata
Current evaluation
Merged PR #384 as commit 9cb2ccd, adding Starbase’s release-publishing workflow to automate PyPI releases and resolving #361.
Resolution: closed resolved
Reason: PR #384 was merged into main as commit 9cb2ccd. Its release workflow implements the automatic PyPI publishing requested in issue #361.
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`?
-----
Add release publishing workflow from starbase.
Resolves #361
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #384 as commit 9cb2ccd, adding Starbase’s release-publishing workflow to automate PyPI releases and resolving #361. | |
| qwen/qwen3.6-35b-a3b | — | closed resolved | Merged PR #384 to add a release publishing workflow from starbase, resolving issue #361. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
canonical/craft-providers#361
(confidence 100%)
The auto-publish-to-PyPI issue was explicitly resolved by merged PR #384.
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. | |
| #361 Auto-publish to pypi | craft-providers | closed | PR #384 (commit 9cb2ccd) added the starbase-style release workflow, automating PyPI publishing for tagged releases. | |
| #998 Add release-publish workflow from starbase | craft-parts | merged | Merged PR #998 via commit dab83ab6, adding Starbase's release-publish workflow to automate publishing releases. | |
| #35 ci: update release publisher workflow from starbase | craft-platforms | merged | Merged PR #35 updated the Starbase-derived release-publish workflow, with 17 additions and 7 deletions in one CI file. | |
| #169 ci: add release-publish workflow from starbase | craft-cli | closed | Closed unmerged after being returned to draft pending agreement on CI release publishing; the proposed Starbase release-publish workflow was not landed. | |
| #2144 ci: use starbase release workflows | charmcraft | merged | Merged in canonical/charmcraft#2144 via commit 739941a5, replacing tox-based publishing with Starbase release workflows. | |
| #815 ci: fix publishing workflow | craft-application | merged | Merged PR #815 fixed the publishing workflow in commit 86fcd407 with a one-line update to .github/workflows/release-publish.yaml. | |
| #725 ci: release to pypi | craft-providers | merged | Merged PR #725 in commit d58f9a8, adding a tag-triggered CI workflow to build Python artifacts and publish releases to PyPI. | |
| #8 Tag & release to pypi | craft-platforms | closed | PyPI tagging and releases were implemented through the Starbase-based release publisher in PR #35 (commit 96e04a1). | |
| #596 ci: fix release workflow | starbase | merged | Merged PR canonical/starbase#596 by mr-cal adds GH_REPO to the release workflow so the `gh` CLI knows the target repo; a one-line fix for breakage introduced by #585. |