The current runner was detected as self-hosted #147696
Replies: 2 comments
-
|
I had this same issue, and I found somewhere else that it isn't the platform itself that is the problem, but rather that uses: ruby/setup-ruby@086ffb1a2090c870a3f881cc91ea83aa4243d408 # v1.195.0 |
Beta Was this translation helpful? Give feedback.
-
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Body
For several months, I've had GitHub Page serving sites that I converted from WordPress to Jekyll. Even with the bizarre documentation, I managed to get them each up and running fine, with many, many content updates and changes over the months.
As of two days ago, none of them will build. I'm getting this message:
`The current runner (ubuntu-24.04-x64) was detected as self-hosted because the platform does not match a GitHub-hosted runner image (or that image is deprecated and no longer supported).
The only thing I am "self-hosting" is the content, some of the Minima theme files, and a couple of config files. Nothing has changed in anything but the content.
What am I missing? How do I get my sites to accept updates again?
Beta Was this translation helpful? Give feedback.
All reactions