fix: remove CF middleware and redirect users to migrated sites

[MayankBansal12]

• fix: add CF function for edge level deprecation (fix: add CF function for edge level deprecation #641)
• chore: Update README to add deprecation notice (chore: Update README to add deprecation notice #645)
• fix: remove CF middleware

Date: 22-01-2026

Developer Name: @MayankBansal12

---

Issue Ticket Number

• #640
  (revert CF function and redirect users to migrated pages)

Description

• Remove CF middleware which was previously displaying a static message
• Redirect users to migrated pages

Documentation Updated?

• Yes
• No

Under Feature Flag

• Yes
• No

Database Changes

• Yes
• No

Breaking Changes

• Yes
• No

Development Tested?

• Yes
• No

Screenshots

Screenshot 1

Test Coverage

Screenshot 1

Additional Notes

[netlify]

✅ Deploy Preview for staging-my ready!

Name	Link
🔨 Latest commit	feaf589
🔍 Latest deploy log	https://app.netlify.com/projects/staging-my/deploys/69712fcd54be37000923cbf8
😎 Deploy Preview	https://deploy-preview-646--staging-my.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Summary by CodeRabbit

• Chores
  • Removed legacy middleware configuration to streamline the application.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

Walkthrough

The onRequest middleware function was removed from functions/_middleware.js. This function previously checked a DEPRECATED environment variable to conditionally return a 410 deprecation response or allow request continuation via next().

Changes

Cohort / File(s)	Change Summary
Middleware Removal functions/_middleware.js	Removed exported onRequest(context) middleware function that handled deprecation status checking and returned 410 responses for deprecated routes

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• fix: add CF function for edge level deprecation #641: Directly related — adds back the onRequest(context) middleware with deprecation logic that was removed in this PR

Suggested reviewers

• AnujChhikara
• iamitprakash

Poem

🐰 The middleware hops away,
No more deprecated delay,
Clean and simple, light and free,
Request flows with glee!
✨ Simplicity's the way!

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title directly addresses the main change: removal of CF middleware, aligning with the changeset that removes the middleware function.
Description check	✅ Passed	The description is related to the changeset, mentioning removal of CF middleware and referencing issue #640, though it also mentions redirect functionality not evident in the code changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

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.}