The post GitHub to Retire macOS 13 Runner Image by December 2025 appeared on BitcoinEthereumNews.com. Darius Baruo Sep 19, 2025 17:59 GitHub announces the deprecation of the macOS 13 runner image by December 4, 2025, with scheduled brownouts to raise awareness of the change. GitHub has announced its decision to retire the macOS 13 runner image by December 4, 2025, as part of its ongoing updates to the GitHub Actions platform. According to The GitHub Blog, this move is aimed at encouraging users to transition to newer macOS versions and architectures. Scheduled Brownout Periods To ensure users are aware of the upcoming change, GitHub will temporarily fail jobs that utilize the macOS 13 runner during scheduled brownout periods. These brownouts are slated for the following dates and times: November 4, 14:00 UTC to November 5, 00:00 UTC November 11, 14:00 UTC to November 12, 00:00 UTC November 18, 14:00 UTC to November 19, 00:00 UTC November 25, 14:00 UTC to November 26, 00:00 UTC Migration Recommendations As part of the deprecation process, GitHub has outlined several migration paths for users. Workflows that are architecture agnostic are encouraged to transition to arm64 labels such as macos-15, macos-latest, or macos-14. For those requiring x86_64 (Intel) architecture, new labels like macos-15-intel have been introduced to support standard runner users. Future of macOS x86_64 (Intel) Architecture The announcement also highlighted the broader deprecation of x86_64 (Intel) architecture by Apple. GitHub plans to cease support for this architecture on macOS after the retirement of the macOS 15 runner image in Fall 2027. Users are advised to begin migrating to arm64-based (Apple Silicon) runners to ensure compatibility with future updates. For detailed information on label changes and migration strategies, users can visit the runner images repository on GitHub’s platform. This transition reflects the ongoing shift towards more modern architectures and the need for… The post GitHub to Retire macOS 13 Runner Image by December 2025 appeared on BitcoinEthereumNews.com. Darius Baruo Sep 19, 2025 17:59 GitHub announces the deprecation of the macOS 13 runner image by December 4, 2025, with scheduled brownouts to raise awareness of the change. GitHub has announced its decision to retire the macOS 13 runner image by December 4, 2025, as part of its ongoing updates to the GitHub Actions platform. According to The GitHub Blog, this move is aimed at encouraging users to transition to newer macOS versions and architectures. Scheduled Brownout Periods To ensure users are aware of the upcoming change, GitHub will temporarily fail jobs that utilize the macOS 13 runner during scheduled brownout periods. These brownouts are slated for the following dates and times: November 4, 14:00 UTC to November 5, 00:00 UTC November 11, 14:00 UTC to November 12, 00:00 UTC November 18, 14:00 UTC to November 19, 00:00 UTC November 25, 14:00 UTC to November 26, 00:00 UTC Migration Recommendations As part of the deprecation process, GitHub has outlined several migration paths for users. Workflows that are architecture agnostic are encouraged to transition to arm64 labels such as macos-15, macos-latest, or macos-14. For those requiring x86_64 (Intel) architecture, new labels like macos-15-intel have been introduced to support standard runner users. Future of macOS x86_64 (Intel) Architecture The announcement also highlighted the broader deprecation of x86_64 (Intel) architecture by Apple. GitHub plans to cease support for this architecture on macOS after the retirement of the macOS 15 runner image in Fall 2027. Users are advised to begin migrating to arm64-based (Apple Silicon) runners to ensure compatibility with future updates. For detailed information on label changes and migration strategies, users can visit the runner images repository on GitHub’s platform. This transition reflects the ongoing shift towards more modern architectures and the need for…

GitHub to Retire macOS 13 Runner Image by December 2025



Darius Baruo
Sep 19, 2025 17:59

GitHub announces the deprecation of the macOS 13 runner image by December 4, 2025, with scheduled brownouts to raise awareness of the change.





GitHub has announced its decision to retire the macOS 13 runner image by December 4, 2025, as part of its ongoing updates to the GitHub Actions platform. According to The GitHub Blog, this move is aimed at encouraging users to transition to newer macOS versions and architectures.

Scheduled Brownout Periods

To ensure users are aware of the upcoming change, GitHub will temporarily fail jobs that utilize the macOS 13 runner during scheduled brownout periods. These brownouts are slated for the following dates and times:

  • November 4, 14:00 UTC to November 5, 00:00 UTC
  • November 11, 14:00 UTC to November 12, 00:00 UTC
  • November 18, 14:00 UTC to November 19, 00:00 UTC
  • November 25, 14:00 UTC to November 26, 00:00 UTC

Migration Recommendations

As part of the deprecation process, GitHub has outlined several migration paths for users. Workflows that are architecture agnostic are encouraged to transition to arm64 labels such as macos-15, macos-latest, or macos-14. For those requiring x86_64 (Intel) architecture, new labels like macos-15-intel have been introduced to support standard runner users.

Future of macOS x86_64 (Intel) Architecture

The announcement also highlighted the broader deprecation of x86_64 (Intel) architecture by Apple. GitHub plans to cease support for this architecture on macOS after the retirement of the macOS 15 runner image in Fall 2027. Users are advised to begin migrating to arm64-based (Apple Silicon) runners to ensure compatibility with future updates.

For detailed information on label changes and migration strategies, users can visit the runner images repository on GitHub’s platform. This transition reflects the ongoing shift towards more modern architectures and the need for developers to adapt to evolving technological standards.

Image source: Shutterstock


Source: https://blockchain.news/news/github-retire-macos-13-runner-image-december-2025

Market Opportunity
ChainAware Logo
ChainAware Price(AWARE)
$0.001193
$0.001193$0.001193
0.00%
USD
ChainAware (AWARE) Live Price Chart
Disclaimer: The articles reposted on this site are sourced from public platforms and are provided for informational purposes only. They do not necessarily reflect the views of MEXC. All rights remain with the original authors. If you believe any content infringes on third-party rights, please contact service@support.mexc.com for removal. MEXC makes no guarantees regarding the accuracy, completeness, or timeliness of the content and is not responsible for any actions taken based on the information provided. The content does not constitute financial, legal, or other professional advice, nor should it be considered a recommendation or endorsement by MEXC.

You May Also Like

The Channel Factories We’ve Been Waiting For

The Channel Factories We’ve Been Waiting For

The post The Channel Factories We’ve Been Waiting For appeared on BitcoinEthereumNews.com. Visions of future technology are often prescient about the broad strokes while flubbing the details. The tablets in “2001: A Space Odyssey” do indeed look like iPads, but you never see the astronauts paying for subscriptions or wasting hours on Candy Crush.  Channel factories are one vision that arose early in the history of the Lightning Network to address some challenges that Lightning has faced from the beginning. Despite having grown to become Bitcoin’s most successful layer-2 scaling solution, with instant and low-fee payments, Lightning’s scale is limited by its reliance on payment channels. Although Lightning shifts most transactions off-chain, each payment channel still requires an on-chain transaction to open and (usually) another to close. As adoption grows, pressure on the blockchain grows with it. The need for a more scalable approach to managing channels is clear. Channel factories were supposed to meet this need, but where are they? In 2025, subnetworks are emerging that revive the impetus of channel factories with some new details that vastly increase their potential. They are natively interoperable with Lightning and achieve greater scale by allowing a group of participants to open a shared multisig UTXO and create multiple bilateral channels, which reduces the number of on-chain transactions and improves capital efficiency. Achieving greater scale by reducing complexity, Ark and Spark perform the same function as traditional channel factories with new designs and additional capabilities based on shared UTXOs.  Channel Factories 101 Channel factories have been around since the inception of Lightning. A factory is a multiparty contract where multiple users (not just two, as in a Dryja-Poon channel) cooperatively lock funds in a single multisig UTXO. They can open, close and update channels off-chain without updating the blockchain for each operation. Only when participants leave or the factory dissolves is an on-chain transaction…
Share
BitcoinEthereumNews2025/09/18 00:09
USDC Treasury mints 250 million new USDC on Solana

USDC Treasury mints 250 million new USDC on Solana

PANews reported on September 17 that according to Whale Alert , at 23:48 Beijing time, USDC Treasury minted 250 million new USDC (approximately US$250 million) on the Solana blockchain .
Share
PANews2025/09/17 23:51
US S&P Global Manufacturing PMI declines to 51.8, Services PMI falls to 52.9 in December

US S&P Global Manufacturing PMI declines to 51.8, Services PMI falls to 52.9 in December

The post US S&P Global Manufacturing PMI declines to 51.8, Services PMI falls to 52.9 in December appeared on BitcoinEthereumNews.com. The business activity in
Share
BitcoinEthereumNews2025/12/16 23:24