Menu

Post image 1
Post image 2
1 / 2
0

When GitHub Actions Goes Silent: The Pending-Forever Bug I Hit Shipping My MCP Server to npm

DEV Community·אחיה כהן·about 1 month ago
#swpPXY56
#npm#part#github#fullscreen#macos#runs
Reading 0:00
15s threshold

I have an open-source MCP server . I tag a release, push, GitHub Actions builds, npm publishes, MCP Registry updates. That's the contract. It worked for v2.7.6 through v2.8.4. Then v2.8.5 didn't publish. Neither did v2.8.6. Or v2.9.0. Or v2.9.1. Or v2.9.2. Or v2.9.3. Six releases stuck. Not failing — stuck . Yellow dot. Forever. Here's what was actually happening. And how I got the releases out without GitHub Actions. The symptom that doesn't match any docs Every release event triggered the workflow. Every workflow showed up in the runs list. None of them ever started a job. $ gh run view 25001890100 --json status,conclusion,jobs { "status" : "queued" , "conclusion" : null, "jobs" : [] } Enter fullscreen mode Exit fullscreen mode No conclusion. No jobs. Empty pending_deployments . Not "waiting for approval". Not "in_progress". Not "failure". Just pending with no work scheduled — for 125 hours. If you search "GitHub Actions stuck pending", you'll find a hundred forum posts.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More