fix: add offer-hub-web.vercel.app to CORS origins

[Josue19-08]

📝 Pull Request Title

🛠️ Issue

• Closes #issue-ID

📚 Description

✅ Changes applied

🔍 Evidence/Media (screenshots/videos)

Summary by CodeRabbit

• New Features

  • Enabled access to the backend from an additional web domain, allowing users on that site to interact with the service without cross-origin issues.

• Chores

  • Updated CORS configuration to include a new allowed origin, improving compatibility for deployments accessing the API from that domain.
  • No changes to routes, behaviors, or public interfaces; existing functionality remains unaffected.

[coderabbitai]

Walkthrough

Added https://offer-hub-web.vercel.app to the allowed CORS origins array in backend/src/index.ts. No other logic, routes, or control flow changed.

Changes

Cohort / File(s)	Change Summary
CORS configuration backend/src/index.ts	Added a new allowed CORS origin: https://offer-hub-web.vercel.app. No other modifications.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Feat/improve project #838 — Also modifies the CORS origin whitelist in backend/src/index.ts, indicating similar configuration changes.

Poem

A rabbit hops through headers bright,
Whitelists updated, set just right.
Vercel’s burrow joins the ring,
Preflights pass on feathered wing.
With CORS now calm and origins true,
The hutch approves each request that’s due. 🐇✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title succinctly and accurately describes the primary change by specifying the addition of offer-hub-web.vercel.app to the CORS origins, follows conventional commit style, and is clear enough for anyone scanning the PR history to understand the fix.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/improve-project

---

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 and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

backend/src/index.ts (1)

48-48: Redundant origin entry.

The explicit origin 'https://offer-hub-web.vercel.app' is already matched by the regex pattern on line 49 (/https:\/\/.*\.vercel\.app$/), which covers any Vercel app subdomain. While the code functions correctly, this creates unnecessary duplication.

Consider removing this line to eliminate the redundancy:

-    'https://offer-hub-web.vercel.app',

Alternatively, if you prefer explicit documentation of specific environments, consider adding a comment explaining why both the explicit entry and the regex pattern are maintained.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 806c404 and 8bc6d9e.

📒 Files selected for processing (1)

• backend/src/index.ts (1 hunks)

🔇 Additional comments (1)

backend/src/index.ts (1)

49-49: Verify the scope of the regex pattern.

The regex /https:\/\/.*\.vercel\.app$/ permits requests from any subdomain under vercel.app, including potentially unauthorized preview deployments or unrelated Vercel apps.

If this broad allowance is intentional (e.g., to support dynamic preview URLs), consider documenting this decision. Otherwise, you may want to tighten the pattern to match only your organization's specific Vercel apps:

-    /https:\/\/.*\.vercel\.app$/
+    /https:\/\/offer-hub[^\/]*\.vercel\.app$/

This modified pattern restricts matches to subdomains starting with offer-hub.

[github-actions]

✅ Frontend CI/CD Pipeline Completed Successfully!

• ✅ Linting passed
• ✅ Build completed
• ✅ Security audit passed

Ready for review and deployment! 🚀