Skip to content

fix(device): drop iOS 17 and five iOS devices, and mirror the iPhone … - #288

Merged
finalerock44 merged 1 commit into
devfrom
feat/removals-2026-11-02
Nov 2, 2026
Merged

finalerock44 merged 1 commit into
devfrom
feat/removals-2026-11-02

Conversation

@finalerock44

Copy link
Copy Markdown
Contributor

…16 / iOS 26 default

The API removes iOS 17 and the iphone-15, iphone-16-plus, iphone-16-pro, iphone-16-pro-max and ipad-pro-6th-gen devices on 2 Nov 2026, and moves the default iOS target from iPhone 14 / iOS 17 to iPhone 16 / iOS 26. Each half still defaults on its own. iphone-14 stays, with iOS 18 only.

  • The help-text enums lose iOS 17 and the five devices; validation already follows the live compatibility data.
  • The default mirror is iphone-16 / 26, so a request that names one half is checked against the other half the API will actually use. A device-only request for a device without iOS 26 (now including iphone-14) is told to pass --ios-version, which is what the API answers too. A device-only iphone-17, iphone-air or M5 iPad request, or a version-only --ios-version 27, is no longer refused.
  • MCP examples and test fixtures use devices and versions the API still offers.

schema.types.ts is deliberately not regenerated: the API drift would come with it.

What & why

Type of change

  • fix — bug fix
  • feat — new feature
  • perf — performance improvement
  • refactor — code change that's neither a fix nor a feature
  • docs — documentation only
  • chore / ci / build / test — tooling, no user-facing change
  • Breaking change (title has ! or PR notes a BREAKING CHANGE:)

Checklist

  • PR title follows the Conventional Commits format (see comment above)
  • pnpm lint passes
  • pnpm typecheck passes
  • pnpm build passes
  • I have not bumped the version or edited CHANGELOG.md (release-please handles this)
  • I have signed the CLA (the bot will prompt on first contribution)
  • Docs / README.md / STYLE_GUIDE.md updated if behaviour or output changed

How to test

…16 / iOS 26 default

The API removes iOS 17 and the iphone-15, iphone-16-plus, iphone-16-pro,
iphone-16-pro-max and ipad-pro-6th-gen devices on 2 Nov 2026, and moves
the default iOS target from iPhone 14 / iOS 17 to iPhone 16 / iOS 26.
Each half still defaults on its own. iphone-14 stays, with iOS 18 only.

- The help-text enums lose iOS 17 and the five devices; validation
  already follows the live compatibility data.
- The default mirror is iphone-16 / 26, so a request that names one half
  is checked against the other half the API will actually use. A
  device-only request for a device without iOS 26 (now including
  iphone-14) is told to pass --ios-version, which is what the API answers
  too. A device-only iphone-17, iphone-air or M5 iPad request, or a
  version-only --ios-version 27, is no longer refused.
- MCP examples and test fixtures use devices and versions the API still
  offers.

schema.types.ts is deliberately not regenerated: the API drift would
come with it.
@finalerock44 finalerock44 self-assigned this Nov 2, 2026
@claude

claude Bot commented Nov 2, 2026

Copy link
Copy Markdown

Code review

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

@finalerock44
finalerock44 merged commit 86acd62 into dev Nov 2, 2026
9 checks passed
@finalerock44
finalerock44 deleted the feat/removals-2026-11-02 branch November 2, 2026 12:04
@claude claude Bot mentioned this pull request Nov 2, 2026
1 of 14 tasks
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