meta(changelog): Update changelog for 7.51.1

Author: AbhiPrasad

CHANGELOG.md

@@ -4,6 +4,25 @@
 
 - "You miss 100 percent of the chances you don't take. — Wayne Gretzky" — Michael Scott
 
+## 7.51.1
+
+- feat(replay): Add event to capture options on checkouts (#8011)
+- feat(replay): Improve click target detection (#8026)
+- fix(node): Make sure we use same ID for checkIns (#8050)
+- fix(replay: Keep session active on key press (#8037)
+- fix(replay): Move error sampling to before send  (#8057)
+- fix(sveltekit): Wrap `load` when typed explicitly (#8049)
+
+**Replay `rrweb` changes:**
+
+`@sentry-internal/rrweb` was updated from 1.106.0 to 1.108.0:
+
+- fix: Fix some input masking (esp for radio buttons) ([#85](https://github.com/getsentry/rrweb/pull/85))
+- fix: Unescaped `:` in CSS rule from Safari ([#86](https://github.com/getsentry/rrweb/pull/86))
+- feat: Define custom elements (web components) ([#87](https://github.com/getsentry/rrweb/pull/87))
+
+Work in this release contributed by @sreetamdas. Thank you for your contribution!
+
 ## 7.51.0
 
 ### Important Changes
@@ -26,30 +45,40 @@ Note that `@sentry/angular` _does not_ support Angular 16.
 
 - **feat(node): Add ability to send cron monitor check ins (#8039)**
 
+**Note: This release contains a bug with generating cron monitors. We recommend you upgrade the JS SDK to 7.51.1 or above to use cron monitoring functionality**
+
 This release adds [Sentry cron monitoring](https://docs.sentry.io/product/crons/) support to the Node SDK.
 
-To monitor your cron jobs, send check-ins everytime you execute your cron jobs to Sentry. You can do this with the `captureCheckIn` method exported from the SDK. First you must send an `in_progress`, checkin, then you can send one with status `ok` or `error` based on what happened with your cron job.
+Check-in monitoring allows you to track a job's progress by completing two check-ins: one at the start of your job and another at the end of your job. This two-step process allows Sentry to notify you if your job didn't start when expected (missed) or if it exceeded its maximum runtime (failed).
 
 ```ts
 const Sentry = require('@sentry/node');
 
-// ...
-
-Sentry.captureCheckIn({
-  // make sure this is the same slug as what you set up your
-  // Sentry cron monitor with.
-  monitorSlug: 'dailyEmail',
+// 🟡 Notify Sentry your job is running:
+const checkInId = Sentry.captureCheckIn({
+  monitorSlug: '<monitor-slug>',
   status: 'in_progress',
 });
 
-const startTime = timeInSeconds();
-
-runTask();
+// Execute your scheduled task here...
 
+// 🟢 Notify Sentry your job has completed successfully:
 Sentry.captureCheckIn({
-  monitorSlug: 'dailyEmail',
+  // make sure you pass in the checkInId generated by the first call to captureCheckIn
+  checkInId,
+  monitorSlug: '<monitor-slug>',
   status: 'ok',
-  duration: timeInSeconds() - startTime,
+});
+```
+
+If your job execution fails, you can notify Sentry about the failure:
+
+```javascript
+// 🔴 Notify Sentry your job has failed:
+Sentry.captureCheckIn({
+  checkInId,
+  monitorSlug: '<monitor-slug>',
+  status: 'error',
 });
 ```