{"items":[{"id":"4a65acd3-0fb3-4888-941d-79978f79c0f9","type":"push","org":"lws803","repo":"GigaChadGPT","title":"Added an announcement banner to the chat interface to promote Beloga’s research-focused experience.","summary":"This change introduces a small `AnnouncementBanner` component and mounts it above the fixed chat input in `ChatInterface`. The banner links users to Beloga with lightweight theme-aware styling, making the promotion visible without changing chat behavior or message flow. In practice, users now see a clear in-product callout for the more research-friendly use case.","url":"https://nomit.dev/lws803/GigaChadGPT/status/859baca7f47428bc0d600815ed194c24eb2c97cd3919b356ca8459db70ad8ca6","author":"lws803","contributors":["lws803"],"updated_at":"2023-09-16T15:48:29+00:00"},{"id":"e4494bdf-100d-4a74-8c0f-3de0a029a2c2","type":"push","org":"lws803","repo":"GigaChadGPT","title":"Refactored LogRocket initialization into an auth-aware analytics component so session replay can be configured per environment and tied to signed-in users.","summary":"This change moves LogRocket setup out of the global app bootstrap and into a dedicated `LogRocketAnalytics` component that reads the client key from `NEXT_PUBLIC_LOG_ROCKET_KEY` instead of hardcoding it. It also identifies authenticated users with their UID and email, which should make debugging and session tracing much more useful once someone signs in. Alongside that, Firebase emulator config was added for the default project, making local auth development easier. Practical effect: observability is cleaner, safer to configure across environments, and more actionable during debugging.","url":"https://nomit.dev/lws803/GigaChadGPT/status/bfc24e1e3f9e90bf7250764c5672224386dfa9b9d8fe0f03812c4de8e80fe0e8","author":"lws803","contributors":["lws803"],"updated_at":"2023-05-13T18:57:11+00:00"},{"id":"75a9902c-da75-4668-bbe4-af673c239c75","type":"push","org":"lws803","repo":"GigaChadGPT","title":"Switched API error reporting to use @sentry/node so server-side exceptions are captured correctly in shared handlers.","summary":"This change updates the shared API handler to import Sentry from `@sentry/node` instead of `@sentry/nextjs`, which is a better fit for server-side error capture in this code path. The previous import could lead to exceptions not being reported as expected from backend handlers, making production debugging harder. With this fix, errors raised through the shared handler should now reach Sentry more reliably, improving observability when API requests fail.","url":"https://nomit.dev/lws803/GigaChadGPT/status/3ff322cb6f2a1b286eca20ba3b9f02283b4b2844cfcdfae6318f1e1a275d0259","author":"lws803","contributors":["lws803"],"updated_at":"2023-04-05T22:00:05+00:00"},{"id":"5e8188cf-1caa-468a-a946-f0dcc7d3304f","type":"push","org":"lws803","repo":"GigaChadGPT","title":"Fixed Sentry exception capture in the shared API handler by correcting the Next.js Sentry import.","summary":"This change updates the shared API handler to import `@sentry/nextjs` as a namespace instead of a default export, which fixes exception reporting when errors are captured. It’s a small but important runtime fix in central error-handling code, so failed requests should now be logged to Sentry reliably again. The practical effect is better visibility into production API failures.","url":"https://nomit.dev/lws803/GigaChadGPT/status/20376522ee1c5bf2c62ebb310ff93adb648a8f955bfdf351daed7a4218fed58c","author":"lws803","contributors":["lws803"],"updated_at":"2023-04-05T21:59:19+00:00"},{"id":"41a1cd41-06ce-48ac-a916-c6fd80f38ddd","type":"push","org":"lws803","repo":"GigaChadGPT","title":"Capture unhandled API handler exceptions in Sentry so server-side failures are visible instead of silently returning 500s","summary":"The shared API error handler now reports unexpected exceptions to Sentry before returning a generic internal server error response. Validation and auth-related cases still keep their existing client-facing behavior, but anything that falls through to the 500 path will now be captured for debugging and monitoring. The practical effect is better visibility into production backend failures with no change to the public API contract.","url":"https://nomit.dev/lws803/GigaChadGPT/status/f05483954c4cb3e54ae944c156b64975c12e28e7258c2e8e911f6e86b7d2f039","author":"lws803","contributors":["lws803"],"updated_at":"2023-04-05T20:47:06+00:00"}],"pagination":{"offset":0,"limit":5,"has_more":true}}