[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"news:devops-github-actions-runner-enforcement-2026-06-14":3},{"meta":4,"markdown":60},{"type":5,"articleId":6,"slug":7,"title":8,"titleEn":9,"category":10,"summary":11,"publishedAt":12,"image":13,"vocabulary":14,"source":58},"news","news-devops-github-actions-runner-enforcement-2026-06-14","devops-github-actions-runner-enforcement-2026-06-14","GitHub Actions、古いセルフホストランナーの制限日程を公表","GitHub Sets an Enforcement Timeline for Outdated Self-Hosted Actions Runners","tech-devops","GitHub said on June 12, 2026 that it will resume minimum-version enforcement for self-hosted GitHub Actions runners on github.com and GitHub Enterprise Cloud with Data Residency. Runner version 2.329.0 becomes the minimum for registration, while active runners must keep installing new releases within 30 days to continue receiving jobs. GitHub is also scheduling temporary brownouts before full enforcement, giving platform teams time to refresh runner images, automation, and upgrade procedures.\n","2026-06-14T00:00:00Z","https:\u002F\u002Fimages.yamiyomi.com\u002Fnews\u002Fdevops-github-actions-runner-enforcement-2026-06-14.png",[15,20,25,30,34,38,42,46,50,54],{"word":16,"reading":17,"meaning":18,"level":19},"制限","せいげん","enforcement or restriction","N2",{"word":21,"reading":22,"meaning":23,"level":24},"実行基盤","じっこうきばん","execution platform","N1",{"word":26,"reading":27,"meaning":28,"level":29},"更新","こうしん","update","N3",{"word":31,"reading":32,"meaning":33,"level":24},"互換性","ごかんせい","compatibility",{"word":35,"reading":36,"meaning":37,"level":29},"登録","とうろく","registration",{"word":39,"reading":40,"meaning":41,"level":24},"自動更新","じどうこうしん","automatic update",{"word":43,"reading":44,"meaning":45,"level":24},"可用性","かようせい","availability",{"word":47,"reading":48,"meaning":49,"level":29},"停止","ていし","stop or suspension",{"word":51,"reading":52,"meaning":53,"level":19},"監査","かんさ","audit",{"word":55,"reading":56,"meaning":57,"level":19},"展開","てんかい","deployment or rollout",{"url":59},"https:\u002F\u002Fgithub.blog\u002Fchangelog\u002F2026-06-12-github-actions-minimum-version-enforcement-timeline-for-self-hosted-runners\u002F","\n::heading\nGitHub Actions、セルフホストランナーの[制限日程]{せいげんにってい:enforcement timeline:N3}を[公表]{こうひょう:announce:N3}\n\n#en\nGitHub Sets an Enforcement Timeline for Outdated Self-Hosted Actions Runners\n::\n\n::para\nGitHubは[6月12日]{ろくがつじゅうににち:June 12:N5}、GitHub Actionsのセルフホストランナーに[対する]{たいする:for:N3} [最小版]{さいしょうばん:minimum version:N2}の[制限]{せいげん:enforcement:N3}を[再開]{さいかい:resume:N2}すると[発表]{はっぴょう:announce:N3}した。[古い]{ふるい:old:N4} [版]{ばん:version:N2}のランナーは、[新しい]{あたらしい:new:N4} [実行基盤]{じっこうきばん:execution platform:N1}との[互換性]{ごかんせい:compatibility:N2}を[保てない]{たもてない:cannot maintain:N1}ため、[今後]{こんご:going forward:N5}は[段階的]{だんかいてき:phased:N2}な[移行]{いこう:migration:N2}が[必要]{ひつよう:necessary:N3}になるとされた。\n\n#en\nGitHub said on June 12 that it will resume minimum-version enforcement for self-hosted Actions runners. The company says older runners can no longer remain compatible with the newer execution platform, so teams now need a phased migration plan.\n::\n\n::para\nGitHubの[説明]{せつめい:explanation:N3}では、この[新しい]{あたらしい:new:N4} [基盤]{きばん:platform:N1}は1[日]{にち:day:N5}あたり1[億2千万件]{いちおくにせんまんけん:120 million jobs:N2}[以上]{いじょう:or more:N4}のジョブを[処理]{しょり:process:N3}し、[移行前]{いこうまえ:before migration:N2}の3[倍]{ばい:three times:N2}を[超える]{こえる:exceed:N2} [規模]{きぼ:scale:N1}まで[伸びた]{のびた:grew:N2}という。[企業]{きぎょう:enterprise:N1}ユーザーは1[分]{ふん:minute:N5}あたり7[倍]{ばい:seven times:N2} [多く]{おおく:more:N4}のジョブを[始められる]{はじめられる:can start:N4}ようになったとも[書かれた]{かかれた:was written:N5}。\n\n#en\nGitHub says the new platform now handles more than 120 million jobs per day, over three times the pre-migration volume. It also says enterprise users can start seven times more jobs per minute than before.\n::\n\n::heading\n[何]{なに:what:N5}が[変わる]{かわる:changes:N3}のか\n\n#en\nWhat Changes Now\n::\n\n::para\n[登録]{とうろく:registration:N2}や[再登録]{さいとうろく:reregistration:N2}をするランナーは、バージョン`2.329.0`[以上]{いじょう:or later:N4}であることが[必要]{ひつよう:required:N3}になる。この[版]{ばん:version:N2}より[古い]{ふるい:older:N4}ランナーは、[新基盤]{しんきばん:new platform:N1}に[認識]{にんしき:recognized:N3}されず、[接続]{せつぞく:connect:N2}もできないと[案内]{あんない:guidance:N1}された。\n\n#en\nAny runner used for registration or re-registration will need to be on version 2.329.0 or later. GitHub says older runners will no longer be recognized by the new platform and therefore will not connect.\n::\n\n::para\nただし、`2.329.0`は[永続的]{えいぞくてき:permanent:N2}な[下限]{かげん:floor:N3}ではない。ジョブを[受け続ける]{うけつづける:keep receiving:N3}には、[新しい]{あたらしい:new:N4}ランナー[公開版]{こうかいばん:released version:N2}が[出てから]{でてから:after it appears:N5} [30日]{さんじゅうにち:30 days:N5} [以内]{いない:within:N3}に[更新]{こうしん:update:N3}を[入れる]{いれる:apply:N5} [必要]{ひつよう:need:N3}があると[明記]{めいき:state explicitly:N3}された。\n\n#en\nVersion 2.329.0 is not a permanent floor. To keep receiving jobs, a runner must install each new release within 30 days after that release becomes available.\n::\n\n::para\n[自動更新]{じどうこうしん:automatic update:N3}を[有効]{ゆうこう:enabled:N2}にしているランナーは、この[条件]{じょうけん:requirement:N1}を[満たしやすい]{みたしやすい:easier to satisfy:N3}。[一方]{いっぽう:by contrast:N4}で、[自動更新]{じどうこうしん:automatic update:N3}を[止めている]{とめている:disabled:N4} [組織]{そしき:organizations:N1}は、[定期的]{ていきてき:regular:N3}な[手動更新]{しゅどうこうしん:manual update:N3}を[組む]{くむ:set up:N3} [必要]{ひつよう:need:N3}がある。GitHubは、[重大]{じゅうだい:critical:N4}なセキュリティ[更新]{こうしん:update:N3}が[出た]{でた:is published:N5} [時]{とき:when:N5}は、ジョブの[投入]{とうにゅう:queuing:N3}を[一時停止]{いちじていし:pause:N2}することもあるとした。\n\n#en\nRunners with auto-update enabled will satisfy the rule more easily. Organizations that disable auto-update will need a regular manual upgrade process, and GitHub says critical security updates can pause job queuing until they are applied.\n::\n\n::heading\n[日程]{にってい:schedule:N3}とブラウンアウト\n\n#en\nDates and Brownouts\n::\n\n::para\nGitHub Enterprise Cloud with Data Residencyでは、[完全]{かんぜん:full:N3} [適用]{てきよう:enforcement:N3}が[2026年7月31日]{にせんにじゅうろくねんしちがつさんじゅういちにち:July 31, 2026:N5}に[始まる]{はじまる:begins:N4}。GitHub Enterprise Cloudでは、[完全]{かんぜん:full:N3} [適用]{てきよう:enforcement:N3}が[2026年9月25日]{にせんにじゅうろくねんくがつにじゅうごにち:September 25, 2026:N5}に[始まる]{はじまる:begins:N4} [予定]{よてい:scheduled:N3}だ。\n\n#en\nFor GitHub Enterprise Cloud with Data Residency, full enforcement starts on July 31, 2026. For GitHub Enterprise Cloud, the date is September 25, 2026.\n::\n\n::para\nその[前]{まえ:before that:N5}に、GitHubは[一時的]{いちじてき:temporary:N4}なブラウンアウトを[実施]{じっし:carry out:N1}する。Data Residency[向け]{むけ:for:N3}では[6月29日]{ろくがつにじゅうくにち:June 29:N5}から、Enterprise Cloud[向け]{むけ:for:N3}では[8月24日]{はちがつにじゅうよっか:August 24:N5}から、[古い]{ふるい:old:N4}ランナーの[登録]{とうろく:registration:N2}やジョブ[実行]{じっこう:execution:N3}が[断続的]{だんぞくてき:intermittent:N3}に[止まる]{とまる:stop:N4}と[予告]{よこく:warn in advance:N3}された。\n\n#en\nBefore those deadlines, GitHub will run temporary brownouts. GitHub says intermittent registration and job-execution failures for outdated runners will begin on June 29 for Data Residency customers and on August 24 for Enterprise Cloud customers.\n::\n\n::heading\n[運用]{うんよう:operations:N4}への[影響]{えいきょう:impact:N1}\n\n#en\nOperational Impact\n::\n\n::para\nこの[変更]{へんこう:change:N3}で、プラットフォームチームは[単に]{たんに:simply:N3}`runner`バイナリを[上げる]{あげる:raise:N5}だけでは[足りない]{たりない:not enough:N4}。[登録]{とうろく:registration:N2}スクリプト、VMイメージ、コンテナイメージ、そして[自動展開]{じどうてんかい:automated rollout:N1}の[手順]{てじゅん:procedure:N2}まで[更新]{こうしん:update:N3}する[必要]{ひつよう:need:N3}がある。GitHubも、[古い]{ふるい:old:N4}テンプレートから[再作成]{さいさくせい:recreate:N2}したランナーは[見直す]{みなおす:review:N3}べきだと[勧めた]{すすめた:recommended:N1}。\n\n#en\nFor platform teams, this is not only a runner-binary upgrade. Registration scripts, VM images, container images, and deployment automation all need updates, and GitHub explicitly recommends reviewing runners recreated from old templates.\n::\n\n::para\n[大きい]{おおきい:large:N5} [運用群]{うんようぐん:fleets:N2}では、[現状]{げんじょう:current state:N3}の[監査]{かんさ:audit:N1}も[重要]{じゅうよう:important:N3}になる。GitHubは、[監査]{かんさ:audit:N1}ログやREST APIでランナー[版]{ばん:version:N2}を[調べる]{しらべる:inspect:N3} [手段]{しゅだん:means:N3}を[示した]{しめした:showed:N3}が、[接続中]{せつぞくちゅう:currently connected:N2}のランナー[全体]{ぜんたい:entire set:N3}を[完全]{かんぜん:fully:N3}に[表す]{あらわす:represent:N3}ものではないとも[注意]{ちゅうい:caution:N4}した。\n\n#en\nLarger fleets will also need an audit pass. GitHub points teams to audit logs and the REST API for runner-version visibility, while warning that registration events are not a complete inventory of every connected runner.\n::\n\n::callout\n[自動更新]{じどうこうしん:automatic update:N3}を[切っている]{きっている:turned off:N4} [組織]{そしき:organizations:N1}ほど、この[発表]{はっぴょう:announcement:N3}の[影響]{えいきょう:impact:N1}は[大きい]{おおきい:large:N5}と[見られる]{みられる:is likely seen:N5}。[可用性]{かようせい:availability:N3}を[守る]{まもる:protect:N3}には、ランナーの[寿命]{じゅみょう:lifecycle:N2}を[コード化]{こーどか:codify:N3}して[継続的]{けいぞくてき:continuous:N1}に[回す]{まわす:operate:N3} [体制]{たいせい:operating structure:N3}が[要る]{いる:is needed:N3}。\n\n#en\nThe organizations most exposed are likely the ones that intentionally turned off auto-update. Protecting availability now means codifying runner lifecycle work and operating it continuously.\n::\n\n::heading\n[今回]{こんかい:this time:N3}の[意味]{いみ:meaning:N4}\n\n#en\nWhy This Matters\n::\n\n::para\nこの[発表]{はっぴょう:announcement:N3}は、GitHub Actionsの[裏側]{うらがわ:backend side:N2}の[再設計]{さいせっけい:rearchitecture:N2}が、[単なる]{たんなる:mere:N3} [性能向上]{せいのうこうじょう:performance gain:N3}ではなく、[運用規律]{うんようきりつ:operational discipline:N2}まで[要求]{ようきゅう:require:N3}する[段階]{だんかい:stage:N2}に[入った]{はいった:entered:N5}ことを[示す]{しめす:show:N3}。セルフホストランナーを[使う]{つかう:use:N4}チームにとっては、CI\u002FCDの[実行基盤]{じっこうきばん:execution platform:N1}を「[古い]{ふるい:old:N4}まま[置く]{おく:leave:N3}」[余地]{よち:room:N3}が[狭くなる]{せまくなる:narrow:N1} [更新]{こうしん:update:N3}だと[言える]{いえる:can be said:N4}。\n\n#en\nThis announcement shows that the GitHub Actions rearchitecture is no longer just a performance story. For teams running self-hosted runners, it is now an operational-discipline change that leaves much less room to keep the CI\u002FCD execution layer on old images and old habits.\n::\n"]