Fan out iOS build dispatch to superscript-ios-next#47
Merged
Conversation
Adds a parallel repository_dispatch to the new slim iOS repo while leaving the legacy superscript-ios trigger in place for the migration window. Once Superwall-iOS and any other consumers have moved to superscript-ios-next, the legacy step can be removed.
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
repository_dispatchstep totrigger-supercel-ios.ymlthat notifies the newsuperwall/superscript-ios-nextrepo on every push tomaster.superwall/Superscript-iOSin place so legacy consumers keep getting builds during the migration window.Why
superscript-ioscommits the ~250 MBlibcel.xcframeworkinto git on every release, which has grown its history past 1.2 GB and makes SPM clones painfully slow.superscript-ios-nextdistributes the framework as a GitHub Release asset and uses SPM'sbinaryTarget(url:checksum:), keeping the repo at ~60 KB.This fan-out keeps both repos healthy during the cutover. Once
Superwall-iOSand any other internal consumers move tosuperscript-ios-next, the legacy dispatch step can be deleted.Test plan
master(or wait for the next real release) and confirm bothsuperscript-ios-nextandSuperscript-iOSworkflows firesuperscript-ios-nextproduces a release withlibcel.xcframework.zipattached and rewritesPackage.swiftwith the new URL/checksum🤖 Generated with Claude Code