meta(changelog): Update changelog for 7.71.0 by lforst · Pull Request #9103 · getsentry/sentry-javascript

lforst · 2023-09-25T12:04:37Z

Minor bc of #9022

[Gitflow] Merge master into develop

…#9064) Even if no scope is passed. I guess this is kind of behavior changing, but I'd argue it is just fixing an unexpected behaviour that's not actually intuitive/logical - that global event processors are only applied if a scope is provided.

I noticed that while from an API POV the current behavior makes kind-of sense IMHO: 1. Run global event processors 2. Run scope event processors 3. Run client event processors It is potentially breaking, as if we rewrite integrations to use the new client processors, their processing will run after any user global event processors, leading to potentially unexpected outcomes. So this PR changes this to instead run them in this order: 1. Run client event processors 2. Run global event processors 3. Run scope event processors Which should be more stable for now. In v8, we should update this to run a more sensible order: 1. Global 2. Client 3. Scope

…9070) Also update all OTEL dependencies to latest to align these properly. The sdk-trace-node package actually just wraps sdk-trace-base, adds some default exports (that we do not need) + sets the async local storage context manager by default (which we overwrite anyhow). So we can cut down on one dependency there and make this a tiny bit easier. I also made a central `OtelSpan` type in node-experimental to avoid using this everywhere throughout the codebase.

Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>

) This refactors browser integrations to use the new `processEvent` hook on the Integrations interface. It also updates Replay to register it's event processor on the client, not globally. This is also needed to ensure the order is somewhat stable, as global processors are run separately from the client ones.

Previously, the error name would always be `React ErrorBoundary Error`, because `errorBoundaryError.name` refers to the name of the Error object that was just created.

Bumps [graphql](https://github.com/graphql/graphql-js) from 16.3.0 to 16.8.1. - [Release notes](https://github.com/graphql/graphql-js/releases) - [Commits](graphql/graphql-js@v16.3.0...v16.8.1) --- updated-dependencies: - dependency-name: graphql dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>

) To keep things better together, and in preparation for follow up PRs with more OTEL-specific stuff. Nothing functionally changes here, this is just to keep follow up PRs more readable as there is a lot going on...

…#9099) Also add tests for this. This can then be reused e.g. by node-experimental in a later step.

…request async storage module (#9100)

mydea

lforst · 2023-09-25T12:04:37Z

Minor bc of #9022

[Gitflow] Merge master into develop

…#9064) Even if no scope is passed. I guess this is kind of behavior changing, but I'd argue it is just fixing an unexpected behaviour that's not actually intuitive/logical - that global event processors are only applied if a scope is provided.

I noticed that while from an API POV the current behavior makes kind-of sense IMHO: 1. Run global event processors 2. Run scope event processors 3. Run client event processors It is potentially breaking, as if we rewrite integrations to use the new client processors, their processing will run after any user global event processors, leading to potentially unexpected outcomes. So this PR changes this to instead run them in this order: 1. Run client event processors 2. Run global event processors 3. Run scope event processors Which should be more stable for now. In v8, we should update this to run a more sensible order: 1. Global 2. Client 3. Scope

…9070) Also update all OTEL dependencies to latest to align these properly. The sdk-trace-node package actually just wraps sdk-trace-base, adds some default exports (that we do not need) + sets the async local storage context manager by default (which we overwrite anyhow). So we can cut down on one dependency there and make this a tiny bit easier. I also made a central `OtelSpan` type in node-experimental to avoid using this everywhere throughout the codebase.

Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>

) This refactors browser integrations to use the new `processEvent` hook on the Integrations interface. It also updates Replay to register it's event processor on the client, not globally. This is also needed to ensure the order is somewhat stable, as global processors are run separately from the client ones.

Previously, the error name would always be `React ErrorBoundary Error`, because `errorBoundaryError.name` refers to the name of the Error object that was just created.

Bumps [graphql](https://github.com/graphql/graphql-js) from 16.3.0 to 16.8.1. - [Release notes](https://github.com/graphql/graphql-js/releases) - [Commits](graphql/graphql-js@v16.3.0...v16.8.1) --- updated-dependencies: - dependency-name: graphql dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>

) To keep things better together, and in preparation for follow up PRs with more OTEL-specific stuff. Nothing functionally changes here, this is just to keep follow up PRs more readable as there is a lot going on...

…#9099) Also add tests for this. This can then be reused e.g. by node-experimental in a later step.

…request async storage module (#9100)

mydea

lforst · 2023-09-25T12:04:37Z

Minor bc of #9022

[Gitflow] Merge master into develop

…#9064) Even if no scope is passed. I guess this is kind of behavior changing, but I'd argue it is just fixing an unexpected behaviour that's not actually intuitive/logical - that global event processors are only applied if a scope is provided.

I noticed that while from an API POV the current behavior makes kind-of sense IMHO: 1. Run global event processors 2. Run scope event processors 3. Run client event processors It is potentially breaking, as if we rewrite integrations to use the new client processors, their processing will run after any user global event processors, leading to potentially unexpected outcomes. So this PR changes this to instead run them in this order: 1. Run client event processors 2. Run global event processors 3. Run scope event processors Which should be more stable for now. In v8, we should update this to run a more sensible order: 1. Global 2. Client 3. Scope

…9070) Also update all OTEL dependencies to latest to align these properly. The sdk-trace-node package actually just wraps sdk-trace-base, adds some default exports (that we do not need) + sets the async local storage context manager by default (which we overwrite anyhow). So we can cut down on one dependency there and make this a tiny bit easier. I also made a central `OtelSpan` type in node-experimental to avoid using this everywhere throughout the codebase.

Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>

) This refactors browser integrations to use the new `processEvent` hook on the Integrations interface. It also updates Replay to register it's event processor on the client, not globally. This is also needed to ensure the order is somewhat stable, as global processors are run separately from the client ones.

Previously, the error name would always be `React ErrorBoundary Error`, because `errorBoundaryError.name` refers to the name of the Error object that was just created.

Bumps [graphql](https://github.com/graphql/graphql-js) from 16.3.0 to 16.8.1. - [Release notes](https://github.com/graphql/graphql-js/releases) - [Commits](graphql/graphql-js@v16.3.0...v16.8.1) --- updated-dependencies: - dependency-name: graphql dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>

) To keep things better together, and in preparation for follow up PRs with more OTEL-specific stuff. Nothing functionally changes here, this is just to keep follow up PRs more readable as there is a lot going on...

…#9099) Also add tests for this. This can then be reused e.g. by node-experimental in a later step.

…request async storage module (#9100)

mydea

lforst · 2023-09-25T12:04:37Z

Minor bc of #9022

[Gitflow] Merge master into develop

…#9064) Even if no scope is passed. I guess this is kind of behavior changing, but I'd argue it is just fixing an unexpected behaviour that's not actually intuitive/logical - that global event processors are only applied if a scope is provided.

I noticed that while from an API POV the current behavior makes kind-of sense IMHO: 1. Run global event processors 2. Run scope event processors 3. Run client event processors It is potentially breaking, as if we rewrite integrations to use the new client processors, their processing will run after any user global event processors, leading to potentially unexpected outcomes. So this PR changes this to instead run them in this order: 1. Run client event processors 2. Run global event processors 3. Run scope event processors Which should be more stable for now. In v8, we should update this to run a more sensible order: 1. Global 2. Client 3. Scope

…9070) Also update all OTEL dependencies to latest to align these properly. The sdk-trace-node package actually just wraps sdk-trace-base, adds some default exports (that we do not need) + sets the async local storage context manager by default (which we overwrite anyhow). So we can cut down on one dependency there and make this a tiny bit easier. I also made a central `OtelSpan` type in node-experimental to avoid using this everywhere throughout the codebase.

Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>

) This refactors browser integrations to use the new `processEvent` hook on the Integrations interface. It also updates Replay to register it's event processor on the client, not globally. This is also needed to ensure the order is somewhat stable, as global processors are run separately from the client ones.

Previously, the error name would always be `React ErrorBoundary Error`, because `errorBoundaryError.name` refers to the name of the Error object that was just created.

Bumps [graphql](https://github.com/graphql/graphql-js) from 16.3.0 to 16.8.1. - [Release notes](https://github.com/graphql/graphql-js/releases) - [Commits](graphql/graphql-js@v16.3.0...v16.8.1) --- updated-dependencies: - dependency-name: graphql dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>

) To keep things better together, and in preparation for follow up PRs with more OTEL-specific stuff. Nothing functionally changes here, this is just to keep follow up PRs more readable as there is a lot going on...

…#9099) Also add tests for this. This can then be reused e.g. by node-experimental in a later step.

…request async storage module (#9100)

mydea

lforst · 2023-09-25T12:04:37Z

Minor bc of #9022

[Gitflow] Merge master into develop

…#9064) Even if no scope is passed. I guess this is kind of behavior changing, but I'd argue it is just fixing an unexpected behaviour that's not actually intuitive/logical - that global event processors are only applied if a scope is provided.

I noticed that while from an API POV the current behavior makes kind-of sense IMHO: 1. Run global event processors 2. Run scope event processors 3. Run client event processors It is potentially breaking, as if we rewrite integrations to use the new client processors, their processing will run after any user global event processors, leading to potentially unexpected outcomes. So this PR changes this to instead run them in this order: 1. Run client event processors 2. Run global event processors 3. Run scope event processors Which should be more stable for now. In v8, we should update this to run a more sensible order: 1. Global 2. Client 3. Scope

…9070) Also update all OTEL dependencies to latest to align these properly. The sdk-trace-node package actually just wraps sdk-trace-base, adds some default exports (that we do not need) + sets the async local storage context manager by default (which we overwrite anyhow). So we can cut down on one dependency there and make this a tiny bit easier. I also made a central `OtelSpan` type in node-experimental to avoid using this everywhere throughout the codebase.

Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>

) This refactors browser integrations to use the new `processEvent` hook on the Integrations interface. It also updates Replay to register it's event processor on the client, not globally. This is also needed to ensure the order is somewhat stable, as global processors are run separately from the client ones.

Previously, the error name would always be `React ErrorBoundary Error`, because `errorBoundaryError.name` refers to the name of the Error object that was just created.

Bumps [graphql](https://github.com/graphql/graphql-js) from 16.3.0 to 16.8.1. - [Release notes](https://github.com/graphql/graphql-js/releases) - [Commits](graphql/graphql-js@v16.3.0...v16.8.1) --- updated-dependencies: - dependency-name: graphql dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>

) To keep things better together, and in preparation for follow up PRs with more OTEL-specific stuff. Nothing functionally changes here, this is just to keep follow up PRs more readable as there is a lot going on...

…#9099) Also add tests for this. This can then be reused e.g. by node-experimental in a later step.

…request async storage module (#9100)

mydea

lforst · 2023-09-25T12:04:37Z

Minor bc of #9022

[Gitflow] Merge master into develop

…#9064) Even if no scope is passed. I guess this is kind of behavior changing, but I'd argue it is just fixing an unexpected behaviour that's not actually intuitive/logical - that global event processors are only applied if a scope is provided.

I noticed that while from an API POV the current behavior makes kind-of sense IMHO: 1. Run global event processors 2. Run scope event processors 3. Run client event processors It is potentially breaking, as if we rewrite integrations to use the new client processors, their processing will run after any user global event processors, leading to potentially unexpected outcomes. So this PR changes this to instead run them in this order: 1. Run client event processors 2. Run global event processors 3. Run scope event processors Which should be more stable for now. In v8, we should update this to run a more sensible order: 1. Global 2. Client 3. Scope

…9070) Also update all OTEL dependencies to latest to align these properly. The sdk-trace-node package actually just wraps sdk-trace-base, adds some default exports (that we do not need) + sets the async local storage context manager by default (which we overwrite anyhow). So we can cut down on one dependency there and make this a tiny bit easier. I also made a central `OtelSpan` type in node-experimental to avoid using this everywhere throughout the codebase.

Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>

) This refactors browser integrations to use the new `processEvent` hook on the Integrations interface. It also updates Replay to register it's event processor on the client, not globally. This is also needed to ensure the order is somewhat stable, as global processors are run separately from the client ones.

Previously, the error name would always be `React ErrorBoundary Error`, because `errorBoundaryError.name` refers to the name of the Error object that was just created.

Bumps [graphql](https://github.com/graphql/graphql-js) from 16.3.0 to 16.8.1. - [Release notes](https://github.com/graphql/graphql-js/releases) - [Commits](graphql/graphql-js@v16.3.0...v16.8.1) --- updated-dependencies: - dependency-name: graphql dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>

) To keep things better together, and in preparation for follow up PRs with more OTEL-specific stuff. Nothing functionally changes here, this is just to keep follow up PRs more readable as there is a lot going on...

…#9099) Also add tests for this. This can then be reused e.g. by node-experimental in a later step.

…request async storage module (#9100)

mydea

lforst · 2023-09-25T12:04:37Z

Minor bc of #9022

[Gitflow] Merge master into develop

…#9064) Even if no scope is passed. I guess this is kind of behavior changing, but I'd argue it is just fixing an unexpected behaviour that's not actually intuitive/logical - that global event processors are only applied if a scope is provided.

I noticed that while from an API POV the current behavior makes kind-of sense IMHO: 1. Run global event processors 2. Run scope event processors 3. Run client event processors It is potentially breaking, as if we rewrite integrations to use the new client processors, their processing will run after any user global event processors, leading to potentially unexpected outcomes. So this PR changes this to instead run them in this order: 1. Run client event processors 2. Run global event processors 3. Run scope event processors Which should be more stable for now. In v8, we should update this to run a more sensible order: 1. Global 2. Client 3. Scope

…9070) Also update all OTEL dependencies to latest to align these properly. The sdk-trace-node package actually just wraps sdk-trace-base, adds some default exports (that we do not need) + sets the async local storage context manager by default (which we overwrite anyhow). So we can cut down on one dependency there and make this a tiny bit easier. I also made a central `OtelSpan` type in node-experimental to avoid using this everywhere throughout the codebase.

Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>

) This refactors browser integrations to use the new `processEvent` hook on the Integrations interface. It also updates Replay to register it's event processor on the client, not globally. This is also needed to ensure the order is somewhat stable, as global processors are run separately from the client ones.

Previously, the error name would always be `React ErrorBoundary Error`, because `errorBoundaryError.name` refers to the name of the Error object that was just created.

Bumps [graphql](https://github.com/graphql/graphql-js) from 16.3.0 to 16.8.1. - [Release notes](https://github.com/graphql/graphql-js/releases) - [Commits](graphql/graphql-js@v16.3.0...v16.8.1) --- updated-dependencies: - dependency-name: graphql dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>

) To keep things better together, and in preparation for follow up PRs with more OTEL-specific stuff. Nothing functionally changes here, this is just to keep follow up PRs more readable as there is a lot going on...

…#9099) Also add tests for this. This can then be reused e.g. by node-experimental in a later step.

…request async storage module (#9100)

mydea

lforst · 2023-09-25T12:04:37Z

Minor bc of #9022

[Gitflow] Merge master into develop

…#9064) Even if no scope is passed. I guess this is kind of behavior changing, but I'd argue it is just fixing an unexpected behaviour that's not actually intuitive/logical - that global event processors are only applied if a scope is provided.

I noticed that while from an API POV the current behavior makes kind-of sense IMHO: 1. Run global event processors 2. Run scope event processors 3. Run client event processors It is potentially breaking, as if we rewrite integrations to use the new client processors, their processing will run after any user global event processors, leading to potentially unexpected outcomes. So this PR changes this to instead run them in this order: 1. Run client event processors 2. Run global event processors 3. Run scope event processors Which should be more stable for now. In v8, we should update this to run a more sensible order: 1. Global 2. Client 3. Scope

…9070) Also update all OTEL dependencies to latest to align these properly. The sdk-trace-node package actually just wraps sdk-trace-base, adds some default exports (that we do not need) + sets the async local storage context manager by default (which we overwrite anyhow). So we can cut down on one dependency there and make this a tiny bit easier. I also made a central `OtelSpan` type in node-experimental to avoid using this everywhere throughout the codebase.

Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>

) This refactors browser integrations to use the new `processEvent` hook on the Integrations interface. It also updates Replay to register it's event processor on the client, not globally. This is also needed to ensure the order is somewhat stable, as global processors are run separately from the client ones.

Previously, the error name would always be `React ErrorBoundary Error`, because `errorBoundaryError.name` refers to the name of the Error object that was just created.

Bumps [graphql](https://github.com/graphql/graphql-js) from 16.3.0 to 16.8.1. - [Release notes](https://github.com/graphql/graphql-js/releases) - [Commits](graphql/graphql-js@v16.3.0...v16.8.1) --- updated-dependencies: - dependency-name: graphql dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>

) To keep things better together, and in preparation for follow up PRs with more OTEL-specific stuff. Nothing functionally changes here, this is just to keep follow up PRs more readable as there is a lot going on...

…#9099) Also add tests for this. This can then be reused e.g. by node-experimental in a later step.

…request async storage module (#9100)

mydea

github-actionsBotand others added 16 commits September 20, 2023 11:14

Merge pull request#9069from getsentry/master
469881d
[Gitflow] Merge master into develop

fix(react): Compare location againstbasename-prefixed route. (#9076)
27cf07f
Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>

docs: Fix comments describing different import styles in readme (#9081)
ef2ed6b

chore: publish bun to release registry (#9073)
685d3b2

feat(bun): Instrument Bun.serve (#9080)
8001498

fix(react): Add actual error name to boundary error name (#9065)
1f8de57
Previously, the error name would always be `React ErrorBoundary Error`, because `errorBoundaryError.name` refers to the name of the Error object that was just created.

ref(node-experimental): Reorder files intoopentelemetryfolder (#9084
d94e72a
) To keep things better together, and in preparation for follow up PRs with more OTEL-specific stuff. Nothing functionally changes here, this is just to keep follow up PRs more readable as there is a lot going on...

chore: Publish @sentry/vercel-edge to release registry (#9074)
0532541

ref(opentelemetry-node): ExtractmaybeCaptureExceptionForTimedEvent(…
705be9b
…#9099) Also add tests for this. This can then be reused e.g. by node-experimental in a later step.

fix(nextjs): Use webpack module paths to attempt to resolve internal …
622186c
…request async storage module (#9100)

meta(changelog): Update changelog for 7.71.0
90b0c1f

lforst requested review from AbhiPrasad and mydea September 25, 2023 12:04

mydea approved these changes Sep 25, 2023
View reviewed changes

lforst merged commit 3ee7e00 into masterSep 25, 2023

lforst deleted the prepare-release/7.71.0 branch September 25, 2023 12:49

github-actionsBotand others added 16 commits September 20, 2023 11:14

Merge pull request#9069from getsentry/master
469881d
[Gitflow] Merge master into develop

fix(react): Compare location againstbasename-prefixed route. (#9076)
27cf07f
Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>

docs: Fix comments describing different import styles in readme (#9081)
ef2ed6b

chore: publish bun to release registry (#9073)
685d3b2

feat(bun): Instrument Bun.serve (#9080)
8001498

fix(react): Add actual error name to boundary error name (#9065)
1f8de57
Previously, the error name would always be `React ErrorBoundary Error`, because `errorBoundaryError.name` refers to the name of the Error object that was just created.

ref(node-experimental): Reorder files intoopentelemetryfolder (#9084
d94e72a
) To keep things better together, and in preparation for follow up PRs with more OTEL-specific stuff. Nothing functionally changes here, this is just to keep follow up PRs more readable as there is a lot going on...

chore: Publish @sentry/vercel-edge to release registry (#9074)
0532541

ref(opentelemetry-node): ExtractmaybeCaptureExceptionForTimedEvent(…
705be9b
…#9099) Also add tests for this. This can then be reused e.g. by node-experimental in a later step.

fix(nextjs): Use webpack module paths to attempt to resolve internal …
622186c
…request async storage module (#9100)

meta(changelog): Update changelog for 7.71.0
90b0c1f

lforst requested review from AbhiPrasad and mydea September 25, 2023 12:04

mydea approved these changes Sep 25, 2023
View reviewed changes

lforst merged commit 3ee7e00 into masterSep 25, 2023

lforst deleted the prepare-release/7.71.0 branch September 25, 2023 12:49

github-actionsBotand others added 16 commits September 20, 2023 11:14

Merge pull request#9069from getsentry/master
469881d
[Gitflow] Merge master into develop

fix(react): Compare location againstbasename-prefixed route. (#9076)
27cf07f
Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>

docs: Fix comments describing different import styles in readme (#9081)
ef2ed6b

chore: publish bun to release registry (#9073)
685d3b2

feat(bun): Instrument Bun.serve (#9080)
8001498

fix(react): Add actual error name to boundary error name (#9065)
1f8de57
Previously, the error name would always be `React ErrorBoundary Error`, because `errorBoundaryError.name` refers to the name of the Error object that was just created.

ref(node-experimental): Reorder files intoopentelemetryfolder (#9084
d94e72a
) To keep things better together, and in preparation for follow up PRs with more OTEL-specific stuff. Nothing functionally changes here, this is just to keep follow up PRs more readable as there is a lot going on...

chore: Publish @sentry/vercel-edge to release registry (#9074)
0532541

ref(opentelemetry-node): ExtractmaybeCaptureExceptionForTimedEvent(…
705be9b
…#9099) Also add tests for this. This can then be reused e.g. by node-experimental in a later step.

fix(nextjs): Use webpack module paths to attempt to resolve internal …
622186c
…request async storage module (#9100)

meta(changelog): Update changelog for 7.71.0
90b0c1f

lforst requested review from AbhiPrasad and mydea September 25, 2023 12:04

mydea approved these changes Sep 25, 2023
View reviewed changes

lforst merged commit 3ee7e00 into masterSep 25, 2023

lforst deleted the prepare-release/7.71.0 branch September 25, 2023 12:49

github-actionsBotand others added 16 commits September 20, 2023 11:14

Merge pull request#9069from getsentry/master
469881d
[Gitflow] Merge master into develop

fix(react): Compare location againstbasename-prefixed route. (#9076)
27cf07f
Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>

docs: Fix comments describing different import styles in readme (#9081)
ef2ed6b

chore: publish bun to release registry (#9073)
685d3b2

feat(bun): Instrument Bun.serve (#9080)
8001498

fix(react): Add actual error name to boundary error name (#9065)
1f8de57
Previously, the error name would always be `React ErrorBoundary Error`, because `errorBoundaryError.name` refers to the name of the Error object that was just created.

ref(node-experimental): Reorder files intoopentelemetryfolder (#9084
d94e72a
) To keep things better together, and in preparation for follow up PRs with more OTEL-specific stuff. Nothing functionally changes here, this is just to keep follow up PRs more readable as there is a lot going on...

chore: Publish @sentry/vercel-edge to release registry (#9074)
0532541

ref(opentelemetry-node): ExtractmaybeCaptureExceptionForTimedEvent(…
705be9b
…#9099) Also add tests for this. This can then be reused e.g. by node-experimental in a later step.

fix(nextjs): Use webpack module paths to attempt to resolve internal …
622186c
…request async storage module (#9100)

meta(changelog): Update changelog for 7.71.0
90b0c1f

lforst requested review from AbhiPrasad and mydea September 25, 2023 12:04

mydea approved these changes Sep 25, 2023
View reviewed changes

lforst merged commit 3ee7e00 into masterSep 25, 2023

lforst deleted the prepare-release/7.71.0 branch September 25, 2023 12:49

github-actionsBotand others added 16 commits September 20, 2023 11:14

Merge pull request#9069from getsentry/master
469881d
[Gitflow] Merge master into develop

fix(react): Compare location againstbasename-prefixed route. (#9076)
27cf07f
Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>

docs: Fix comments describing different import styles in readme (#9081)
ef2ed6b

chore: publish bun to release registry (#9073)
685d3b2

feat(bun): Instrument Bun.serve (#9080)
8001498

fix(react): Add actual error name to boundary error name (#9065)
1f8de57
Previously, the error name would always be `React ErrorBoundary Error`, because `errorBoundaryError.name` refers to the name of the Error object that was just created.

ref(node-experimental): Reorder files intoopentelemetryfolder (#9084
d94e72a
) To keep things better together, and in preparation for follow up PRs with more OTEL-specific stuff. Nothing functionally changes here, this is just to keep follow up PRs more readable as there is a lot going on...

chore: Publish @sentry/vercel-edge to release registry (#9074)
0532541

ref(opentelemetry-node): ExtractmaybeCaptureExceptionForTimedEvent(…
705be9b
…#9099) Also add tests for this. This can then be reused e.g. by node-experimental in a later step.

fix(nextjs): Use webpack module paths to attempt to resolve internal …
622186c
…request async storage module (#9100)

meta(changelog): Update changelog for 7.71.0
90b0c1f

lforst requested review from AbhiPrasad and mydea September 25, 2023 12:04

mydea approved these changes Sep 25, 2023
View reviewed changes

lforst merged commit 3ee7e00 into masterSep 25, 2023

lforst deleted the prepare-release/7.71.0 branch September 25, 2023 12:49

github-actionsBotand others added 16 commits September 20, 2023 11:14

Merge pull request#9069from getsentry/master
469881d
[Gitflow] Merge master into develop

fix(react): Compare location againstbasename-prefixed route. (#9076)
27cf07f
Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>

docs: Fix comments describing different import styles in readme (#9081)
ef2ed6b

chore: publish bun to release registry (#9073)
685d3b2

feat(bun): Instrument Bun.serve (#9080)
8001498

fix(react): Add actual error name to boundary error name (#9065)
1f8de57
Previously, the error name would always be `React ErrorBoundary Error`, because `errorBoundaryError.name` refers to the name of the Error object that was just created.

ref(node-experimental): Reorder files intoopentelemetryfolder (#9084
d94e72a
) To keep things better together, and in preparation for follow up PRs with more OTEL-specific stuff. Nothing functionally changes here, this is just to keep follow up PRs more readable as there is a lot going on...

chore: Publish @sentry/vercel-edge to release registry (#9074)
0532541

ref(opentelemetry-node): ExtractmaybeCaptureExceptionForTimedEvent(…
705be9b
…#9099) Also add tests for this. This can then be reused e.g. by node-experimental in a later step.

fix(nextjs): Use webpack module paths to attempt to resolve internal …
622186c
…request async storage module (#9100)

meta(changelog): Update changelog for 7.71.0
90b0c1f

lforst requested review from AbhiPrasad and mydea September 25, 2023 12:04

mydea approved these changes Sep 25, 2023
View reviewed changes

lforst merged commit 3ee7e00 into masterSep 25, 2023

lforst deleted the prepare-release/7.71.0 branch September 25, 2023 12:49

github-actionsBotand others added 16 commits September 20, 2023 11:14

Merge pull request#9069from getsentry/master
469881d
[Gitflow] Merge master into develop

fix(react): Compare location againstbasename-prefixed route. (#9076)
27cf07f
Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>

docs: Fix comments describing different import styles in readme (#9081)
ef2ed6b

chore: publish bun to release registry (#9073)
685d3b2

feat(bun): Instrument Bun.serve (#9080)
8001498

fix(react): Add actual error name to boundary error name (#9065)
1f8de57
Previously, the error name would always be `React ErrorBoundary Error`, because `errorBoundaryError.name` refers to the name of the Error object that was just created.

ref(node-experimental): Reorder files intoopentelemetryfolder (#9084
d94e72a
) To keep things better together, and in preparation for follow up PRs with more OTEL-specific stuff. Nothing functionally changes here, this is just to keep follow up PRs more readable as there is a lot going on...

chore: Publish @sentry/vercel-edge to release registry (#9074)
0532541

ref(opentelemetry-node): ExtractmaybeCaptureExceptionForTimedEvent(…
705be9b
…#9099) Also add tests for this. This can then be reused e.g. by node-experimental in a later step.

fix(nextjs): Use webpack module paths to attempt to resolve internal …
622186c
…request async storage module (#9100)

meta(changelog): Update changelog for 7.71.0
90b0c1f

lforst requested review from AbhiPrasad and mydea September 25, 2023 12:04

mydea approved these changes Sep 25, 2023
View reviewed changes

lforst merged commit 3ee7e00 into masterSep 25, 2023

lforst deleted the prepare-release/7.71.0 branch September 25, 2023 12:49

github-actionsBotand others added 16 commits September 20, 2023 11:14

Merge pull request#9069from getsentry/master
469881d
[Gitflow] Merge master into develop

fix(react): Compare location againstbasename-prefixed route. (#9076)
27cf07f
Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>

docs: Fix comments describing different import styles in readme (#9081)
ef2ed6b

chore: publish bun to release registry (#9073)
685d3b2

feat(bun): Instrument Bun.serve (#9080)
8001498

fix(react): Add actual error name to boundary error name (#9065)
1f8de57
Previously, the error name would always be `React ErrorBoundary Error`, because `errorBoundaryError.name` refers to the name of the Error object that was just created.

ref(node-experimental): Reorder files intoopentelemetryfolder (#9084
d94e72a
) To keep things better together, and in preparation for follow up PRs with more OTEL-specific stuff. Nothing functionally changes here, this is just to keep follow up PRs more readable as there is a lot going on...

chore: Publish @sentry/vercel-edge to release registry (#9074)
0532541

ref(opentelemetry-node): ExtractmaybeCaptureExceptionForTimedEvent(…
705be9b
…#9099) Also add tests for this. This can then be reused e.g. by node-experimental in a later step.

fix(nextjs): Use webpack module paths to attempt to resolve internal …
622186c
…request async storage module (#9100)

meta(changelog): Update changelog for 7.71.0
90b0c1f

lforst requested review from AbhiPrasad and mydea September 25, 2023 12:04

mydea approved these changes Sep 25, 2023
View reviewed changes

lforst merged commit 3ee7e00 into masterSep 25, 2023

lforst deleted the prepare-release/7.71.0 branch September 25, 2023 12:49

Uh oh!

Uh oh!

Conversation

lforst commented Sep 25, 2023

Uh oh!

mydea left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Uh oh!

Uh oh!

Conversation

lforst commented Sep 25, 2023

Uh oh!

mydea left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Uh oh!

Uh oh!

Conversation

lforst commented Sep 25, 2023

Uh oh!

mydea left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Uh oh!

Uh oh!

Conversation

lforst commented Sep 25, 2023

Uh oh!

mydea left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Uh oh!

Uh oh!

Conversation

lforst commented Sep 25, 2023

Uh oh!

mydea left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants