pandoras-box/mcp-web
Watch
8
0
Fork
You've already forked mcp-web
 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

ci: run compile jobs on the dev runner #6

Merged
Claude-Run merged 1 commit from fix/MCPWEB-6-compile-jobs-dev-runner into main 2026-08-01 03:10:55 +02:00
Conversation 0 Commits 1 Files changed 4 +20 -3
Claude-Run commented 2026-08-01 03:07:51 +02:00
Member
Copy link

The check and publish jobs both invoke a compiler (cargo fmt/clippy/build/test, and cargo publish which builds and verifies the crate before upload) but ran on RUNS_ON_OPENSUSE_BASE_LATEST, which carries no toolchain. Both now set runs-on to RUNS_ON_OPENSUSE_DEV_LATEST. create-release.yml only reads git log and calls the Forgejo API from nu, so it stays on the base label.

A step in check.yml enforces the rule mechanically: it fails if either compile workflow drops the dev label or reverts to the base one. CLAUDE.md records the rule in the .forgejo/workflows/ bullet, including why the label has to be set literally on each job.

#MCPWEB-6

The check and publish jobs both invoke a compiler (cargo fmt/clippy/build/test, and cargo publish which builds and verifies the crate before upload) but ran on RUNS_ON_OPENSUSE_BASE_LATEST, which carries no toolchain. Both now set runs-on to RUNS_ON_OPENSUSE_DEV_LATEST. create-release.yml only reads git log and calls the Forgejo API from nu, so it stays on the base label. A step in check.yml enforces the rule mechanically: it fails if either compile workflow drops the dev label or reverts to the base one. CLAUDE.md records the rule in the .forgejo/workflows/ bullet, including why the label has to be set literally on each job. #MCPWEB-6
ci: run compile jobs on the dev runner
All checks were successful
Check / fmt + clippy + build + tests (pull_request) Successful in 2m42s
Details
Create release / Create release from merged PR (pull_request) Has been skipped
Details
f4381bf285 
The check and publish jobs both invoke a compiler (cargo fmt/clippy/build/test, and cargo publish which builds and verifies the crate before upload) but ran on RUNS_ON_OPENSUSE_BASE_LATEST, which carries no toolchain. Both now set runs-on to RUNS_ON_OPENSUSE_DEV_LATEST. create-release.yml only reads git log and calls the Forgejo API from nu, so it stays on the base label.

A step in check.yml enforces the rule mechanically: it fails if either compile workflow drops the dev label or reverts to the base one. CLAUDE.md records the rule in the .forgejo/workflows/ bullet, including why the label has to be set literally on each job.

#MCPWEB-6
Claude-Run deleted branch fix/MCPWEB-6-compile-jobs-dev-runner 2026-08-01 03:10:55 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
pandoras-box/mcp-web!6
No description provided.