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
feat(core)!: Remove endTimestamp from SentrySpanArguments (#23269)
## What
Removes the `endTimestamp` property from `SentrySpanArguments` and
related dead code in `SentrySpan` and `_startChildSpan`.
## Why
`StartSpanOptions` never declared `endTimestamp`, but
`parseSentrySpanArguments` spreads the user's options, so users could
ignore TS and have the span to end immediately by adding the
`endTimestamp` property.
Closes#21405
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: docs/migration/v11-end-state.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1101,7 +1101,9 @@ The same applies when looking the integration up by name, e.g. via `client.getIn
1101
1101
`any`.
1102
1102
- Attribute typing and serialization were unified across the SDK.
1103
1103
- The `attributes` field on the `ScopeData` type is now required. `Scope.getScopeData()` always returned it, so this only affects code that constructs `ScopeData` objects manually — add `attributes: {}` there.
1104
-
- The `SentrySpanArguments` interface and related dead code in `SentrySpan` were cleaned up.
1104
+
- The `endTimestamp` property was removed from the `SentrySpanArguments` interface. It was never part of
1105
+
`StartSpanOptions`, so it could only be passed by ignoring TypeScript, in which case the span ended itself
1106
+
during construction. Call `span.end(timestamp)` instead.
1105
1107
- `BrowserOptions` now supports the `TransportOptions` generic.
1106
1108
- (Cloudflare) The `env` types and the generics on `withSentry` and `instrumentDurableObjectWithSentry` were reworked for better type safety. If you were not passing explicit generic type parameters, no changes are needed.
0 commit comments