Notify the Unity package when Android releases

[ianrumac]

Summary

• Adds superwall/Superwall-Unity to the wrapper dispatch list, so an Android release tells Unity to open a bump PR the way Flutter, Expo, and KMP already are.
• Depends on Open a PR when a native SDK releases Superwall-Unity#12 landing native-sdk-bump.yml on main. Until then a dispatch to Unity fails, and the other wrappers are still notified.

Test plan

• Confirm WRAPPER_DISPATCH_TOKEN has Contents read & write on superwall/Superwall-Unity. The dispatch API checks that permission, and a token that cannot see the repo fails this job.
• After the Unity workflow is on main, run this workflow by hand for a version Unity does not already pin and confirm the Unity bump workflow starts.

[pullfrog]

✅ No new issues found.

Reviewed changes

I reviewed the one-commit change that adds Unity to the list of wrappers notified on an Android release.

• Unity added to WRAPPER_REPOS: notify-wrappers.yml now sends native-sdk-release to superwall/Superwall-Unity along with Flutter, Expo and KMP, through the same per-repo loop. One repo failing does not stop the others.
• Comment updates: the header in notify-wrappers.yml and the notify_wrappers job comment in build+test+deploy.yml now list Unity.

ℹ️ Until Superwall-Unity#12 lands, the Unity dispatch is silently ignored rather than failing

The description says a dispatch to Unity fails until native-sdk-bump.yml is on Unity's main. That is not quite right. POST /repos/{owner}/{repo}/dispatches returns 204 whether or not any workflow listens for the event, so the job stays green and nothing happens on the Unity side. This means the two PRs can merge in either order. The only thing that would turn this job red is WRAPPER_DISPATCH_TOKEN lacking access to Superwall-Unity (a 404 from gh api), which the test plan already covers. Note that a version released before #12 lands will not start a Unity bump on its own. You would re-send it with notify_wrappers_only.

  ^{｜ View workflow run ｜ Using claude-opus-5.5 ｜ 𝕏}