autotel-cli 0.18.0 → 0.18.1

package/dist/index.js

@@ -1681,12 +1681,12 @@ const drizzle = {
 //#endregion
 //#region src/presets/plugins/sentry.ts
 /**
-* Sentry preset — wires Sentry as the OTLP destination + error linker.
+* Sentry preset — wires Sentry as the OTLP destination.
 *
-* Uses `sentryOtlpConfig(DSN)` to build endpoint/headers from the user's DSN
-* and `linkSentryErrors(Sentry)` to thread captured errors onto the active
-* trace context. Sentry's own OpenTelemetry setup is skipped
-* (`skipOpenTelemetrySetup: true`) — autotel owns the OTel side.
+* Uses `sentryOtlpConfig(DSN)` to build endpoint/headers from the user's DSN.
+* Sentry's own OpenTelemetry setup is skipped (`skipOpenTelemetrySetup: true`)
+* — autotel owns the OTel side. Sentry still links captured errors to the
+* active span itself, so nothing here does that.
 */
 const sentry = {
 	name: "Sentry",
@@ -1713,19 +1713,18 @@ const sentry = {
 		default: "* as Sentry"
 	}, {
 		source: "autotel-sentry",
-		specifiers: ["sentryOtlpConfig", "linkSentryErrors"]
+		specifiers: ["sentryOtlpConfig"]
 	}],
 	configBlock: {
 		type: "plugin",
 		code: `// Sentry OTLP setup
 const sentryConfig = sentryOtlpConfig(process.env.SENTRY_DSN!);
-Sentry.init({ dsn: sentryConfig.dsn, skipOpenTelemetrySetup: true });
-linkSentryErrors(Sentry);`,
+Sentry.init({ dsn: sentryConfig.dsn, skipOpenTelemetrySetup: true });`,
 		section: "PLUGIN_INIT"
 	},
 	nextSteps: [
 		"Set SENTRY_DSN in .env (from Sentry → Settings → Projects → Client Keys)",
-		"Captured Sentry errors will now be linked to active OTel traces",
+		"Captured Sentry errors are linked to the active OTel trace by @sentry/node itself",
 		"Pass sentryConfig.endpoint and sentryConfig.headers to init() if you want Sentry as the trace backend"
 	]
 };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "autotel-cli",
-  "version": "0.18.0",
+  "version": "0.18.1",
   "description": "CLI for autotel - setup wizard, diagnostics, and incremental features",
   "type": "module",
   "bin": {