[Retired] GitHub Actions: Self-hosted runner minimum version enforcement extended

[EiJackGH]

Why are you starting this discussion?

Product Feedback

What GitHub Actions topic or product is this about?

Actions Runner

Discussion Details

⚠️ Final Enforcement Date: March 16, 2026

GitHub has extended the deadline for the mandatory self-hosted runner upgrade by one week. As of March 16, 2026, all runner registrations and configurations using versions older than v2.329.0 (released Oct 2025) will be permanently blocked.

Important

This is a "Registration-Time" enforcement. Outdated runners will be rejected before they can connect, meaning they cannot self-upgrade once blocked.

📉 2026 Brownout Schedule (Remaining)

During these windows, GitHub will temporarily block connections from runners below v2.329.0 to help you identify unpatched systems.

*Note: Daylight Saving Time begins March 8, 2026. Adjust your local scripts accordingly

🛠️ What You Need To Do (EiJack Lab Checklist)

Audit Your Runners: Check the version on your active hosts.

Update Base Images: If you use Docker for your runners (like your botbuilder-js environment), update the Dockerfile to fetch the latest binary:
https://github.com/actions/runner/releases/download/v2.329.0/actions-runner-linux-x64-2.329.0.tar.gz

ARC Users: If using Actions Runner Controller, ensure your controller is on v0.14.0 or higher to support the new registration handshake.

GHES Exception: GitHub Enterprise Server (on-premises) customers are not impacted by this specific cloud enforcement.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐