Skip to content

DO NOT MERGE: canary for build-ios (unfixed Courier_iOS 5.9.0 bump) - #73

Closed
mikemilla wants to merge 2 commits into
mainfrom
ci/ios-build-canary-5.9.0
Closed

mikemilla wants to merge 2 commits into
mainfrom
ci/ios-build-canary-5.9.0

Conversation

@mikemilla

@mikemilla mikemilla commented Oct 1, 2026 •

Copy link
Copy Markdown
Collaborator

Throwaway canary for #72. Main now has the 5.9.0 bump and the putUserToken fix (#68), so this branch is #72 plus a commit that puts courierDevice ?? CourierDevice() back, to confirm build-ios goes red. I will close it and delete the branch once it does.

🤖 Generated with Claude Code

mikemilla and others added 2 commits October 1, 2026 12:23
Nothing in CI compiled the Swift bridge in ios/, so the Courier_iOS 5.9.0
bump (#68) went green while putUserToken no longer compiled. The new
build-ios job runs on macos-15, resolves Courier_iOS from the podspec pin,
and builds example-085 for the iOS Simulator with signing disabled.

The example Podfile also pinned Courier_iOS to git tag 5.8.3, which
overrode the podspec pin; drop it so the build uses the pinned version.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mikemilla
mikemilla force-pushed the ci/ios-build-canary-5.9.0 branch from facad03 to e5018c7 Compare October 1, 2026 19:25
@mikemilla

Copy link
Copy Markdown
Collaborator Author

Canary result: build-ios failed as expected with CourierClientMethodHandler-style main-actor error at ios/CourierClientModule.swift:75:46: error: call to main actor-isolated initializer ... in a synchronous nonisolated context (Courier_iOS 5.9.0 pinned and resolved). lint/test/build-library stayed green, which is the gap #72 closes. Closing.

@mikemilla mikemilla closed this Oct 1, 2026
@mikemilla
mikemilla deleted the ci/ios-build-canary-5.9.0 branch October 1, 2026 19:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant