You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Merge branch 'develop' into onur/more-guarding-against-wildcard-transactions
Resolved conflicts in instrumentation.tsx by preserving wildcard transaction
handling improvements while integrating develop's router state improvements.
Key resolutions:
- Kept trackLazyRouteLoad() and lazy route timeout functionality
- Integrated shouldHandleNavigation() for router state awareness
- Preserved activeNavigationSpans and placeholder race condition handling
- Maintained wildcard-to-parameterized route name upgrade logic
3 cross-usage tests will need updates in follow-up to match new behavior.
description: Use this rule if you are looking to grade OpenTelemetry instrumentations for the Sentry JavaScript SDKs
3
+
globs: *
4
+
alwaysApply: false
5
+
---
6
+
7
+
# Upgrading OpenTelemetry instrumentations
8
+
9
+
1. For every package in packages/\*\*:
10
+
- When upgrading dependencies for OpenTelemetry instrumentations we need to first upgrade `@opentelemetry/instrumentation` to the latest version.
11
+
**CRITICAL**: `@opentelemetry/instrumentation` MUST NOT include any breaking changes.
12
+
Read through the changelog of `@opentelemetry/instrumentation` to figure out if breaking changes are included and fail with the reason if it does include breaking changes.
13
+
You can find the changelog at `https://github.com/open-telemetry/opentelemetry-js/blob/main/experimental/CHANGELOG.md`
14
+
15
+
- After successfully upgrading `@opentelemetry/instrumentation` upgrade all `@opentelemetry/instrumentation-{instrumentation}` packages, e.g. `@opentelemetry/instrumentation-pg`
16
+
**CRITICAL**: `@opentelemetry/instrumentation-{instrumentation}` MUST NOT include any breaking changes.
17
+
Read through the changelog of `@opentelemetry/instrumentation-{instrumentation}` to figure out if breaking changes are included and fail with the reason if it does including breaking changes.
18
+
You can find the changelogs at `https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/packages/instrumentation-{instrumentation}/CHANGELOG.md`.
19
+
20
+
- Finally, upgrade third party instrumentations to their latest versions, these are currently:
21
+
- @prisma/instrumentation
22
+
23
+
**CRITICAL**: Upgrades to third party instrumentations MUST NOT include breaking changes.
24
+
Read through the changelog of each third party instrumentation to figure out if breaking changes are included and fail with the reason if it does include breaking changes.
25
+
26
+
2. For packages and apps in dev-packages/\*\*:
27
+
- If an app depends on `@opentelemetry/instrumentation` >= 0.200.x upgrade it to the latest version.
28
+
**CRITICAL**: `@opentelemetry/instrumentation` MUST NOT include any breaking changes.
29
+
30
+
- If an app depends on `@opentelemetry/instrumentation-http` >= 0.200.x upgrade it to the latest version.
31
+
**CRITICAL**: `@opentelemetry/instrumentation-http` MUST NOT include any breaking changes.
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/bug.yml
+8-7Lines changed: 8 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -136,13 +136,14 @@ body:
136
136
id: additional
137
137
attributes:
138
138
label: Additional Context
139
-
description:
140
-
Add any other context here. Please keep the pre-filled text, which helps us manage issue prioritization.
141
-
value: |-
142
-
<sub>Tip: React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding `+1` or `me too`, to help us triage it.</sub>
139
+
description: Add any other context here.
143
140
validations:
144
141
required: false
145
-
- type: markdown
142
+
- type: dropdown
146
143
attributes:
147
-
value: |-
148
-
## Thanks 🙏
144
+
label: 'Priority'
145
+
description: Please keep the pre-filled option, which helps us manage issue prioritization.
146
+
default: 0
147
+
options:
148
+
- <sub>React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding `+1`
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/feature.yml
+8-8Lines changed: 8 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -27,14 +27,14 @@ body:
27
27
id: additional
28
28
attributes:
29
29
label: Additional Context
30
-
description:
31
-
Add any other context here. Please keep the pre-filled text, which helps us manage feature prioritization.
32
-
value: |-
33
-
<sub>Tip: React with 👍 to help prioritize this improvement. Please use comments to provide useful context, avoiding `+1` or `me too`, to help us triage it.</sub>
30
+
description: Add any other context here.
34
31
validations:
35
32
required: false
36
-
- type: markdown
33
+
- type: dropdown
37
34
attributes:
38
-
value: |-
39
-
## Thanks 🙏
40
-
Check our [triage docs](https://open.sentry.io/triage/) for what to expect next.
35
+
label: 'Priority'
36
+
description: Please keep the pre-filled option, which helps us manage issue prioritization.
37
+
default: 0
38
+
options:
39
+
- <sub>React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding `+1`
0 commit comments