Bump @sentry/profiling-node from 0.0.12 to 10.11.0
Type: Pull Request
State: Closed
Association: None
Comments: 3
(9 months ago)
(9 months ago)
(9 months ago)
Scope: Frontend
Bumps @sentry/profiling-node from 0.0.12 to 10.11.0.
Release notes
Sourced from @sentry/profiling-node's releases.
10.11.0
Important Changes
feat(aws): Add experimental AWS Lambda extension for tunnelling events (#17525)
This release adds an experimental Sentry Lambda extension to the existing Sentry Lambda layer. Sentry events are now tunneled through the extension and then forwarded to Sentry. This has the benefit of reducing the request processing time.
To enable it, set
_experiments.enableLambdaExtensionin your Sentry config like this:Sentry.init({ dsn: '<YOUR_DSN>', _experiments: { enableLambdaExtension: true, }, });Other Changes
- feat(core): Add replay id to logs (#17563)
- feat(core): Improve error handling for Anthropic AI instrumentation (#17535)
- feat(deps): bump
@opentelemetry/instrumentation-ioredisfrom 0.51.0 to 0.52.0 (#17557)- feat(node): Add incoming request headers as OTel span attributes (#17475)
- fix(astro): Ensure traces are correctly propagated for static routes (#17536)
- fix(react): Remove
handleExistingNavigation(#17534)- ref(browser): Add more specific
mechanism.typeto errors captured byhttpClientIntegration(#17254)- ref(browser): Set more descriptive
mechanism.typeinbrowserApiErrorsIntergation(#17251)- ref(core): Add
mechanism.typetotrpcMiddlewareerrors (#17287)- ref(core): Add more specific event
mechanisms and span origins toopenAiIntegration(#17288)- ref(nestjs): Add
mechanismto captured errors (#17312)
- chore: Use proper
test-utilsdependency in workspace (#17538)- chore(test): Remove
geistfont (#17541)- ci: Check for stable lockfile (#17552)
- ci: Fix running of only changed E2E tests (#17551)
- ci: Remove project automation workflow (#17508)
- test(node-integration-tests): pin ai@5.0.30 to fix test fails (#17542)
Bundle size 📦
Path Size @sentry/browser23.61 KB @sentry/browser- with treeshaking flags22.22 KB
... (truncated)
Changelog
Sourced from @sentry/profiling-node's changelog.
10.11.0
Important Changes
feat(aws): Add experimental AWS Lambda extension for tunnelling events (#17525)
This release adds an experimental Sentry Lambda extension to the existing Sentry Lambda layer. Sentry events are now tunneled through the extension and then forwarded to Sentry. This has the benefit of reducing the request processing time.
To enable it, set
_experiments.enableLambdaExtensionin your Sentry config like this:Sentry.init({ dsn: '<YOUR_DSN>', _experiments: { enableLambdaExtension: true, }, });Other Changes
- feat(core): Add replay id to logs (#17563)
- feat(core): Improve error handling for Anthropic AI instrumentation (#17535)
- feat(deps): bump
@opentelemetry/instrumentation-ioredisfrom 0.51.0 to 0.52.0 (#17557)- feat(node): Add incoming request headers as OTel span attributes (#17475)
- fix(astro): Ensure traces are correctly propagated for static routes (#17536)
- fix(react): Remove
handleExistingNavigation(#17534)- ref(browser): Add more specific
mechanism.typeto errors captured byhttpClientIntegration(#17254)- ref(browser): Set more descriptive
mechanism.typeinbrowserApiErrorsIntergation(#17251)- ref(core): Add
mechanism.typetotrpcMiddlewareerrors (#17287)- ref(core): Add more specific event
mechanisms and span origins toopenAiIntegration(#17288)- ref(nestjs): Add
mechanismto captured errors (#17312)
- chore: Use proper
test-utilsdependency in workspace (#17538)- chore(test): Remove
geistfont (#17541)- ci: Check for stable lockfile (#17552)
- ci: Fix running of only changed E2E tests (#17551)
- ci: Remove project automation workflow (#17508)
- test(node-integration-tests): pin ai@5.0.30 to fix test fails (#17542)
10.10.0
Important Changes
- feat(browser): Add support for
propagateTraceparentSDK option (#17509)
... (truncated)
Commits
- See full diff in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Pull Request Statistics
1
2
+582
-422
Package Dependencies
Technical Details
| ID: | 7341234 |
| UUID: | 2813453225 |
| Node ID: | PR_kwDOIiIfRc6nseOp |
| Host: | GitHub |
| Repository: | python-benchmark/sentry |
| Mergeable: | Yes |
| Merge State: | Unstable |