Skip to content

chore: promote cli 5.11.1 - #293

Merged
finalerock44 merged 11 commits into
productionfrom
promote/cli-5.11.1
Nov 2, 2026
Merged

chore: promote cli 5.11.1#293
finalerock44 merged 11 commits into
productionfrom
promote/cli-5.11.1

Conversation

@finalerock44

@finalerock44 finalerock44 commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

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

finalerock44 and others added 11 commits October 28, 2026 13:11
@finalerock44
chore(deps): bump the qs override to 6.16.1 (#285)
2e5b87c 
GHSA-6pq8-jhm2-2vcw (moderate, published 2026-10-28) covers qs up to
6.16.0, which is exactly where the override held it, so the CI audit
fails on every branch. 6.16.1 is the lowest patched version in the
major; the lockfile change is qs alone (it reaches us through
@modelcontextprotocol/sdk > express). Dependabot cannot bump an
overridden pin, hence by hand, as for hono.
@finalerock44
chore(help): list iphone-duo in the --ios-device help text (#284)
e289df5 
The device enum only feeds --help; validation runs against the live
compatibility payload, which advertises the iPhone Duo since the
production API deploy on 2026-10-27.
@dcd-release-please @finalerock44
@riglar @github-actions
chore: merge production into dev after 5.11.0 (#283)
638d71d 
* ReleaseAs: 5.8.0

* Release-As: 5.8.0

* Release-As: 5.8.0

* chore(production): release 5.8.0

* chore: pin the 5.9.0 promotion

Release-As: 5.9.0

* chore(production): release 5.9.0

* chore: pin the 5.10.0 promotion

Release-As: 5.10.0

* chore(production): release 5.10.0

* chore: pin the 5.11.0 promotion

Release-As: 5.11.0

* chore(production): release 5.11.0

---------

Co-authored-by: finalerock44 <[email protected]>
Co-authored-by: finalerock44 <[email protected]>
Co-authored-by: dcd-release-please[bot] <296541543+dcd-release-please[bot]@users.noreply.github.com>
Co-authored-by: Tom Riglar <[email protected]>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@riglar @claude
chore(deps): override minimatch to 11.0.1 and glob to 14.0.2 (#287)
aef5640 
GHSA-g3hv-75wg-m249 (minimatch <11.0.1) and GHSA-3g3m-2fjr-6pw4
(glob >=9.0.0 <=14.0.1) are both moderate, so the CI audit fails on
every branch. Both reach us only through dev tools: minimatch through
eslint and mocha, glob through mocha. The patched versions are new
majors, so they are pinned by override; lint, the unit suite and the
build all pass on them.

Co-authored-by: Claude Opus 5.5 <[email protected]>
@finalerock44
fix(device): drop iOS 17 and five iOS devices, and mirror the iPhone … (
86acd62 
#288)

fix(device): drop iOS 17 and five iOS devices, and mirror the iPhone 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
fix(cloud): show notices before rejecting an unsupported iOS device o… (
ac75b8f 
#289)

fix(cloud): show notices before rejecting an unsupported iOS device or version

The iOS device/version check ran before the DB-driven notices were
rendered, while the Android check ran after them (both date from the
initial commit). So a run that pinned a removed iOS device or version was
rejected without the notice that explains the removal: on 2 Nov 2026 the
removed-ios-17-2026-11-02 and removed-ios-devices-2026-11-02 notices never
showed in the CLI, only the bare "not supported" error.

The iOS check now runs right after the notices, next to the Android one.
Nothing between the two reads the validation result, and the notice
context uses the raw flags, so only the output order changes. Checked
against dev: --ios-device iphone-15 and --ios-device iphone-14
--ios-version 17 now print their removed notice, then the same error.

The MCP tool (dcd_run_cloud_test) renders no notices, so it is unchanged.
@finalerock44
fix(device): keep iOS 17, iPhone 16 Pro and iPhone 16 Pro Max in the … (
e8bf432 
#290)

fix(device): keep iOS 17, iPhone 16 Pro and iPhone 16 Pro Max in the help text

iOS 17, iphone-16-pro and iphone-16-pro-max stay supported until a later
removal, so the --ios-device and --ios-version help text lists them
again. iphone-15, iphone-16-plus and ipad-pro-6th-gen stay removed, and
the default mirror stays iphone-16 / iOS 26.

The validation test fixture gives iphone-14 iOS 17 and 18 again, as the
API does; a device-only iphone-14 request still fails because iOS 26 is
not offered, and its message now lists 17, 18.
@dependabot
chore: bump eslint-plugin-unicorn from 78.0.0 to 79.0.0 (#292)
304a323 
Bumps [eslint-plugin-unicorn](https://github.com/sindresorhus/eslint-plugin-unicorn) from 78.0.0 to 79.0.0.
- [Release notes](https://github.com/sindresorhus/eslint-plugin-unicorn/releases)
- [Commits](sindresorhus/eslint-plugin-unicorn@v78.0.0...v79.0.0)

---
updated-dependencies:
- dependency-name: eslint-plugin-unicorn
  dependency-version: 79.0.0
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
@dependabot
deps: bump the minor-and-patch group across 1 directory with 4 updates (
2002ad3 
#291)

Bumps the minor-and-patch group with 4 updates in the / directory: [@modelcontextprotocol/sdk](https://github.com/modelcontextprotocol/typescript-sdk), [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node), [eslint](https://github.com/eslint/eslint) and [typescript-eslint](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/typescript-eslint).


Updates `@modelcontextprotocol/sdk` from 1.32.1 to 1.32.2
- [Release notes](https://github.com/modelcontextprotocol/typescript-sdk/releases)
- [Commits](modelcontextprotocol/typescript-sdk@1.32.1...1.32.2)

Updates `@types/node` from 26.6.5 to 26.6.6
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

Updates `eslint` from 10.13.0 to 10.14.0
- [Release notes](https://github.com/eslint/eslint/releases)
- [Commits](eslint/eslint@v10.13.0...v10.14.0)

Updates `typescript-eslint` from 8.72.0 to 8.72.1
- [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases)
- [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/typescript-eslint/CHANGELOG.md)
- [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.72.1/packages/typescript-eslint)

---
updated-dependencies:
- dependency-name: "@modelcontextprotocol/sdk"
  dependency-version: 1.32.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: "@types/node"
  dependency-version: 26.6.6
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: eslint
  dependency-version: 10.14.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: typescript-eslint
  dependency-version: 8.72.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
@finalerock44
Merge remote-tracking branch 'origin/production' into promote/cli-5.11.1
71942a9
@finalerock44
chore: pin the 5.11.1 promotion
3b7bcf3 
Release-As: 5.11.1
@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.

This is a dev → production promotion. It carries a separate Release-As: 5.11.1 pin commit, as CLAUDE.md requires, and leaves the package.json version line unchanged. The source changes all come from PRs that were already merged into dev: #284, #285, #287, #288, #289, #290, #291 and #292. I checked these in particular:

  • Moving validateiOSDevice below renderNotices in cloud.ts only changes the order of the output. The notices read the raw flags, and nothing between the old and new call sites reads the validation result.
  • The new iOS default (iphone-16 / 26) matches the updated unit fixtures and their messages.

🤖 Generated with Claude Code

@finalerock44
finalerock44 merged commit e4dbf01 into production Nov 2, 2026
6 checks passed
@finalerock44
finalerock44 deleted the promote/cli-5.11.1 branch November 2, 2026 18:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@finalerock44 finalerock44

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@finalerock44 @riglar