Skip to content

docs: iPhone 16 Pro Max and the gpu1 runner type were removed on 9 No… - #161

Merged
finalerock44 merged 2 commits into
mainfrom
feat/removals-2026-11-09
Nov 9, 2026
Merged

finalerock44 merged 2 commits into
mainfrom
feat/removals-2026-11-09

Conversation

@finalerock44

Copy link
Copy Markdown
Contributor

…vember 2026

A usage check found that iPhone 16 Pro Max and the gpu1 runner type each carry less than 1% of 7-day usage, so under the support policy they were removed on 9 November 2026. iPhone 16 Pro still carries more than 1%, so it stays, deprecated, with removal now targeted for 7 December 2026, subject to change based on usage. iOS 17, Pixel 7 and Maestro 2.2.0 are not changed here.

  • Devices & OS Versions: the iPhone 16 Pro Max row is gone. The deprecation warning names only iPhone 16 Pro and its new target date, and a removal sentence says runs that target iPhone 16 Pro Max are rejected and where to move them: iphone-16 (the default), iphone-17, iphone-air, iphone-18-pro or iphone-18-pro-max.
  • Runner Type: the gpu1 row is gone, and the warning says it was removed and that Android runs which still pass it, per upload or per flow, run on cpu1 at the standard Android rate rather than failing (iOS still rejects it). The limitations no longer mention gpu1. This also drops a stray "|" after the old warning's closing ":::".
  • Concurrency: the gpu1 column is gone, and the warning says its runs now count towards the cpu1 limit.
  • Billing, README, GitHub Actions, EAS Workflows, Bitbucket Pipelines, Google Play APIs, Per-flow Devices and the MCP tools page no longer offer gpu1 or iphone-16-pro-max. iphone-16-pro stays, deprecated.

…vember 2026

A usage check found that iPhone 16 Pro Max and the gpu1 runner type each
carry less than 1% of 7-day usage, so under the support policy they were
removed on 9 November 2026. iPhone 16 Pro still carries more than 1%, so
it stays, deprecated, with removal now targeted for 7 December 2026,
subject to change based on usage. iOS 17, Pixel 7 and Maestro 2.2.0 are
not changed here.

- Devices & OS Versions: the iPhone 16 Pro Max row is gone. The
  deprecation warning names only iPhone 16 Pro and its new target date,
  and a removal sentence says runs that target iPhone 16 Pro Max are
  rejected and where to move them: iphone-16 (the default), iphone-17,
  iphone-air, iphone-18-pro or iphone-18-pro-max.
- Runner Type: the gpu1 row is gone, and the warning says it was removed
  and that Android runs which still pass it, per upload or per flow, run
  on cpu1 at the standard Android rate rather than failing (iOS still
  rejects it). The limitations no longer mention gpu1. This also drops a
  stray "|" after the old warning's closing ":::".
- Concurrency: the gpu1 column is gone, and the warning says its runs
  now count towards the cpu1 limit.
- Billing, README, GitHub Actions, EAS Workflows, Bitbucket Pipelines,
  Google Play APIs, Per-flow Devices and the MCP tools page no longer
  offer gpu1 or iphone-16-pro-max. iphone-16-pro stays, deprecated.
@finalerock44 finalerock44 self-assigned this Nov 7, 2026
@claude

claude Bot commented Nov 7, 2026

Copy link
Copy Markdown

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.

…November 2026

iOS 17, Pixel 7 and Maestro 2.2.0 were targeted for 9 November 2026, subject to usage. All three were still over 1% on the 2026-11-06 check, so their removal is now targeted for 23 November 2026.
@finalerock44
finalerock44 merged commit dfa60bf into main Nov 9, 2026
2 checks passed
@finalerock44
finalerock44 deleted the feat/removals-2026-11-09 branch November 9, 2026 11:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant