fix(unsubscribe): unsubscribe page missing suspense boundary

[icecrasher321]

Description

Seeing this error on Railway deployment

This PR should fix that by wrapping it in the suspense component.

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added tests that prove my fix is effective or that my feature works
• All tests pass locally and in CI (bun run test)
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules
• I have updated version numbers as needed (if needed)
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

Security Considerations:

• My changes do not introduce any new security vulnerabilities
• I have considered the security implications of my changes

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
sim	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 14, 2025 10:43pm

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
docs	⬜️ Skipped (Inspect)			Jul 14, 2025 10:43pm

[greptile-apps]

Greptile Summary

This PR addresses a production error in the unsubscribe page by implementing a Suspense boundary around the UnsubscribeContent component. The changes follow a pattern we already use in other authentication-related pages (like SignupPage and ResetPasswordPage) where the main content is wrapped in a Suspense component to handle loading states properly.

The change involves:

1. Splitting the UnsubscribePage into a container and content component
2. Adding a Suspense boundary with a loading fallback
3. Moving the original content into UnsubscribeContent component

This change is particularly important for the production environment on Railway where the missing Suspense boundary was causing errors.

Confidence score: 4/5

1. This PR is safe to merge as it follows established patterns in the codebase
2. The high score is due to the straightforward nature of the fix and its consistency with existing auth page implementations
3. Files that need attention:
   • apps/sim/app/unsubscribe/page.tsx - verify the loading fallback matches other auth pages for consistency

_{1 file reviewed, no comments
Edit PR Review Bot Settings | Greptile}

[delve-auditor]

✅ No security or compliance issues detected. Reviewed everything up to 2ad3e35.

Security Overview

• 🔎 Scanned files: 1 changed file(s)

Detected Code Changes

Change Type	Relevant files
Bug Fix	► page.tsx Add missing Suspense boundary to unsubscribe page Split component into UnsubscribeContent and UnsubscribePage

Reply to this PR with @delve-auditor followed by a description of what change you want and we'll auto-submit a change to this PR to implement it.