Add ci-ios PR pipeline

[kieran-osgood-shopify]

Part of the macOS CI speed-up
Epic
Issue

What

Adds a new ci-ios pipeline in bitrise
ci-ios will be non-blocking until stable and will run in parallel to the github actions
ci-ios will run all macos xcode jobs to improve speed

Why

Bitrise reports one status per pipeline.
Reusing the e2e pipeline would tie the merge gate to the BrowserStack device flake that e2e/BITRISE.md:53 deliberately keeps non-blocking.

How it works

1. ci-ios-plan runs on the cheap default Linux stack. It derives the changed files, maps them through e2e/config/ios_ci.yml, and publishes one CI_IOS_* flag per job with share-pipeline-variable@1. Every macOS machine his pipeline boots is decided here, so a change needing no iOS job costs one short Linux build.
2. Each job workflow carries a run_if on its own flag.
3. ci-ios-report has no run_if and should_always_run: workflow. It posts the Checkout Kit iOS check run on every build, including one where the plan selected nothing.

The trigger_map entry for ci-ios has no changed_files filter, on purpose.
A required check that never posts leaves a pull request permanently unmergeable, so the trigger is unconditional and the cheap Linux gate decides the rest.

Files

File	Role
e2e/config/ios_ci.yml	job → changed-file-filter mapping
e2e/lib/ios_ci_run_plan.rb	selection, flag names, validation
e2e/lib/ios_ci_reporter.rb	the Checkout Kit iOS check run
e2e/scripts/ios_ci_run_plan	validate / bitrise-env / selected-jobs / assert-pipeline-coverage
e2e/scripts/report_ios_ci_results	Bitrise entry point for the reporter
e2e/scripts/bitrise_ci_helpers	changed-files, branch config, GitHub token — shared with the E2E gate

Testing

It wont run on this pr until it hits main so i manually dispatched:

   curl -X POST \
     'https://api.bitrise.io/v0.1/apps/f51f9054-053e-40f1-81e9-ae727567ae76/builds' \
     -H 'accept: application/json' \
     -H "Authorization: ${BITRISE_PAT}" \
     -H 'Content-Type: application/json' \
     -d '{
       "hook_info": {
         "type": "bitrise"
       },
       "build_params": {
         "branch": "kieran-osgood/macos-ci-4-bitrise-gate",
         "branch_dest": "main",
         "branch_repo_owner": "Shopify",
         "branch_dest_repo_owner": "Shopify",
         "commit_hash": "4fd7ce0dd2c8c18c98a3e9fab71a93cd46a46fab",
         "pull_request_id": 635,
         "pipeline_id": "ci-ios"
       }
     }'

https://app.bitrise.io/app/f51f9054-053e-40f1-81e9-ae727567ae76/pipelines/8c1b9e60-6905-43e9-9387-17857c34df2c

---

Before you merge

Important

• I've added tests to support my implementation
• I have read and agree with the Contribution Guidelines
• I have read and agree with the Code of Conduct
• I've updated the relevant platform README (platforms/swift/README.md and/or platforms/android/README.md)

---

Releasing a new Swift version?

• I have bumped the version in ShopifyCheckoutKit.podspec
• I have bumped the version in platforms/swift/Sources/ShopifyCheckoutKit/ShopifyCheckoutKit.swift
• I have updated the SwiftPM/CocoaPods version snippets in platforms/swift/README.md (major version only)

Releasing a new Embedded Checkout Protocol version?

• I have bumped embeddedCheckoutProtocolAndroid in platforms/android/gradle/libs.versions.toml
• I have updated protocol/languages/kotlin/embedded-checkout-protocol/api/embedded-checkout-protocol.api if the public API changed

Releasing a new Android version?

• I have bumped checkoutKitAndroid in platforms/android/gradle/libs.versions.toml
• I have updated the Gradle/Maven version snippets in platforms/android/README.md

Tip

See the Contributing documentation for the full release process per platform.

[kieran-osgood-shopify]

• Document the ci-ios pipeline and fix the stale Ruby pin in BITRISE.md #639
• Cache React Native iOS builds with sccache #638
• Cache DerivedData on the macOS build jobs and stop cleaning it away #637
• Port the remaining three macOS jobs to the Bitrise ci-ios pipeline #636
• Add ci-ios PR pipeline #635 👈 (View in Graphite)
• Increase CI script portability around xcbeautify #634
• Make the CocoaPods spec repo refresh opt-in on CI #633
• Drop the duplicate Swift compile in build_and_test_samples #632
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

Web — Coverage Report

Lines	Statements	Branches	Functions
	94.62% (299/316)	81.72% (152/186)	98.71% (77/78)

[github-actions]

React Native — Coverage Report

Lines	Statements	Branches	Functions
	90.97% (363/399)	87.29% (213/244)	100% (92/92)

[github-actions]

Package Size

Platform	Artifact	Base	Head	Delta
Web	npm tarball	70.6 KiB	70.6 KiB	0 B
React Native	npm tarball	107.3 KiB	107.3 KiB	0 B
Android	release AAR	279.8 KiB	279.8 KiB	0 B

Web file breakdown

File	Base	Head	Delta
dist/index.js.map	192.2 KiB	192.2 KiB	0 B
dist/index.d.ts	44.9 KiB	44.9 KiB	0 B
dist/custom-elements.json	44.0 KiB	44.0 KiB	0 B
dist/index.js	31.5 KiB	31.5 KiB	0 B
README.md	19.0 KiB	19.0 KiB	0 B
package.json	2.8 KiB	2.8 KiB	0 B
LICENSE	1.1 KiB	1.1 KiB	0 B

React Native file breakdown

File	Base	Head	Delta
node_modules/@shopify/checkout-kit-protocol/src/generated/Models.ts	85.4 KiB	85.4 KiB	0 B
node_modules/@shopify/checkout-kit-protocol/src/generated/Models.d.ts	53.0 KiB	53.0 KiB	0 B
android/src/main/java/com/shopify/reactnative/checkoutkit/ShopifyCheckoutKitModule.java	16.0 KiB	16.0 KiB	0 B
ios/ShopifyCheckoutKit.swift	15.9 KiB	15.9 KiB	0 B
ios/AcceleratedCheckoutButtons.swift	14.1 KiB	14.1 KiB	0 B
src/components/AcceleratedCheckoutButtons.tsx	13.0 KiB	13.0 KiB	0 B
src/index.ts	12.7 KiB	12.7 KiB	0 B
lib/commonjs/index.js	12.4 KiB	12.4 KiB	0 B
lib/commonjs/components/AcceleratedCheckoutButtons.js	11.4 KiB	11.4 KiB	0 B
src/index.d.ts	11.1 KiB	11.1 KiB	0 B
lib/commonjs/components/AcceleratedCheckoutButtons.js.map	10.4 KiB	10.4 KiB	0 B
lib/module/index.js	10.4 KiB	10.4 KiB	0 B
lib/module/components/AcceleratedCheckoutButtons.js	10.2 KiB	10.2 KiB	0 B
node_modules/@shopify/checkout-kit-protocol/src/generated/ProtocolNotifications.ts	9.5 KiB	9.5 KiB	0 B
lib/module/components/AcceleratedCheckoutButtons.js.map	9.1 KiB	9.1 KiB	0 B
lib/module/index.js.map	8.1 KiB	8.1 KiB	0 B
src/present-dispatcher.ts	8.0 KiB	8.0 KiB	0 B
lib/commonjs/index.js.map	7.9 KiB	7.9 KiB	0 B
node_modules/@shopify/checkout-kit-protocol/src/generated/ProtocolNotifications.d.ts	7.6 KiB	7.6 KiB	0 B
node_modules/@shopify/checkout-kit-protocol/src/generated/ProtocolRenameMap.ts	7.2 KiB	7.2 KiB	0 B
…and 117 smaller files

Android file breakdown

File	Base	Head	Delta
classes.jar	295.6 KiB	295.6 KiB	0 B
res/layout/checkout_view_content.xml	2.6 KiB	2.6 KiB	0 B
res/layout/checkout_sheet_content.xml	2.0 KiB	2.0 KiB	0 B
res/values/values.xml	1.3 KiB	1.3 KiB	0 B
R.txt	1.2 KiB	1.2 KiB	0 B
AndroidManifest.xml	922 B	922 B	0 B
proguard.txt	798 B	798 B	0 B
res/drawable/close.xml	431 B	431 B	0 B
res/menu/checkout_menu.xml	354 B	354 B	0 B
META-INF/com/android/build/gradle/aar-metadata.properties	157 B	157 B	0 B

Measured from the PR base SHA and PR head SHA. The file breakdown shows uncompressed sizes within each package artifact, so individual files do not sum to the compressed artifact total. This comment reports package artifact sizes only; it is not a final app binary-size report.

[bitrise]

Install this build

Open Tophat, select your target device, then click Install. Links open on the Mac running Tophat.

SDK	Install
React Native	Install with Tophat
Swift	Install with Tophat
Kotlin	Install with Tophat

Checkout Kit E2E results

Status	Suite	Target	Platform	OS version tag	Device
✅	react-native-ios	react-native	ios	latest	iPhone 15 iOS 27 Beta
✅	react-native-android	react-native	android	latest	Google Pixel 9 Android 17.0
✅	kotlin-android	kotlin	android	latest	Google Pixel 9 Android 17.0
✅	swift-ios	swift	ios	latest	iPhone 15 iOS 27 Beta

[markmur]

[P1] This fails open when BITRISEIO_FINISHED_WORKFLOWS is missing, malformed, or omits an expected stage. BitrisePipelineStages.parse then yields an empty roster, problem_stages is empty, and the required check reports success—even marking a selected job as passed. I reproduced that with a nil roster. Could we require every expected stage to be present with an explicit successful status, and add tests for invalid JSON plus entirely absent plan/job entries?

[kieran-osgood-shopify]

This should be resolved now added guards for succeeded and hyandling empty arrays - added tests covering it too

[markmur]

[P2] The shared stage parser treats succeeded_with_abort as success. That may be acceptable for the existing non-blocking E2E report, but for a required iOS test gate an aborted selected workflow should not count as evidence that its tests passed. Could this reporter require the literal succeeded status, or make the success policy injectable, with coverage for the aborted status?

[kieran-osgood-shopify]

This should also be covered now