Why deployment target 18+?

[Janneman84]

I noticed you recently upped the minimal supported iOS version to 18. Is this really necessary?

I mean I cloned your repo, lowered the target and the demo app now runs fine on my iPad Air 2 running iOS 15. Setting it to 12 compiles fine too.

[kostub]

No particular reason to make it iOS 18 other than it is a recent version. I can drop it down to 15 which is the earliest supported iOS by apple right now.

[kostub]

You're right — the iOS 18 floor wasn't justified. The bump in v2.0.0 was a toolchain-cleanup pass, but I never checked whether the library actually needed anything new. Reviewing the source: no @available gates, no SwiftUI/Combine/async-await, only CoreText + CoreGraphics + UIKit/AppKit fundamentals available since iOS 8.

PR #216 lowers the floors to iOS 13 / macOS 10.15. That gets your iPad Air 2 (and the long tail of devices stuck on iOS 13–17) building and running again, without giving up anything on the library side.

I picked iOS 13 rather than 12 because Swift 6's SPM minimum is iOS 12, and the extra year buys nothing meaningful in 2026 install-base terms — but if you'd prefer iOS 12 to match your local test, happy to drop another point.

[Janneman84]

Thanks, it's annoying having an SPM package dictate your deployment target. If I were you I'd just set it low as possible 🙃.