Trigger Typesense Schema Update Function on Deploy

[kiminkim724]

Summary

• Closes Trigger Typesense Schema Update Function on Deploy  #1978
• Added step to github actions for both prod and dev environments
• Added logging to scheduleUpgradeIfNeeded to check if schema is being updated or not

Checklist

• On the frontend, I've made my strings translate-able.
• If I've added shared components, I've added a storybook story.
• I've made pages responsive and look good on mobile.
• If I've added new Firestore queries, I've added any new required indexes to firestore.indexes.json (Please do not only create indexes through the Firebase Web UI, even though the error messages may reccommend it - indexes created this way may be obliterated by subsequent deploys)

Screenshots

Add some screenshots highlighting your changes.

Known issues

If you've run against limitations or caveats, include them here. Include follow-up issues as well.

Steps to test/reproduce

For each feature or bug fix, create a step by step list for how a reviewer can test it out. E.g.:

1. Make a change to any of the Typesense schemas and push schema update to main
2. Check if the pub/sub function is called and Typesense alias is updated

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
maple-dev	Ready	Preview, Comment	Feb 4, 2026 0:48am

[Mephistic]

LGTM - let's give this a shot.

Note - we will need to test it with a real schema change before we're fully confident, but just ensuring that it doesn't update when it shouldn't is a good step A.