Mailme Library Migration Doc

MAILME_LIBRARY_MIGRATION.md

@@ -0,0 +1,35 @@
+# Mailme Library Migration Implementation Note
+
+## Issue Reference
+GitHub Issue: https://github.com/supabase/supabase/issues/27950
+
+## Summary
+Replace `go-gomail/gomail` with `wneessen/go-mail` in the mailme project.
+
+## Current Status
+The `mailme` project is referenced in the Supabase open-source ecosystem but is maintained as a separate repository. This main Supabase repository does not contain the Go code that needs to be updated.
+
+## Required Actions
+1. The migration needs to be implemented in the separate `supabase/mailme` repository
+2. Key changes required:
+   - Update `go.mod` to replace `go-gomail/gomail` dependency with `wneessen/go-mail`
+   - Update import statements throughout the codebase
+   - Adapt code to use the new library's API (differences in method signatures, configuration, etc.)
+   - Update any SMTP configuration and email sending logic
+   - Test email functionality with the new library
+
+## Benefits of Migration
+- Migrate from unmaintained library to actively maintained one
+- Follow modern Go standards and idioms
+- Improved security and performance from active maintenance
+
+## Implementation Guidelines
+1. Review the new library documentation: https://pkg.go.dev/github.com/wneessen/go-mail
+2. Create a feature branch for the migration
+3. Update dependencies in go.mod
+4. Refactor email sending code to use new API
+5. Add comprehensive tests for email functionality
+6. Update documentation if needed
+
+## Next Steps
+This implementation should be done in the `supabase/mailme` repository, not in this main Supabase repository.