meta: Update changelog for 9.2.0 #15454
Draft
+5,939
−758
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Migrates the prisma tests to use the `withDockerCompose` option on the test runner. This means: - Docker is only required if you're running tests that actually use docker - Containers are automatically cleaned up after tests complete
…ting (#15408) While submitting feedback the Submit and Cancel buttons previously remained active. So you could smash that submit many times and submit many duplicate feedbacks. This disabled the buttons while the network request is being fired off. The disabled buttons are slightly grayed out by the browser. So it depends on what custom color you've picked: 
After moving to setup docker via the test runner, the tests became flakey. This PR extends the timeouts.
[Gitflow] Merge master into develop
Removes all references to typedocs (http://getsentry.github.io/sentry-javascript/) as this page has been deleted.
Link spans which are related. Example:
```javascript
const span1 = startInactiveSpan({ name: 'span1' });
startSpan({ name: 'span2' }, span2 => {
span2.addLink({
context: span1.spanContext(),
attributes: { 'sentry.link.type': 'previous_trace' },
});
```
… params or fragments (#15404) This patch fixes an oversight with our `fetch` instrumentation in the core package and the browser XHR instrumentation. We didn't strip query params and URL hash fragments from the span name (description) of `http.client` spans. With this fix, the span description now only contains the URL protocol, host and path as defined in our [develop specification](https://develop.sentry.dev/sdk/expected-features/data-handling/#spans).
…tests/test-applications/node-profiling-esm (#15366) Bumps [esbuild](https://github.com/evanw/esbuild) from 0.20.0 to 0.25.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/evanw/esbuild/releases">esbuild's releases</a>.</em></p> <blockquote> <h2>v0.25.0</h2> <p><strong>This release deliberately contains backwards-incompatible changes.</strong> To avoid automatically picking up releases like this, you should either be pinning the exact version of <code>esbuild</code> in your <code>package.json</code> file (recommended) or be using a version range syntax that only accepts patch upgrades such as <code>^0.24.0</code> or <code>~0.24.0</code>. See npm's documentation about <a href="https://docs.npmjs.com/cli/v6/using-npm/semver/">semver</a> for more information.</p> <ul> <li> <p>Restrict access to esbuild's development server (<a href="https://github.com/evanw/esbuild/security/advisories/GHSA-67mh-4wv8-2f99">GHSA-67mh-4wv8-2f99</a>)</p> <p>This change addresses esbuild's first security vulnerability report. Previously esbuild set the <code>Access-Control-Allow-Origin</code> header to <code>*</code> to allow esbuild's development server to be flexible in how it's used for development. However, this allows the websites you visit to make HTTP requests to esbuild's local development server, which gives read-only access to your source code if the website were to fetch your source code's specific URL. You can read more information in <a href="https://github.com/evanw/esbuild/security/advisories/GHSA-67mh-4wv8-2f99">the report</a>.</p> <p>Starting with this release, <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS">CORS</a> will now be disabled, and requests will now be denied if the host does not match the one provided to <code>--serve=</code>. The default host is <code>0.0.0.0</code>, which refers to all of the IP addresses that represent the local machine (e.g. both <code>127.0.0.1</code> and <code>192.168.0.1</code>). If you want to customize anything about esbuild's development server, you can <a href="https://esbuild.github.io/api/#serve-proxy">put a proxy in front of esbuild</a> and modify the incoming and/or outgoing requests.</p> <p>In addition, the <code>serve()</code> API call has been changed to return an array of <code>hosts</code> instead of a single <code>host</code> string. This makes it possible to determine all of the hosts that esbuild's development server will accept.</p> <p>Thanks to <a href="https://github.com/sapphi-red"><code>@sapphi-red</code></a> for reporting this issue.</p> </li> <li> <p>Delete output files when a build fails in watch mode (<a href="https://redirect.github.com/evanw/esbuild/issues/3643">#3643</a>)</p> <p>It has been requested for esbuild to delete files when a build fails in watch mode. Previously esbuild left the old files in place, which could cause people to not immediately realize that the most recent build failed. With this release, esbuild will now delete all output files if a rebuild fails. Fixing the build error and triggering another rebuild will restore all output files again.</p> </li> <li> <p>Fix correctness issues with the CSS nesting transform (<a href="https://redirect.github.com/evanw/esbuild/issues/3620">#3620</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/3877">#3877</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/3933">#3933</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/3997">#3997</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/4005">#4005</a>, <a href="https://redirect.github.com/evanw/esbuild/pull/4037">#4037</a>, <a href="https://redirect.github.com/evanw/esbuild/pull/4038">#4038</a>)</p> <p>This release fixes the following problems:</p> <ul> <li> <p>Naive expansion of CSS nesting can result in an exponential blow-up of generated CSS if each nesting level has multiple selectors. Previously esbuild sometimes collapsed individual nesting levels using <code>:is()</code> to limit expansion. However, this collapsing wasn't correct in some cases, so it has been removed to fix correctness issues.</p> <pre lang="css"><code>/* Original code */ .parent { > .a, > .b1 > .b2 { color: red; } } <p>/* Old output (with --supported:nesting=false) */<br /> .parent > :is(.a, .b1 > .b2) {<br /> color: red;<br /> }</p> <p>/* New output (with --supported:nesting=false) */<br /> .parent > .a,<br /> .parent > .b1 > .b2 {<br /> color: red;<br /> }<br /> </code></pre></p> <p>Thanks to <a href="https://github.com/tim-we"><code>@tim-we</code></a> for working on a fix.</p> </li> <li> <p>The <code>&</code> CSS nesting selector can be repeated multiple times to increase CSS specificity. Previously esbuild ignored this possibility and incorrectly considered <code>&&</code> to have the same specificity as <code>&</code>. With this release, this should now work correctly:</p> <pre lang="css"><code>/* Original code (color should be red) */ </code></pre> </li> </ul> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/evanw/esbuild/blob/main/CHANGELOG-2024.md">esbuild's changelog</a>.</em></p> <blockquote> <h1>Changelog: 2024</h1> <p>This changelog documents all esbuild versions published in the year 2024 (versions 0.19.12 through 0.24.2).</p> <h2>0.24.2</h2> <ul> <li> <p>Fix regression with <code>--define</code> and <code>import.meta</code> (<a href="https://redirect.github.com/evanw/esbuild/issues/4010">#4010</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/4012">#4012</a>, <a href="https://redirect.github.com/evanw/esbuild/pull/4013">#4013</a>)</p> <p>The previous change in version 0.24.1 to use a more expression-like parser for <code>define</code> values to allow quoted property names introduced a regression that removed the ability to use <code>--define:import.meta=...</code>. Even though <code>import</code> is normally a keyword that can't be used as an identifier, ES modules special-case the <code>import.meta</code> expression to behave like an identifier anyway. This change fixes the regression.</p> <p>This fix was contributed by <a href="https://github.com/sapphi-red"><code>@sapphi-red</code></a>.</p> </li> </ul> <h2>0.24.1</h2> <ul> <li> <p>Allow <code>es2024</code> as a target in <code>tsconfig.json</code> (<a href="https://redirect.github.com/evanw/esbuild/issues/4004">#4004</a>)</p> <p>TypeScript recently <a href="https://devblogs.microsoft.com/typescript/announcing-typescript-5-7/#support-for---target-es2024-and---lib-es2024">added <code>es2024</code></a> as a compilation target, so esbuild now supports this in the <code>target</code> field of <code>tsconfig.json</code> files, such as in the following configuration file:</p> <pre lang="json"><code>{ "compilerOptions": { "target": "ES2024" } } </code></pre> <p>As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in <a href="https://esbuild.github.io/content-types/#tsconfig-json">the documentation</a>.</p> <p>This fix was contributed by <a href="https://github.com/billyjanitsch"><code>@billyjanitsch</code></a>.</p> </li> <li> <p>Allow automatic semicolon insertion after <code>get</code>/<code>set</code></p> <p>This change fixes a grammar bug in the parser that incorrectly treated the following code as a syntax error:</p> <pre lang="ts"><code>class Foo { get *x() {} set *y() {} } </code></pre> <p>The above code will be considered valid starting with this release. This change to esbuild follows a <a href="https://redirect.github.com/microsoft/TypeScript/pull/60225">similar change to TypeScript</a> which will allow this syntax starting with TypeScript 5.7.</p> </li> <li> <p>Allow quoted property names in <code>--define</code> and <code>--pure</code> (<a href="https://redirect.github.com/evanw/esbuild/issues/4008">#4008</a>)</p> <p>The <code>define</code> and <code>pure</code> API options now accept identifier expressions containing quoted property names. Previously all identifiers in the identifier expression had to be bare identifiers. This change now makes <code>--define</code> and <code>--pure</code> consistent with <code>--global-name</code>, which already supported quoted property names. For example, the following is now possible:</p> <pre lang="js"><code></code></pre> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/evanw/esbuild/commit/e9174d671b1882758cd32ac5e146200f5bee3e45"><code>e9174d6</code></a> publish 0.25.0 to npm</li> <li><a href="https://github.com/evanw/esbuild/commit/c27dbebb9e7a55dd9a084dd151dddd840787490e"><code>c27dbeb</code></a> fix <code>hosts</code> in <code>plugin-tests.js</code></li> <li><a href="https://github.com/evanw/esbuild/commit/6794f602a453cf0255bcae245871de120a89a559"><code>6794f60</code></a> fix <code>hosts</code> in <code>node-unref-tests.js</code></li> <li><a href="https://github.com/evanw/esbuild/commit/de85afd65edec9ebc44a11e245fd9e9a2e99760d"><code>de85afd</code></a> Merge commit from fork</li> <li><a href="https://github.com/evanw/esbuild/commit/da1de1bf77a65f06654b49878d9ec4747ddaa21f"><code>da1de1b</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4065">#4065</a>: bitwise operators can return bigints</li> <li><a href="https://github.com/evanw/esbuild/commit/f4e9d19fb20095a98bf40634f0380f6a16be91e7"><code>f4e9d19</code></a> switch case liveness: <code>default</code> is always last</li> <li><a href="https://github.com/evanw/esbuild/commit/7aa47c3e778ea04849f97f18dd9959df88fa0886"><code>7aa47c3</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4028">#4028</a>: minify live/dead <code>switch</code> cases better</li> <li><a href="https://github.com/evanw/esbuild/commit/22ecd306190b8971ec4474b5485266c20350e266"><code>22ecd30</code></a> minify: more constant folding for strict equality</li> <li><a href="https://github.com/evanw/esbuild/commit/4cdf03c03697128044fa8fb76e5c478e9765b353"><code>4cdf03c</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4053">#4053</a>: reordering of <code>.tsx</code> in <code>node_modules</code></li> <li><a href="https://github.com/evanw/esbuild/commit/dc719775b7140120916bd9e6777ca1cb8a1cdc0e"><code>dc71977</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/3692">#3692</a>: <code>0</code> now picks a random ephemeral port</li> <li>Additional commits viewable in <a href="https://github.com/evanw/esbuild/compare/v0.20.0...v0.25.0">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/getsentry/sentry-javascript/network/alerts). </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
This PR adds the possibility to add a `links` array that can be passed to the span options at creation of the span.
) Filters out an unactionable error thrown by the Facebook Mobile browser web view. Closes #15065
Bump profiling chunk interval to 60s as per [spec](https://www.notion.so/sentry/Continuous-UI-Profiling-SDK-API-Spec-17e8b10e4b5d80c59a40c6e114470934)
Bumps [@sentry/webpack-plugin](https://github.com/getsentry/sentry-javascript-bundler-plugins) from 2.22.7 to 3.1.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/releases"><code>@sentry/webpack-plugin</code>'s releases</a>.</em></p> <blockquote> <h2>3.1.2</h2> <ul> <li>deps: Bump <code>@sentry/cli</code> to <code>2.41.1</code> (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/671">#671</a>)</li> </ul> <h2>3.1.1</h2> <ul> <li> <p>fix(core): Disable release creation and source maps upload in dev mode (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/666">#666</a>)</p> <p>This fix disables any external calls to the Sentry API for managing releases or uploading source maps, when detecting that the plugin is running in dev-mode. While this rarely actually happened, it also polluted the dev server output with unnecessary logs about missing auth tokens, which shouldn't be required in dev mode.</p> </li> </ul> <h2>3.1.0</h2> <ul> <li>feat(webpack): Gate forced process exit behind experimental flag (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/663">#663</a>)</li> </ul> <h2>3.0.0</h2> <h3>Breaking Changes</h3> <ul> <li> <p>Injected code will now use <code>let</code>, which was added in ES6 (ES2015). This means that ES6 is the minimum JavaScript version that the Sentry bundler plugins support.</p> </li> <li> <p>Deprecated options have been removed:</p> <ul> <li><code>deleteFilesAfterUpload</code> - Use <code>filesToDeleteAfterUpload</code> instead</li> <li><code>bundleSizeOptimizations.excludePerformanceMonitoring</code> - Use <code>bundleSizeOptimizations.excludeTracing</code> instead</li> <li><code>_experiments.moduleMetadata</code> - Use <code>moduleMetadata</code> instead</li> <li><code>cleanArtifacts</code> - Did not do anything</li> </ul> </li> </ul> <h3>List of Changes</h3> <ul> <li>fix!: Wrap injected code in block-statement to contain scope (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/646">#646</a>)</li> <li>chore!: Remove deprecated options (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/654">#654</a>)</li> <li>feat(logger): Use console methods respective to log level (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/652">#652</a>)</li> <li>fix(webpack): Ensure process exits when done (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/653">#653</a>)</li> <li>fix: Use correct replacement matcher for <code>bundleSizeOptimizations.excludeTracing</code> (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/644">#644</a>)</li> </ul> <p>Work in this release contributed by <a href="https://github.com/jdelStrother"><code>@jdelStrother</code></a>. Thank you for your contribution!</p> <h2>2.23.0</h2> <ul> <li>chore(deps): bump nanoid from 3.3.6 to 3.3.8 (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/641">#641</a>)</li> <li>feat(core): Detect Railway release name (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/639">#639</a>)</li> <li>feat(core): Write module injections to <code>globalThis</code> (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/636">#636</a>)</li> <li>feat(react-component-annotate): Allow skipping annotations on specified components (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/617">#617</a>)</li> <li>ref(core): Rename release management plugin name (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/647">#647</a>)</li> </ul> <p>Work in this release contributed by <a href="https://github.com/conor-ob"><code>@conor-ob</code></a>. Thank you for your contribution!</p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/blob/main/CHANGELOG.md"><code>@sentry/webpack-plugin</code>'s changelog</a>.</em></p> <blockquote> <h2>3.1.2</h2> <ul> <li>deps: Bump <code>@sentry/cli</code> to <code>2.41.1</code> (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/671">#671</a>)</li> </ul> <h2>3.1.1</h2> <ul> <li> <p>fix(core): Disable release creation and source maps upload in dev mode (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/666">#666</a>)</p> <p>This fix disables any external calls to the Sentry API for managing releases or uploading source maps, when detecting that the plugin is running in dev-mode. While this rarely actually happened, it also polluted the dev server output with unnecessary logs about missing auth tokens, which shouldn't be required in dev mode.</p> </li> </ul> <h2>3.1.0</h2> <ul> <li>feat(webpack): Gate forced process exit behind experimental flag (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/663">#663</a>)</li> </ul> <h2>3.0.0</h2> <h3>Breaking Changes</h3> <ul> <li> <p>Injected code will now use <code>let</code>, which was added in ES6 (ES2015). This means that ES6 is the minimum JavaScript version that the Sentry bundler plugins support.</p> </li> <li> <p>Deprecated options have been removed:</p> <ul> <li><code>deleteFilesAfterUpload</code> - Use <code>filesToDeleteAfterUpload</code> instead</li> <li><code>bundleSizeOptimizations.excludePerformanceMonitoring</code> - Use <code>bundleSizeOptimizations.excludeTracing</code> instead</li> <li><code>_experiments.moduleMetadata</code> - Use <code>moduleMetadata</code> instead</li> <li><code>cleanArtifacts</code> - Did not do anything</li> </ul> </li> </ul> <h3>List of Changes</h3> <ul> <li>fix!: Wrap injected code in block-statement to contain scope (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/646">#646</a>)</li> <li>chore!: Remove deprecated options (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/654">#654</a>)</li> <li>feat(logger): Use console methods respective to log level (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/652">#652</a>)</li> <li>fix(webpack): Ensure process exits when done (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/653">#653</a>)</li> <li>fix: Use correct replacement matcher for <code>bundleSizeOptimizations.excludeTracing</code> (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/644">#644</a>)</li> </ul> <p>Work in this release contributed by <a href="https://github.com/jdelStrother"><code>@jdelStrother</code></a>. Thank you for your contribution!</p> <h2>2.23.0</h2> <ul> <li>chore(deps): bump nanoid from 3.3.6 to 3.3.8 (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/641">#641</a>)</li> <li>feat(core): Detect Railway release name (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/639">#639</a>)</li> <li>feat(core): Write module injections to <code>globalThis</code> (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/636">#636</a>)</li> <li>feat(react-component-annotate): Allow skipping annotations on specified components (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/617">#617</a>)</li> <li>ref(core): Rename release management plugin name (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/647">#647</a>)</li> </ul> <p>Work in this release contributed by <a href="https://github.com/conor-ob"><code>@conor-ob</code></a>. Thank you for your contribution!</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/900341064e20483c1dd4fd58a194544f2d2da14a"><code>9003410</code></a> release: 3.1.2</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/1063e0a2cd1093a7a33446b3930e6e77a43d2c0c"><code>1063e0a</code></a> meta: Update changelog for <code>3.1.2</code> (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/672">#672</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/cfb6fcc12b9900398c9f2c2643bf3ea6969fdcc9"><code>cfb6fcc</code></a> deps: Bump <code>@sentry/cli</code> to <code>2.41.1</code> (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/671">#671</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/27626a3688c32d92b87583f89a6217ff55ed8f3f"><code>27626a3</code></a> Merge branch 'release/3.1.1'</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/0db92f683ab0a4952e6d1b32e75a43d938c2d52b"><code>0db92f6</code></a> release: 3.1.1</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/8cdc739c168e66c1e85d6155ad15eb8516a44c0a"><code>8cdc739</code></a> meta: Add Changelog for 3.1.1 (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/668">#668</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/d39f50ebbcb9f2ea8743ce5aa13acf9c4a2dbbc6"><code>d39f50e</code></a> fix(core): Check for dev mode via <code>process.env.NODE_ENV</code> (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/666">#666</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/071fd5cc0b2d46c977df30b2d4fa08a52694415a"><code>071fd5c</code></a> Merge branch 'release/3.1.0'</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/b2f807b2192ab965747301a06b5ecf6948ee72ef"><code>b2f807b</code></a> release: 3.1.0</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/d57886dc724863669cb5c951cd055495b4cc5cb5"><code>d57886d</code></a> meta: Update changelog for 3.1.0 (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/664">#664</a>)</li> <li>Additional commits viewable in <a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/compare/2.22.7...3.1.2">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
We actually have a concrete type for the `init` on the server-side. However, this type was not used so far. Additionally, I removed the `Omit` of `'app'` as there is no `'app'` on the Node types anyway.
The Nuxt SDK also uses the preview command to determine where to put the Sentry top-level import. Like this: `node .output/server/index.mjs` (would add Sentry to `index.mjs`) However, the function to get the file name also used folder names without file extensions which led to Sentry not being included at the top of the index file. This was a problem in e.g. Azure as the command is the following: `npx @azure/static-web-apps-cli start ./public --api-location ./server`
#14916) Closes #14809. I have tested this with my project and it sort of works. While it's not perfect (sometimes produces an unplayable replay), it might unblock other users looking to experiment with this feature. Verify: - [ ] If you've added code that should be tested, please add tests. - [x] Ensure your code lints and the test suite passes (`yarn lint`) & (`yarn test`). This just exposes the API under experiments, as such I don't think it requires tests. --------- Co-authored-by: Billy Vong <[email protected]>
…tting (#15440) - read sourcemap generation config in `config` hook of our source maps settings sub plugin - resolve the `filesToDeleteAfterUpload` promise whenever we know what to set it to (using a promise allows us to defer this decision to plugin hook runtime rather than plugin creation time) - adusted tests
These types were moved to `@sentry-internal/node-cpu-profiler` but I didn't remove them here during the migration.
The goal is for Express to eventually support publishing events to `diagnostics_channel` (#15107) so that Open Telemetry can instrument it without monkey-patching internal code. However, this might take a while and it would be great to support Express v5 now. This PR is a stop-gap solution until that work is complete and published. This PR vendors the code added in my otel PR: - open-telemetry/opentelemetry-js-contrib#2437 - Adds a new instrumentation specifically for hooking express v5 - Copies the Express v4 integration tests to test v5 - The only changes in the tests is the removal of a couple of complex regex tests where the regexes are no longer supported by Express. - Modifies the NestJs v11 tests which now support full Express spans
Update remix readme to use the proper integrations reference for Prisma.
Extends the basic SDK test to ensure the metadata is correct and that we get the expected exception.
This PR adds the external contributor to the CHANGELOG.md file, so that they are credited for their contribution. See #15346 Co-authored-by: AbhiPrasad <[email protected]>
Co-authored-by: Abhijeet Prasad <[email protected]>
AbhiPrasad
force-pushed
the
prepare-release/9.2.0
branch
from
d79f85d to
fc46859
Compare
2 tasks
This patch adds a different set of package exports for workers. To use this, you have to use the new `initCloudflareSentryHandle` SvelteKit handler function, before your call to `sentryHandle()`. --------- Co-authored-by: Lukas Stracke <[email protected]>
attributions more entries correct username
Lms24
force-pushed
the
prepare-release/9.2.0
branch
from
e232230 to
b45cab5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To be released on Monday;