Summary
We integrate Reaper via Swift Package Manager using exact version v2.0.1. On iOS 26 (Xcode 26), EMGReaper’s startWithHandler: path returns early because only majors 15–18 are allowed, so no observers are registered and the handler never runs.
Current main
main already extends the supported majors to include 26 (see Sources/Reaper/EMGReaper.mm on main). So the runtime fix exists, but there is no tagged release after that change, which forces consumers to depend on main or a raw revision.
Request
Please tag and release a new version (e.g. v2.0.2) that includes the iOS 26 support from main, so SPM users can pin with from: "2.0.2" / exact version instead of a branch.
Why this matters
We need reproducible, reviewable dependency pins in CI and production pipelines; floating on main is risky for us.
Thanks!
Summary
We integrate Reaper via Swift Package Manager using exact version
v2.0.1. On iOS 26 (Xcode 26),EMGReaper’sstartWithHandler:path returns early because only majors 15–18 are allowed, so no observers are registered and the handler never runs.Current
mainmainalready extends the supported majors to include 26 (seeSources/Reaper/EMGReaper.mmonmain). So the runtime fix exists, but there is no tagged release after that change, which forces consumers to depend onmainor a raw revision.Request
Please tag and release a new version (e.g.
v2.0.2) that includes the iOS 26 support frommain, so SPM users can pin withfrom: "2.0.2"/ exact version instead of a branch.Why this matters
We need reproducible, reviewable dependency pins in CI and production pipelines; floating on
mainis risky for us.Thanks!