Skip to content

Use most powerful Linux runner for publishing #20

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ammario merged 1 commit into from
Sep 10, 2025
Merged

Use most powerful Linux runner for publishing #20

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .github/workflows/publish.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ jobs:
publish:
name: Publish to crates.io
needs: tests
runs-on: ubuntu-latest
runs-on: ubuntu-latest-xlarge
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot Sep 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[P1] Avoid unavailable GitHub runner label

Switching the publish job to runs-on: ubuntu-latest-xlarge assumes the repository has access to GitHub’s larger hosted runners. Unless the organization is explicitly configured for large runners, this label does not resolve and the workflow fails to start with “No hosted runner found” errors, blocking every release. Consider retaining ubuntu-latest or using a self-hosted label that is guaranteed to exist.

Useful? React with 👍 / 👎.

environment: publish

steps:
Expand Down Expand Up @@ -56,4 +56,4 @@ jobs:
- name: Publish to crates.io
run: cargo publish --token ${{ secrets.CARGO_REGISTRY_TOKEN }}
env:
CARGO_REGISTRY_TOKEN: ${{ secrets.CARGO_REGISTRY_TOKEN }}
CARGO_REGISTRY_TOKEN: ${{ secrets.CARGO_REGISTRY_TOKEN }}