feat(core): Add the primitives to answer managed tunnel requests in the runtimes by logaretm · Pull Request #25997 · getsentry/sentry-javascript

feat(core): Add the primitives to answer managed tunnel requests in the runtimes

logaretm

committed

ae3cbec

ref(core): Keep the managed tunnel state behind a registry module

logaretm

committed

bc33cba

ref(core): Rename the tunnel registry's client accessors

logaretm

committed

6435b16

ref(core): Read the tunnel forwarder from the shared registry only

logaretm

committed

3fd8179

ref(core): Name the tunnel registry's carrier key after it

logaretm

committed

0fdfaf1

ref(core): Rename the tunnel registry to the tunnel store

logaretm

committed

c92ecd2

ref: Rename the managed tunnel defaults to tunnel defaults

logaretm

committed

a672b62

ref(core): Name the client tunnel resolver applyTunnelDefaults

logaretm

committed

8180949

ref: Name the browser and server tunnel defaults functions after where they run

logaretm

committed

a63290a

fix(core): Isolate tunnel requests the app answers itself

logaretm

committed

cc48a54

fix(core): Set the client on the isolation scope of tunnel requests the app answers

logaretm

committed

2d0875b

fix(server-utils): Capture errors and request data of tunnel requests the app answers

logaretm

committed

46d84af

fix(core): Deliver tunnel envelopes after the browser leaves

logaretm

committed

9c67136

fix(core): Claim tunnel requests before forwarding them

logaretm

committed

f92c9ac

test(node): Leave the tunnel only after it started the upload to Sentry

logaretm

committed

3d4645d

ref(core): Drop the unused close listener from the tunnel's Node response type

logaretm

committed

bf844da

Navigation Menu

Repository navigation

feat(core): Add the primitives to answer managed tunnel requests in the runtimes - #25997

feat(core): Add the primitives to answer managed tunnel requests in the runtimes#25997
logaretm merged 16 commits into
developfrom
awad/runtime-tunnel-core

Commits on Nov 6, 2026

feat(core): Add the primitives to answer managed tunnel requests in the runtimes

ref(core): Keep the managed tunnel state behind a registry module

ref(core): Rename the tunnel registry's client accessors

ref(core): Read the tunnel forwarder from the shared registry only

ref(core): Name the tunnel registry's carrier key after it

ref(core): Rename the tunnel registry to the tunnel store

ref: Rename the managed tunnel defaults to tunnel defaults

ref(core): Name the client tunnel resolver applyTunnelDefaults

ref: Name the browser and server tunnel defaults functions after where they run

fix(core): Isolate tunnel requests the app answers itself

fix(core): Set the client on the isolation scope of tunnel requests the app answers

fix(server-utils): Capture errors and request data of tunnel requests the app answers

fix(core): Deliver tunnel envelopes after the browser leaves

fix(core): Claim tunnel requests before forwarding them

test(node): Leave the tunnel only after it started the upload to Sentry

ref(core): Drop the unused close listener from the tunnel's Node response type