v1.41.0

🔧 Improvements

1. New HTTP Error Type: ErrorRecordNotFound

A new standardized error type http.ErrorRecordNotFound has been introduced to gracefully handle scenarios where no records are found in the database.

Example:

return  nil, http.ErrorRecordNotFound{
    Message: "User not found with the given ID",
}

This improves semantic clarity and enables better client-side handling for empty-query results.

2. Improved Cron Job Observability

All cron jobs in GoFr now come with built-in logger and tracing support.

• Logs from scheduled tasks are now clearly visible.

• Each recurring job run is automatically tagged with a unique trace ID, making it easier to trace, debug, and monitor scheduled executions across your system.

This ensures better observability for background tasks without requiring additional instrumentation.

🐛 Fixes

1. Supabase Connection Issue Resolved

Previously, Supabase connections were not initializing correctly in GoFr due to a missing dialect registration. Supabase-backed services will now connect without issues—no manual fixes required.