GitHub Actions: Self-hosted runner minimum version enforcement extended

[samus-aran]

We’ve extended the timeline for configuration‑time version enforcement of the minimum self‑hosted runner requirement by one week. You now have until March 16, 2026 to upgrade your runners to v2.329.0 or later.

This extends the timeline we shared in our December 2025 announcement.

What's changing

Starting March 16, 2026, GitHub Actions will block configurations from self-hosted runners older than v2.329.0 (released October 15, 2025). Between February 16 and March 16, we'll run a brownout period with scheduled configuration blocks to help you identify runners that need updates.

After March 16, runners must meet the minimum version requirement before registration. Older runners won't be able to connect or self-upgrade after running the configuration script.

Brownout schedule

During the brownout period, we'll temporarily block configurations from runners below v2.329.0. This table shows when blocks will occur in major timezones:

Week	Dates (2026)	UTC Time	US Pacific	US Eastern	Central Europe	India	Japan/Korea	Australia East
1	Feb 16 (Sun)	08:00-09:00	00:00-01:00	03:00-04:00	09:00-10:00	13:30-14:30	17:00-18:00	19:00-20:00
2	Feb 23 (Sun)	08:00-10:00	00:00-02:00	03:00-05:00	09:00-11:00	13:30-15:30	17:00-19:00	19:00-21:00
2	Feb 25 (Tue)	16:00-18:00	08:00-10:00	11:00-13:00	17:00-19:00	21:30-23:30	01:00-03:00*	03:00-05:00*
3	Mar 2 (Mon)	00:00-04:00	16:00-20:00*	19:00-23:00*	01:00-05:00	05:30-09:30	09:00-13:00	11:00-15:00
3	Mar 4 (Wed)	12:00-16:00	04:00-08:00	07:00-11:00	13:00-17:00	17:30-21:30	21:00-01:00*	23:00-03:00*
3	Mar 6 (Fri)	20:00-00:00*	12:00-16:00	15:00-19:00	21:00-01:00*	01:30-05:30*	05:00-09:00*	07:00-11:00*
4	Mar 9 (Mon)	08:00 onwards	00:00 onwards	03:00 onwards	09:00 onwards	13:30 onwards	17:00 onwards	19:00 onwards

*Times marked with an asterisk fall on the next day in that timezone.

Full enforcement begins March 16, 2026. At that time, all configurations from runners below v2.329.0 will be permanently blocked.

What you need to do

Update all self-hosted runners to v2.329.0 or later by March 16, 2026:

1. Download the latest runner release from the Actions Runner releases page.
2. Update your installation scripts, images, or automation to install v2.329.0 or later before running ./config.sh.
3. Recreate or redeploy any runners built from images or templates that contain older versions.
4. Review the upgrade documentation for detailed guidance.

[shubham055555]

Thank you for the update and for extending the timeline.

The brownout approach is particularly helpful for identifying outdated runners before full enforcement. It provides a practical window to test and validate upgrade strategies without immediate disruption.

I have a couple of questions and suggestions:

1. For teams using containerized or image-based runners:
   Are there recommended strategies to ensure all cached or prebuilt images are consistently updated to the required version, especially in CI environments with multiple pipelines?

2. For automated infrastructure (e.g., Docker or VM-based runners):
   Would you recommend enforcing version checks at startup (pre-config step) to avoid failed registrations during brownout periods?

3. It would be useful to have:

   • A simple script or command to audit all registered self-hosted runners and their versions
   • Guidance on handling edge cases where runners fail to self-update due to restricted environments

Overall, the communication and phased rollout are well structured. This change will likely improve stability and security across self-hosted runner environments.

Appreciate the clear timeline and documentation.

[dahyallylh87-dotcom]

**__**# Monitoring your GitHub Copilot usage and entitlements (legacy)

Learn how you can monitor your monthly usage of Copilot and get the most value out of your Copilot plan.

[!IMPORTANT] This article only applies to Copilot Pro and Copilot Pro+ subscribers on an existing annual plan who remained on legacy premium request-based billing after June 1, 2026.

You can track your monthly usage of premium requests to help you get the most value from your Copilot plan.

Premium request counters reset on the 1st of each month at 00:00:00 UTC.

Viewing premium request usage

There are multiple ways to view your premium request usage:

• View current usage directly within your IDE
• Viewing an overview in your Billing and licensing settings
• View detailed analytics of your usage

If you reach your limit for premium requests, you will be notified with a message in each of the Copilot interfaces you use. To download a usage report, see Downloading usage reports.

Viewing usage in your IDE

If you're using Copilot in an editor, you can view your usage directly in the editor. For example, in Visual Studio Code, you can view information about features included in your plan, your progress towards any limits on your plan, and the date your allowance resets.

You can access usage information in the following IDEs.

• In Visual Studio Code, click the Copilot icon () in the status bar.
• In Visual Studio, click the Copilot icon () in the top right corner, then click Copilot Consumptions.
• In JetBrains IDEs, click the Copilot icon () in the status bar, then select View quota usage.
• In Xcode, click the Copilot icon () in the menu bar.
• In Eclipse, click the Copilot icon () in the status bar at the bottom of Eclipse.

Viewing an overview in your Billing and licensing settings

You can view an overview of your premium request usage at any time in your "Billing and licensing" settings on GitHub.com.

1. Open your billing overview page: https://github.com/settings/billing. The "Overview" page shows a summary of your current GitHub usage.
2. Scroll down to the "Metered usage" area and click Copilot to show only your Copilot use.

Viewing detailed analytics of your usage

1. Open your billing overview page: https://github.com/settings/billing.

2. In the side bar, click Premium request analytics to show detailed analytics.

3. Use the filter, "Group by", and "Timeframe" options to change the data displayed in the chart and table.

4. Optionally, to download the data shown in the chart, click the button and select your preferred format.

   

Downloading a usage report

For details on how to request a usage report, see Viewing your usage of metered products and licenses.

Optimizing usage of premium requests

You can use the following strategies to maximize the value of your premium requests:

• Choose the right model for the task. Some models are better suited to different tasks. If you're using a premium request, you can strategically choose which model you use to get the best result from Copilot. See AI model comparison.

• Setting a budget. Set a budget to track your overages and receive alerts when you reach 75%, 90%, or 100% of your budget. See Setting up budgets to control spending on metered products.

• Monitor your usage regularly. Check your usage in your GitHub account settings to see how many premium requests you’ve used. This helps you plan how much you can use for the rest of the month.

• Avoid retrying large prompts unnecessarily. Submitting the same long or complex prompt multiple times may use more premium requests. Try rephrasing or simplifying your request when needed.

[dahyallylh87-dotcom]

تم

[dahyallylh87-dotcom]

تم