chore(release): announce beta + prod releases in Slack from the release scripts

[alichherawalla]

What

Both release scripts now announce the release in Slack after the GitHub release is cut:

• scripts/uat.sh (beta → TestFlight + Play internal) — posts after gh release create, before the notes tempfile is removed.
• scripts/release.sh (production/local) — same step added before its rm -f "$NOTES_FILE".

Both call the existing scripts/notify-slack-release.mjs and are fail-soft (|| true) — a chat post can never fail an already-shipped build.

Why

The Slack announcer only fired from CI (release-ios.yml on workflow_run). Releases cut locally via uat.sh / release.sh posted nothing, so beta ships (which are cut on this machine) never announced. This wires the same notifier into the local path.

Secret handling

The webhook is read from the gitignored .env.keygen — the local secret store that already holds the RevenueCat / Resend / Keygen / Cloudflare tokens — mirroring the SLACK_WEBHOOK_URL repo secret the CI workflows use. It is extracted with a scoped sed for that one key (not a full source), so the other secrets in .env.keygen never enter the script environment. notify-slack-release.mjs no-ops when the webhook is unset, so this is a no-op on any machine without it.

No secrets are committed — .env.keygen, fastlane/.env, and .env* are all confirmed gitignored.

Verification

• notify-slack-release.mjs posted the 0.0.103-beta.3 announcement successfully via this webhook during the live release.
• No native/deps/config changes; scripts-only.

Summary by CodeRabbit

• New Features

  • Added automatic Slack notifications when GitHub releases and beta prereleases are published.
  • Notifications include the product, version, release link, and beta status where applicable.

• Reliability

  • Release and beta build processes continue successfully even if Slack notification delivery fails.

[qodo-code-review]

ⓘ Qodo reviews are paused because your trial has ended. Ask your workspace admin to add credits to resume reviews. Manage billing

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 591396fc-0aac-42a2-814a-691fc9cbf930

📥 Commits

Reviewing files that changed from the base of the PR and between 6477754 and 57913c5.

📒 Files selected for processing (1)

• scripts/release.sh

🚧 Files skipped from review as they are similar to previous changes (1)

• scripts/release.sh

---

📝 Walkthrough

Walkthrough

Release and beta UAT scripts now notify Slack after creating GitHub releases. They resolve the webhook URL, retrieve the release URL, invoke the shared notifier with release metadata, and ignore notification failures.

Changes

Release notifications

Layer / File(s)	Summary
Notify Slack after release creation scripts/release.sh, scripts/uat.sh	Release and beta workflows resolve SLACK_WEBHOOK_URL, fetch the GitHub release URL, invoke notify-slack-release.mjs, and continue when notification fails.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

• off-grid-ai/off-grid-ai-mobile#509: Updates the shared Slack notifier invoked by these release scripts.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is informative but does not follow the required template; it omits Summary, Type of Change, Screenshots, and Checklist sections.	Add the template sections, especially Summary, Type of Change, Screenshots or N/A, Checklist, Related Issues, and Additional Notes for completeness.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: adding Slack release announcements from the release scripts.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/slack-release-notify

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[gitar-bot]

Code Review ✅ Approved

Integrates automatic Slack release notifications into local uat.sh and release.sh scripts. No issues found.

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change the behavior for this request:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[alichherawalla]

Subsumed by #557 — its two commits (Slack release announcements in uat.sh/release.sh) were merged into fix/ios-download-durable-staging. Closing to avoid a double-merge; the changes ship with #557.