[skill-drift] sentry-nextjs-sdk may need updates

[github-actions]

cc @getsentry/team-javascript-sdks

SDK Changes Detected

The following PRs were merged to getsentry/sentry-javascript in the last 7 days that may affect the sentry-nextjs-sdk skill:

• feat(nextjs): Vercel queue instrumentation sentry-javascript#19799 — feat(nextjs): Vercel queue instrumentation (feat(nextjs): Vercel queue instrumentation sentry-javascript#19799)

Potential Skill Gaps

1. New Feature (Vercel Queues instrumentation): PR #19799 adds automatic OTel messaging span enrichment for Vercel Queues in @sentry/nextjs. Both consumer and producer sides are instrumented with zero config:

   • Consumer: HTTP requests with ce-type: com.vercel.queue.v2beta header are enriched with messaging.system=vercel.queue, messaging.operation.name=process, queue name, and message ID as span attributes.
   • Producer: Outgoing HTTP requests to *.vercel-queue.com are enriched with messaging.system=vercel.queue and messaging.operation.name=send.

   The skill's Phase 2 recommendation matrix covers Vercel Cron monitoring but does not mention Vercel Queues. Apps using Vercel Queues get distributed tracing across queue producer/consumer automatically — this should be noted in the Tracing feature description or as a callout for Vercel Queue users.

Skill Files to Review

• skills/sentry-nextjs-sdk/SKILL.md

Priority

MEDIUM — zero-config new feature; no user action required but the skill should document coverage so users know queue tracing works out of the box.

Generated by SDK Skill Drift Detector · ◷

• expires on Mar 30, 2026, 11:02 PM UTC

[github-actions]

This issue is being closed as outdated. A newer issue has been created: #66

View newer issue

---

This action was performed automatically by the SDK Skill Drift Detector workflow.