upgrade-otel
Upgrading OpenTelemetry Instrumentations
All upgrades must be free of breaking changes. Read each changelog before proceeding.
1. packages/**
Upgrade in this order:
@opentelemetry/instrumentationto latest. Check changelog:https://github.com/open-telemetry/opentelemetry-js/blob/main/experimental/CHANGELOG.md- All
@opentelemetry/instrumentation-*packages. Check each changelog:https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/packages/instrumentation-{name}/CHANGELOG.md - Third-party instrumentations (currently
@prisma/instrumentation). Check their changelogs.
STOP if any upgrade introduces breaking changes — fail with the reason.
2. dev-packages/**
- If an app depends on
@opentelemetry/instrumentation>=0.200.x, upgrade to latest. - If an app depends on
@opentelemetry/instrumentation-http>=0.200.x, upgrade to latest.
More from getsentry/sentry-javascript
fix-security-vulnerability
Analyze and propose fixes for Dependabot security alerts
12skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
11triage-issue
Triage GitHub issues with codebase research and actionable recommendations
10e2e
Run E2E tests for Sentry JavaScript SDK test applications
9release
Publish a new Sentry JavaScript SDK release. Use when preparing a release, updating the changelog, or creating a release branch.
9dotagents
Manage agent skill dependencies with dotagents. Use when asked to "add a skill", "install skills", "remove a skill", "update skills", "dotagents init", "agents.toml", "agents.lock", "sync skills", "list skills", "set up dotagents", "configure trust", "add MCP server", "add hook", "wildcard skills", "user scope", or any dotagents-related task.
9