meta(changelog): Update changelog for v8.0.0-alpha.1

.github/workflows/build.yml

@@ -620,7 +620,7 @@ jobs:
     name: Playwright (${{ matrix.bundle }}${{ matrix.shard && format(' {0}/{1}', matrix.shard, matrix.shards) || ''}}) Tests
     needs: [job_get_metadata, job_build]
     if: needs.job_get_metadata.outputs.changed_browser_integration == 'true' || github.event_name != 'pull_request'
-    runs-on: ubuntu-20.04-large-js
+    runs-on: ubuntu-20.04
     timeout-minutes: 25
     strategy:
       fail-fast: false
@@ -783,7 +783,7 @@ jobs:
     name: Browser (${{ matrix.browser }}) Tests
     needs: [job_get_metadata, job_build]
     if: needs.job_get_metadata.outputs.changed_browser == 'true' || github.event_name != 'pull_request'
-    runs-on: ubuntu-20.04-large-js
+    runs-on: ubuntu-20.04
     timeout-minutes: 20
     strategy:
       fail-fast: false

.github/workflows/flaky-test-detector.yml

@@ -23,7 +23,7 @@ concurrency:
 
 jobs:
   flaky-detector:
-    runs-on: ubuntu-20.04-large-js
+    runs-on: ubuntu-20.04
     timeout-minutes: 60
     name: 'Check tests for flakiness'
     # Also skip if PR is from master -> develop

CHANGELOG.md

@@ -19,7 +19,7 @@ changes:
 
 - There is now automated performance instrumentation for Express, Fastify, Nest.js and Koa. You can remove any
   performance and request isolation code you previously wrote manually for these frameworks.
-- All performance instrumenttion is enabled by default, and will only take effect if the instrumented package is used.
+- All performance instrumention is enabled by default, and will only take effect if the instrumented package is used.
   You don't need to use `autoDiscoverNodePerformanceMonitoringIntegrations()` anymore.
 - You need to ensure to call `Sentry.init()` _before_ you import any other packages. Otherwise, the packages cannot be
   instrumented:
@@ -121,11 +121,14 @@ configuration options.
 
 ### Other Changes
 
+- feat: Ensure `withActiveSpan` is exported everywhere (#10878)
 - feat: Allow passing `null` to `withActiveSpan` (#10717)
 - feat: Implement new Async Context Strategy (#10647)
 - feat: Remove `hub` from global, `hub.run` & hub utilities (#10718)
 - feat: Update default trace propagation targets logic in the browser (#10621)
+- feat: Ignore ResizeObserver and undefined error (#10845)
 - feat(browser): Export `getIsolationScope` and `getGlobalScope` (#10658)
+- feat(browser): Prevent initialization in browser extensions (#10844)
 - feat(core): Add metric summaries to spans (#10554)
 - feat(core): Decouple metrics aggregation from client (#10628)
 - feat(core): Lookup client on current scope, not hub (#10635)
@@ -210,6 +213,8 @@ We have also removed or updated a variety of deprecated APIs.
 - feat(v8/node): Remove deepReadDirSync export (#10564)
 - feat(v8/node): Remove deprecated anr methods (#10562)
 - feat(v8/node): Remove getModuleFromFilename export (#10754)
+- feat(core): Remove deprecated props from `Span` interface (#10854)
+- fix(v8): Remove deprecated tracing config (#10870)
 - ref: Make `setupOnce` optional in integrations (#10729)
 - ref: Migrate transaction source from metadata to attributes (#10674)
 - ref: Refactor remaining `makeMain` usage (#10713)
@@ -224,6 +229,53 @@ We have also removed or updated a variety of deprecated APIs.
 - ref: Remove usage of span tags (#10808)
 - ref: Remove user segment (#10575)
 
+## 7.105.0
+
+### Important Changes
+
+- **feat: Ensure `withActiveSpan` is exported everywhere (#10877)**
+
+You can use the `withActiveSpan` method to ensure a certain span is the active span in a given callback. This can be
+used to create a span as a child of a specific span with the `startSpan` API methods:
+
+```js
+const parentSpan = Sentry.startInactiveSpan({ name: 'parent' });
+if (parentSpan) {
+  withActiveSpan(parentSpan, () => {
+    // This will be a direct child of parentSpan
+    const childSpan = Sentry.startInactiveSpan({ name: 'child' });
+  });
+}
+```
+
+## 7.104.0
+
+### Important Changes
+
+- **feat(performance): create Interaction standalone spans on inp events (#10709)**
+
+This release adds support for the INP web vital. This is currently only supported for Saas Sentry, and product support
+is released with the upcoming `24.3.0` release of self-hosted.
+
+To opt-in to this feature, you can use the `enableInp` option in the `browserTracingIntegration`:
+
+```js
+Sentry.init({
+  integrations: [
+    Sentry.browserTracingIntegration({
+      enableInp: true,
+    });
+  ]
+})
+```
+
+### Other Changes
+
+- feat(feedback): Flush replays when feedback form opens (#10567)
+- feat(profiling-node): Expose `nodeProfilingIntegration` (#10864)
+- fix(profiling-node): Fix dependencies to point to current versions (#10861)
+- fix(replay): Add `errorHandler` for replayCanvas integration (#10796)
+
 ## 7.103.0
 
 ### Important Changes