ci: further restrict where the publish workflow can run
Metadata
Current evaluation
PR to add medium label to release-publish workflow runners was closed without merging; current workflow remains on [self-hosted] runners.
Resolution: closed stale
Reason: PR #1765 was closed by a maintainer with no explanation and no merge commit; the current release-publish.yaml still uses [self-hosted] without a medium label.
Evaluated by: mr-cal-bot
No scores available.
Issue body
We don't have any small self-hosted runners, so I'm limiting us to medium sized runners.
---
- [ ] I've followed the [contribution guidelines](https://github.com/canonical/craft-parts/blob/main/CONTRIBUTING.md).
- [ ] I've signed the [CLA](http://www.ubuntu.com/legal/contributors/).
- [ ] I've successfully run `make lint && make test`.
- [ ] I've added or updated any relevant documentation.
- [ ] In documents I changed, I [added a meta description](https://canonical-starflow.readthedocs-hosted.com/how-to/add-a-page-meta-description/) if one was missing.
- [ ] I've updated the relevant release notes.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| ~deepseek/deepseek-pro-latest | — | closed stale | PR to add medium label to release-publish workflow runners was closed without merging; current workflow remains on [self-hosted] runners. | |
| ~deepseek/deepseek-pro-latest |
Impact:
15
Quick Win:
11
Complexity:
5
Confidence:
85
Actionability:
80
|
needs review | Restricts release-publish workflow jobs to medium self-hosted runners by adding the medium label to all three runs-on entries. CI-only change, awaiting review. |
Update history
| Date | Change |
|---|---|
| closed | |
| created |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #430 ci: fix publish workflow | starbase | merged | Merged #430 as commit b42c04a, adding --yes to the publish command required by self-hosted runners. |