Skip to content

fix(security): SEC-619 raise minimum deployment target to iOS 17#18

Open
juwoncube wants to merge 1 commit into
release/v3.1.0from
release/v3.1.1
Open

fix(security): SEC-619 raise minimum deployment target to iOS 17#18
juwoncube wants to merge 1 commit into
release/v3.1.0from
release/v3.1.1

Conversation

@juwoncube

Copy link
Copy Markdown

Why

Pen test of the Blood iOS app flagged embedded frameworks declaring end-of-life minimum OS versions (Jira: SEC-619). This raises Baymax's minimum deployment target to iOS 17.0, in line with the other 3SC frameworks being updated under the same ticket.

What changed

  • Baymax.xcodeproj: IPHONEOS_DEPLOYMENT_TARGET 14.0 → 17.0 (framework + tests, Debug/Release)
  • Example Project: IPHONEOS_DEPLOYMENT_TARGET 14.7/13.0 → 17.0
  • Package.swift: .iOS(.v14).iOS(.v17); swift-tools-version 5.7 → 5.9 (required for the .v17 platform constant)
  • MARKETING_VERSION 2.0.0 → 3.1.1 (was stale relative to the v3.x release branches)

No Cartfile, xcconfig, or podspec in this repo. No source changes were needed.

Build / test results

  • xcodebuild clean build (scheme Baymax, generic/platform=iOS): succeeded
  • xcodebuild test (scheme BaymaxTests, iPhone 17 simulator): succeeded — note the test target currently contains 0 tests
  • swift package dump-package: manifest valid

New warnings

None — the clean build after the bump produced zero compiler/deprecation warnings.

Note for consumers

Apps embedding this version must target iOS ≥ 17.0.

Pen-test finding SEC-619 flags embedded frameworks declaring EOL minimum
iOS versions. Raise IPHONEOS_DEPLOYMENT_TARGET and the SPM platform
requirement to iOS 17.0, and bump MARKETING_VERSION to 3.1.1.

- Baymax.xcodeproj: IPHONEOS_DEPLOYMENT_TARGET 14.0 -> 17.0 (all configs)
- Example Project: IPHONEOS_DEPLOYMENT_TARGET 14.7/13.0 -> 17.0
- Package.swift: .iOS(.v14) -> .iOS(.v17); swift-tools-version 5.7 -> 5.9
  (required for the .v17 platform constant)
- MARKETING_VERSION 2.0.0 -> 3.1.1
@juwoncube juwoncube changed the base branch from master to release/v3.1.0 June 3, 2026 17:25
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