From ef1dd9484122a007374f94a4a112ba4095cc9414 Mon Sep 17 00:00:00 2001
From: finalerock44 <77282157+finalerock44@users.noreply.github.com>
Date: Mon, 24 Aug 2026 11:30:22 +0100
Subject: [PATCH] chore: release the iOS 16 removal as 5.4.0, not 6.0.0
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

I wrote fcfa524f as `feat!: remove iOS 16`. The `!` is what made
release-please propose 6.0.0-beta.2 in #122. That marker was wrong.

Dropping '16' from EiOSVersions does not break anything that still worked:
the platform removed iOS 16 server-side on 2026-08-24, so `--ios-version 16`
already fails with a 400 on every existing 5.x CLI. The enum change only moves
that same rejection client-side, with a better message. Nobody loses a working
capability, which is the bar for a major.

`Release-As: 5.4.0-beta.0` re-pins the pending beta release PR. Same mechanism
this repo already used to hold #120 at 5.3.1 rather than let it roll.

Minor rather than patch because the supported-version set changed, which is a
behaviour change worth a minor even though the trigger was a removal.

⚠️ THIS ONLY FIXES THE BETA LINE. fcfa524f still carries `!` in history, and
the production line reads the same commits — so when dev promotes to
production, release-please will propose 6.0.0 on the stable line for exactly
the same reason. That promotion needs its own `Release-As: 5.4.0` commit, or
fcfa524f reworded before it lands there. production does not have the commit
yet, so there is still a clean window to do the latter.

Release-As: 5.4.0-beta.0