meta(changelog): Update changelog for 9.13.0 #16078
Merged
Conversation
This file contains hidden or 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
[Gitflow] Merge master into develop
In cases where we tweak the options we pass to the instrumentation, our code did not handle this very well. This could lead to certain options missing when init is called again later, as we updated the config with incomplete/wrong options. To fix this properly, I added a new variant to `generateInstrumentOnce` which accepts a class and an options transformer, which ensures that the options are always correctly transformed, no matter if called the first or second time. (The code to make this overloaded `generateInstrumentOnce` function work with TS was pretty tricky, but I think it is good now - type inferral etc. works nicely now!) Fixes #16004
We should run `beforeSendLog` after we do processing to logs to add relevant attributes. This ensures that users can control or mutate things like `sentry.message.template` if they so wish.
…vercel-edge (#16024) resolves #15439 resolves #4532 resolves https://linear.app/getsentry/issue/JSC-192 Supercedes #16021 Our console instrumentation was always inconsistent, but adding breadcrumbs should not really be. This PR adds a unified console instrumentation to `@sentry/core`, and makes the Node SDK use that. We also add this to the `vercel-edge` and `cloudflare` SDKs. I also left todo comments in the deno and browser SDKs for us to unify into this single integration afterwards. --------- Co-authored-by: Francesco Gringl-Novy <[email protected]>
This PR adds a extra callback to the offline transport that allows delaying sending of envelopes. This callback has existed in the Electron offline transport for a couple of major versions.
Supercedes #15978 resolves #15941 resolves #15827 resolves #15816 Bun recently updated their `Bun.serve` API with new functionality, which unfortunately broke our existing instrumentation. This is detailed with https://bun.sh/docs/api/http#bun-serve. Specifically, they added a new routing API that looks like so: ```ts Bun.serve({ // `routes` requires Bun v1.2.3+ routes: { // Dynamic routes "/users/:id": req => { return new Response(`Hello User ${req.params.id}!`); }, // Per-HTTP method handlers "/api/posts": { GET: () => new Response("List posts"), POST: async req => { const body = await req.json(); return Response.json({ created: true, ...body }); }, }, // Wildcard route for all routes that start with "/api/" and aren't otherwise matched "/api/*": Response.json({ message: "Not found" }, { status: 404 }), // Redirect from /blog/hello to /blog/hello/world "/blog/hello": Response.redirect("/blog/hello/world"), // Serve a file by buffering it in memory "/favicon.ico": new Response(await Bun.file("./favicon.ico").bytes(), { headers: { "Content-Type": "image/x-icon", }, }), }, // (optional) fallback for unmatched routes: // Required if Bun's version < 1.2.3 fetch(req) { return new Response("Not Found", { status: 404 }); }, }); ``` Because there are now dynamic routes and wildcard routes, we can actually generate `route` transaction source and send parameterized routes to Sentry. The `fetch` API is still supported. The only API we don't support is [static routes/responses](https://bun.sh/docs/api/http#static-responses). This is because these are optimized by Bun itself, and if we turn it into a function (which we need to do to time it), we'll lose out on the optimization. For now they aren't instrumented.
Closes #16040 this logs a warning if a user adds multiple instances of `browserTracingIntegration`. If this is done, this can lead to potentially weird things (e.g. we add multiple handlers etc). This is especially relevant for react, as there are multiple different integrations there that users may add.
…rom `@modelcontextprotocol/sdk` (#16032)
…6034) Continuation of #14474 As the store logic changed a bit, I changed the PR a bit. The `getAllStores` function can now receive the `stateTransformer` and apply it. Closes #14441 --------- Co-authored-by: Olivier Savignac <[email protected]>
resolves https://linear.app/getsentry/issue/JS-4 resolves #15953 This PR adds support for winston, a popular logging library for Node.js. Specifically you can send logs via winston to Sentry. Usage: ```js const winston = require('winston'); const Transport = require('winston-transport'); const transport = Sentry.createSentryWinstonTransport(Transport); const logger = winston.createLogger({ transports: [transport], }); ``` `createSentryWinstonTransport` was used because we didn't want to add `winston` as a dependency to the nodejs sdk.
…ges/node-integration-tests (#16059) Bumps [@nestjs/common](https://github.com/nestjs/nest/tree/HEAD/packages/common) from 10.4.6 to 11.0.16. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/nestjs/nest/releases"><code>@nestjs/common</code>'s releases</a>.</em></p> <blockquote> <h2>v11.0.16 (2025-04-11)</h2> <ul> <li>fix(common): use <code>file-type</code> to validate file mimetypes by <a href="https://github.com/Chathula"><code>@Chathula</code></a> in <a href="https://redirect.github.com/nestjs/nest/pull/14881">nestjs/nest#14881</a></li> </ul> <h2>v11.0.15 (2025-04-10)</h2> <h4>Bug fixes</h4> <ul> <li><code>platform-fastify</code> <ul> <li><a href="https://redirect.github.com/nestjs/nest/pull/14935">#14935</a> fix(fastify): methods comparison (<a href="https://github.com/johaven"><code>@johaven</code></a>)</li> </ul> </li> </ul> <h4>Committers: 1</h4> <ul> <li>Johan Legrand (<a href="https://github.com/johaven"><code>@johaven</code></a>)</li> </ul> <h2>v11.0.14 (2025-04-09)</h2> <h4>Bug fixes</h4> <ul> <li><code>platform-fastify</code> <ul> <li><a href="https://redirect.github.com/nestjs/nest/pull/14511">#14511</a> fix(fastify): adds the non-standard http methods to the instance (<a href="https://github.com/johaven"><code>@johaven</code></a>)</li> </ul> </li> </ul> <h4>Committers: 1</h4> <ul> <li>Johan Legrand (<a href="https://github.com/johaven"><code>@johaven</code></a>)</li> </ul> <h2>v11.0.13 (2025-04-03)</h2> <h4>Bug fixes</h4> <ul> <li><code>platform-fastify</code> <ul> <li><a href="https://redirect.github.com/nestjs/nest/pull/14895">#14895</a> fix(fastify-adapter): global prefix exclusion path handling w/middleware (<a href="https://github.com/KyleLilly"><code>@KyleLilly</code></a>)</li> </ul> </li> <li><code>microservices</code> <ul> <li><a href="https://redirect.github.com/nestjs/nest/pull/14869">#14869</a> fix(microservices): do not re-create client connection once get client by service name (<a href="https://github.com/mingo023"><code>@mingo023</code></a>)</li> </ul> </li> </ul> <h4>Dependencies</h4> <ul> <li><code>platform-express</code> <ul> <li><a href="https://redirect.github.com/nestjs/nest/pull/14883">#14883</a> fix(deps): update dependency express to v5.1.0 (<a href="https://github.com/apps/renovate"><code>@renovate[bot]</code></a>)</li> <li><a href="https://redirect.github.com/nestjs/nest/pull/14817">#14817</a> fix(deps): update dependency multer to v1.4.5-lts.2 (<a href="https://github.com/apps/renovate"><code>@renovate[bot]</code></a>)</li> </ul> </li> <li><code>platform-fastify</code> <ul> <li><a href="https://redirect.github.com/nestjs/nest/pull/14861">#14861</a> fix(deps): update dependency fastify to v5.2.2 (<a href="https://github.com/apps/renovate"><code>@renovate[bot]</code></a>)</li> <li><a href="https://redirect.github.com/nestjs/nest/pull/14864">#14864</a> chore(deps): bump <code>@fastify/cors</code> from 11.0.0 to 11.0.1 (<a href="https://github.com/apps/dependabot"><code>@dependabot[bot]</code></a>)</li> </ul> </li> </ul> <h4>Committers: 2</h4> <ul> <li>Kyle Lilly (<a href="https://github.com/KyleLilly"><code>@KyleLilly</code></a>)</li> <li>Minh Ngo (<a href="https://github.com/mingo023"><code>@mingo023</code></a>)</li> </ul> <h2>v11.0.12 (2025-03-19)</h2> <h4>Bug fixes</h4> <ul> <li><code>core</code> <ul> <li><a href="https://redirect.github.com/nestjs/nest/pull/14803">#14803</a> fix(core): infinite loop on broken circular reference (<a href="https://github.com/kamilmysliwiec"><code>@kamilmysliwiec</code></a>)</li> <li><a href="https://redirect.github.com/nestjs/nest/pull/14792">nestjs/nest#14792</a> dependencies not resolving for request-scoped lazy providers (<a href="https://github.com/anizozina"><code>@anizozina</code></a>)</li> </ul> </li> </ul> <h4>Enhancements</h4> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/nestjs/nest/commit/b6edf9ada7c6436cc978978a6e1892e44b815b98"><code>b6edf9a</code></a> chore(<a href="https://github.com/nestjs"><code>@nestjs</code></a>) publish v11.0.16 release</li> <li><a href="https://github.com/nestjs/nest/commit/ab79c566fd71e1a33ab47f79288a5f302e0124ef"><code>ab79c56</code></a> chore: minor tweaks</li> <li><a href="https://github.com/nestjs/nest/commit/dcc177a133c51f0a23a98667f7e23209a8327531"><code>dcc177a</code></a> Update packages/common/pipes/file/file-type.validator.ts</li> <li><a href="https://github.com/nestjs/nest/commit/e019da86a19b209cc3ec8740a53ea08fde42669a"><code>e019da8</code></a> refactor(common): move back file type validator options type</li> <li><a href="https://github.com/nestjs/nest/commit/4718a648eb2069674ab592202ff682fc271b4057"><code>4718a64</code></a> chore(<a href="https://github.com/nestjs"><code>@nestjs</code></a>) publish v11.0.15 release</li> <li><a href="https://github.com/nestjs/nest/commit/b6078fd923ac5eaf4e88c1a85a5d8ba497d2b70e"><code>b6078fd</code></a> refactor(common): move file-type package to peer dependencies</li> <li><a href="https://github.com/nestjs/nest/commit/f34ef9a79361c25093556d3fa6d9774cb59dc88b"><code>f34ef9a</code></a> refactor(common): refactor code to use simple eval</li> <li><a href="https://github.com/nestjs/nest/commit/3ff90244c72887377ad1dbe4e6b36cd00625a83c"><code>3ff9024</code></a> fix(common): used eval import</li> <li><a href="https://github.com/nestjs/nest/commit/63d28bf1bcf9c72a5dd36d2795edef08f6675695"><code>63d28bf</code></a> refactor(common): removed async keyword</li> <li><a href="https://github.com/nestjs/nest/commit/5243fca1dc4583f5572cdf5a61e75c0b2354982c"><code>5243fca</code></a> fix(common): update file mime package and add param skip magic numbers</li> <li>Additional commits viewable in <a href="https://github.com/nestjs/nest/commits/v11.0.16/packages/common">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>
Bumps [@sentry/webpack-plugin](https://github.com/getsentry/sentry-javascript-bundler-plugins) from 3.2.4 to 3.3.1. <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.3.1</h2> <ul> <li>fix(webpack5): All <code>esm</code> files must have <code>.mjs</code> postfix (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/721">#721</a>)</li> </ul> <h2>3.3.0</h2> <ul> <li>feat(webpack): Add <code>@sentry/webpack-plugin/webpack5</code> export for webpack 5.1+ and compatible environments (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/715">#715</a>)</li> <li>feat: Only do automatic commit association for Vercel production environments (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/711">#711</a>)</li> </ul> <h2>3.3.0-alpha.1</h2> <p>Pre-release to test primitive APIs.</p> <h2>3.3.0-alpha.0</h2> <p>Pre-release to test primitive APIs.</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.3.1</h2> <ul> <li>fix(webpack5): All <code>esm</code> files must have <code>.mjs</code> postfix (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/721">#721</a>)</li> </ul> <h2>3.3.0</h2> <ul> <li>feat(webpack): Add <code>@sentry/webpack-plugin/webpack5</code> export for webpack 5.1+ and compatible environments (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/715">#715</a>)</li> <li>feat: Only do automatic commit association for Vercel production environments (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/711">#711</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/ecb826d7dd72693434c7e43218889a3d54e8ab3b"><code>ecb826d</code></a> release: 3.3.1</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/6f232ac1f71c9f5cf8a0ce7abd4d55fac8c03fa8"><code>6f232ac</code></a> fix(webpack5): Ensure all <code>esm</code> files have <code>.mjs</code> postfix (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/721">#721</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/abca2b099cc2e79bf275bcda2b2a0b2d4745ea19"><code>abca2b0</code></a> Merge branch 'release/3.3.0'</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/29d15bc7817b542c52514ca7972a383a72c222c2"><code>29d15bc</code></a> release: 3.3.0</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/8a4d4cb1d08749b5dafadb7a0ef46394be965466"><code>8a4d4cb</code></a> meta(changelog): Add missing feature entry for 3.3.0 release (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/720">#720</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/45cf007acfbb1791ae6d8864f9e6e2ca45d7522f"><code>45cf007</code></a> meta(changelog): Add 3.3.0 release (<a href="https://redirect.github.com/getsentry/sentry-javascript-bundler-plugins/issues/719">#719</a>)</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/f577a472b687f4b7e76c15833b5d31f3e5ea2ef4"><code>f577a47</code></a> feat(webpack): Add <code>sentry/webpack-plugin/webpack5</code> export for webpack 5.1+ a...</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/95e5cca323e67d535993ef7bf1985d645b3c38e7"><code>95e5cca</code></a> feat: Only do automatic commit association for Vercel production environments...</li> <li><a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/commit/109a52a52c455940ce32a41f8071536463ea8e7c"><code>109a52a</code></a> Merge branch 'release/3.2.4'</li> <li>See full diff in <a href="https://github.com/getsentry/sentry-javascript-bundler-plugins/compare/3.2.4...3.3.1">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>
This updates the bug issue template labels as well as their mapping to labels to make this work nicer with linear. --------- Co-authored-by: Charly Gomez <[email protected]>
…16074) See https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.1.0. the rabbitmq image v4.1.0 requires this new amqlib version to work. ## Quote of braking changes in rabbitmq 4.1.0 Before a client connection can negotiate a maximum frame size (frame_max), it must authenticate successfully. Before the authenticated phase, a special lower frame_max value is used. With this release, the value was increased from the original 4096 bytes to 8192 to accommodate larger [JWT tokens](https://www.rabbitmq.com/docs/oauth2). Clients that do override frame_max now must use values of 8192 bytes or greater. We recommend using the default server value of 131072: do not override the frame_max key in rabbitmq.conf and do not set it in the application code. [amqplib](https://github.com/amqp-node/amqplib/) is a popular client library that has been using a low frame_max default of 4096. Its users must [upgrade to a compatible version](https://github.com/amqp-node/amqplib/blob/main/CHANGELOG.md#v0107) (starting with 0.10.7) or explicitly use a higher frame_max.
AbhiPrasad
requested review from
a team,
stephanie-anderson and
s1gr1d
and removed request for
a team
size-limit report 📦
|
Lms24
approved these changes
Apr 16, 2025
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.
Awesome release that includes support for Winston logger, MCP support, new Bun SDK features, Cloudflare console instrumentation, and a bunch of other fixes and features.