Skip to content

chore: Bump pnpm to 12.21.0 and use the v13 lockfile format - #26421

Closed
sentry-junior[bot] wants to merge 2 commits into
developfrom
chore/pnpm-lockfile-v13
Closed

sentry-junior[bot] wants to merge 2 commits into
developfrom
chore/pnpm-lockfile-v13

Conversation

@sentry-junior

@sentry-junior sentry-junior Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

What

Bumps pnpm from 12.11.2 to 12.21.0 and sets lockfile.format: v13, so pnpm-lock.yaml is now written in the experimental pnpm 13 format (tab-indented JSON that is still valid YAML, lockfileVersion: '13.0'). It resolves to the same 3464 package versions as before; only the file format changes.

Why

The v13 format has one entry per package version and no peer-suffixed keys, so a peer dependency bump only touches the lines that record it instead of rewriting large parts of the lockfile. lockfile.format landed in 12.19.0, and 12.20/12.21 fix several v13 write and frozen-install bugs, so this uses the latest 12.x.

Notes:

  • Nx 24 fails to parse the v13 lockfile (Failed to parse pnpm lockfile), which broke every nx command. nx.json now sets analyzeLockfile: false for @nx/js. Workspace project dependencies come from package.json, and pnpm-lock.yaml is already a shared global input, so the project graph (64 projects, 244 edges) is identical to develop. analyzeSourceFiles: false keeps the current default, which setting pluginsConfig would otherwise flip.
  • The leading boot document (pinned pnpm) stays in the v9 format while the project pins pnpm ≤13, as documented. pnpm 12 no longer pins @pnpm/exe there.
  • The format is experimental and may change before pnpm 13, so a later pnpm may need to regenerate the lockfile.
  • Open question: Dependabot (daily npm updates and security alerts) parses pnpm-lock.yaml and probably does not understand v13 yet. That should be checked before this merges.

via @msonnb.

--

View Session [Sentry]

Co-Authored-By: Martin Sonnberger <26038247+msonnb@users.noreply.github.com>
Nx 24 cannot parse the v13 lockfile format. Workspace project dependencies come from package.json, and the lockfile is already a shared global input, so the project graph is unchanged.
@semgrep-code-getsentry

Copy link
Copy Markdown

Semgrep found 1 ssc-9e16049c-d627-4ef3-9759-3139101c4fa9 finding:

🟡 Medium severity issue identified in your code:

Risk: Affected versions of @babel/helpers, @babel/runtime, @babel/runtime-corejs2, and @babel/runtime-corejs3 are vulnerable to Inefficient Regular Expression Complexity. Babel generates a polyfill (the wrapRegExp helper) for String.prototype.replace on regular expressions with named capturing groups that has quadratic (ReDoS) complexity when an untrusted replacement string containing the substring $< is processed. The vulnerable code is generated polyfill code rather than a symbol you call directly, so any project transpiling named capturing groups against affected browser targets is at risk. Upgrade to a patched version and recompile your code to remediate.

Fix: Upgrade this library to at least version 7.26.10 at sentry-javascript/pnpm-lock.yaml:9321.

Reference(s): https://euvd.enisa.europa.eu/vulnerability/EUVD-2025-7806, GHSA-968p-4wvh-cqc8, CVE-2025-27789

Semgrep found 3 ssc-90df8fd1-2d4f-4e7b-a8aa-dfa15f51f5bf findings:

🟡 Medium severity issue identified in your code:

Risk: Affected versions of esbuild are vulnerable to Origin Validation Error. esbuild's development server responds to every request, including Server-Sent Events connections, with Access-Control-Allow-Origin: *. Any website a developer visits can therefore make cross-origin requests to the local dev server and read the responses, leaking bundled source code, source maps, and served file paths. Starting the dev server via serve() reaches the vulnerable code path.

Manual Review Advice: A vulnerability from this advisory is reachable if you run esbuild with the --serve flag to start the development server

Fix: Upgrade this library to at least version 0.25.0 at sentry-javascript/pnpm-lock.yaml:25791.

Reference(s): GHSA-67mh-4wv8-2f99

Semgrep found 1 ssc-c8b7a1f2-4d36-4f0a-9e2b-1a5c8d7e6f30 finding:

🟡 Medium severity issue identified in your code:

Risk: Affected versions of vite and vite-plus are vulnerable to Exposure of Sensitive Information to an Unauthorized Actor / Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'). Vite's server.fs.deny blocklist—which protects sensitive files such as .env and certificate files from being served—can be bypassed on Windows using alternate path representations (NTFS Alternate Data Stream syntax like /.env::$DATA?raw, or 8.3 short filenames), allowing an attacker to read otherwise-denied files when the dev server is exposed to the network.

Manual Review Advice: A vulnerability from this advisory is reachable if you expose the Vite dev server or vite-plus to the network by configuring a non-loopback address using the --host CLI flag on Windows

Fix: Upgrade this library to at least version 6.4.3 at sentry-javascript/pnpm-lock.yaml:41343.

Reference(s): https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-38303, GHSA-fx2h-pf6j-xcff, CVE-2026-53571

Semgrep found 1 ssc-14373fcb-6df6-4a88-a68b-95bf4fdd53ad finding:

🟡 Medium severity issue identified in your code:

Risk: Affected versions of jsondiffpatch are vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'). jsondiffpatch renders JSON object keys into HTML without escaping in its HTML formatter (HtmlFormatter / format). An attacker who controls the JSON being diffed can inject a malicious object key (e.g. a <script> tag) that executes in the context of the consuming web page (DOM-based XSS).

Manual Review Advice: A vulnerability from this advisory is reachable if you are uisng jsondiffpatch on the CLI

Fix: Upgrade this library to at least version 0.7.2 at sentry-javascript/pnpm-lock.yaml:29656.

Reference(s): https://euvd.enisa.europa.eu/vulnerability/EUVD-2025-27629, GHSA-33vc-wfww-vjfv, CVE-2025-9910

Semgrep found 2 ssc-609dd635-87fa-44a8-af18-b6e58a147de0 findings:

🟡 Medium severity issue identified in your code:

Risk: Affected versions of svelte are vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'). Svelte versions before 4.2.19 improperly escape HTML during server-side rendering (SSR): attribute values only escape & and " but not <. A user-controlled value placed in an element attribute inside a <noscript> element can break out of the attribute/noscript context and inject markup, resulting in cross-site scripting (XSS).

Manual Review Advice: A vulnerability from this advisory is reachable if you use Svelte server-side rendering with a component that places user-controlled data in an element attribute inside a <noscript> element

Fix: Upgrade this library to at least version 4.2.19 at sentry-javascript/pnpm-lock.yaml:38859.

Reference(s): https://euvd.enisa.europa.eu/vulnerability/EUVD-2024-2530, GHSA-8266-84wp-wv5c, CVE-2024-45047

Semgrep found 1 ssc-484bb776-a960-4899-8ddd-675885fe6a95 finding:

🟡 Medium severity issue identified in your code:

Risk: Affected versions of webpack-dev-server are vulnerable to Exposed Dangerous Method or Function. webpack-dev-server serves bundled assets without rejecting cross-origin classic script requests. Because such <script src> requests bypass the same-origin policy, a malicious website visited by a developer running the dev server can load the application bundle cross-origin and, via prototype pollution of the webpack runtime, extract the application source code.

Manual Review Advice: A vulnerability from this advisory is reachable if you are using webpack dev server CLI setup

Fix: Upgrade this library to at least version 5.2.1 at sentry-javascript/pnpm-lock.yaml:42256.

Reference(s): https://euvd.enisa.europa.eu/vulnerability/EUVD-2025-16767, GHSA-4v9v-hfq4-rm2v, CVE-2025-30359

Semgrep found 1 ssc-013ecbde-4597-4af3-bcc3-06920828d5cc finding:

🟡 Medium severity issue identified in your code:

Risk: Affected versions of webpack-dev-server are vulnerable to Origin Validation Error. webpack-dev-server improperly validates the WebSocket connection Origin header, unconditionally accepting any IP-address-based Origin. A malicious website can perform a cross-site WebSocket hijack against a running dev server and exfiltrate the developer source code carried in Hot Module Reloading (HMR) messages. The insecure origin check is the package default and is reached on every WebSocket connection, so any project running an affected version is vulnerable.

Manual Review Advice: A vulnerability from this advisory is reachable if you are using webpack dev server CLI setup and access untrusted web site with non-Chromium based browser

Fix: Upgrade this library to at least version 5.2.1 at sentry-javascript/pnpm-lock.yaml:42256.

Reference(s): https://euvd.enisa.europa.eu/vulnerability/EUVD-2025-16764, GHSA-9jgg-88mc-972h, CVE-2025-30360

Semgrep found 1 ssc-f748ff04-95cd-4e1a-8429-2525a723a048 finding:

🟡 Medium severity issue identified in your code:

Risk: Affected versions of webpack are vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'). webpack's AutoPublicPathRuntimeModule emits runtime code that derives the asset public path from document.currentScript. Because document.currentScript can be DOM-clobbered by an injected scriptless element (e.g. ), an attacker who can inject markup into the page can redirect dynamic chunk/asset loading to an attacker-controlled origin, resulting in cross-site scripting (XSS).

Manual Review Advice: A vulnerability from this advisory is reachable if you build with output.publicPath unset

Fix: Upgrade this library to at least version 5.94.0 at sentry-javascript/pnpm-lock.yaml:42482.

Reference(s): https://euvd.enisa.europa.eu/vulnerability/EUVD-2024-2497, GHSA-4vvj-4cpr-p986, CVE-2024-43788

Semgrep found 13 ssc-9c34c675-756b-44e8-9512-28718930fef2 findings:

🟠 High severity issue identified in your code:

Risk: Affected versions of @cloudflare/workerd-darwin-64, @cloudflare/workerd-darwin-arm64, @cloudflare/workerd-linux-64, @cloudflare/workerd-linux-arm64, @cloudflare/workerd-windows-64, @duckdb/node-api, @duckdb/node-bindings, @duckdb/node-bindings-darwin-arm64, @duckdb/node-bindings-darwin-x64, @duckdb/node-bindings-linux-arm64, @duckdb/node-bindings-linux-arm64-musl, @duckdb/node-bindings-linux-x64, @duckdb/node-bindings-linux-x64-musl, @duckdb/node-bindings-win32-arm64, @duckdb/node-bindings-win32-x64, @napi-rs/canvas, @napi-rs/canvas-linux-arm64-gnu, @napi-rs/canvas-linux-x64-gnu, @napi-rs/canvas-linux-x64-musl, @oven/bun-darwin-aarch64, @oven/bun-darwin-x64, @oven/bun-darwin-x64-baseline, @oven/bun-freebsd-aarch64, @oven/bun-freebsd-x64, @oven/bun-linux-aarch64, @oven/bun-linux-aarch64-android, @oven/bun-linux-aarch64-musl, @oven/bun-linux-x64, @oven/bun-linux-x64-android, @oven/bun-linux-x64-baseline, @oven/bun-linux-x64-musl, @oven/bun-linux-x64-musl-baseline, @oven/bun-windows-aarch64, @oven/bun-windows-x64, @oven/bun-windows-x64-baseline, @skia-canvas/linux-arm64-glibc, @skia-canvas/linux-arm64-musl, @skia-canvas/linux-x64-glibc, @skia-canvas/linux-x64-musl, @sparticuz/chromium, @yao-pkg/pkg-fetch, @zkl2333/freetype-wasm, canvaskit-wasm, chrome-aws-lambda, duckdb, electron, electron-nightly, fonteditor-core, iltorb, kuzu, kuzu-wasm, lbug, node-aix-ppc64, node-darwin-x64, node-libcurl, node-linux-arm64, node-linux-armv7l, node-linux-ppc64le, node-linux-s390x, node-linux-x64, node-sunos-x64, node-win-arm64, node-win-x64, node-win-x86, nodejs-mobile-react-native, pkg-fetch, playwright-chromium, playwright-core, puppeteer, skia-canvas, wawoff2, woff2-encoder, and workerd are vulnerable to Out-of-bounds Write. These packages use a version of the Brotli C library (1.0.3 through 1.2.0) that has an out-of-bounds write in the Brotli decoder. Decoding attacker-controlled Brotli data (for example HTTP responses, request bodies, WOFF2 fonts or Parquet files) can corrupt memory and may lead to denial of service, memory disclosure or remote code execution. Upgrade to a fixed version where one is available.

Fix: Upgrade this library to at least version 1.20261027.1 at sentry-javascript/pnpm-lock.yaml:42813.

Reference(s): https://github.com/advisories/GHSA-cust-0000-0034

Semgrep found 1 ssc-7c41e9a2-3b5d-4f86-9e0a-d12f6b8c4a57 finding:

🟠 High severity issue identified in your code:

Risk: Affected versions of launch-editor, vite, and vite-plus are vulnerable to Improper Neutralization of Special Elements used in a Command ('Command Injection'). launch-editor (bundled by vite and vite-plus for the dev server's /__open-in-editor endpoint) checks fs.existsSync(fileName) before passing the supplied file to the editor command, but the path is resolved (e.g. by launch-editor-middleware) before the :line:column suffix is stripped. On Windows, a crafted path ending in \..:1:1 is reduced to <nonexistent>\.., which fs.existsSync() accepts as the existing parent directory, so the existence check is bypassed without placing any file on disk. Combined with the % escaping issue (GHSA-698v-4r3x-3vcv), an attacker who controls the file argument passed to the default-exported launchEditor function (directly or via launch-editor-middleware) can achieve OS command injection.

Manual Review Advice: A vulnerability from this advisory is reachable if you run the vite or vite-plus dev server (or another tool that mounts launch-editor-middleware) on Windows

Fix: Upgrade this library to at least version 6.4.4 at sentry-javascript/pnpm-lock.yaml:41343.

Reference(s): https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-105035, GHSA-587h-7wmj-h5pm, CVE-2026-112942

Semgrep found 2 ssc-e4c0f25b-1e41-443a-9b72-0fd356011bb1 findings:

🟠 High severity issue identified in your code:

Risk: Affected versions of sharp are vulnerable to Dependency on Vulnerable Third-Party Component / Use After Free. The prebuilt libvips binaries shipped with sharp bundle a vulnerable librsvg that has a use-after-free when decoding SVG images, which can lead to remote code execution when sharp processes an attacker-supplied SVG. Upgrade to sharp 0.35.5 or later, or block SVG decoding with sharp.block({ operation: ["VipsForeignLoadSvg"] }).

Manual Review Advice: A vulnerability from this advisory is reachable if you decode SVG input with sharp, which is enabled by default, and have not disabled it with sharp.block({ operation: ["VipsForeignLoadSvg"] })

Fix: Upgrade this library to at least version 0.35.5 at sentry-javascript/pnpm-lock.yaml:37832.

Reference(s): GHSA-wq5f-xc86-pv6w

Semgrep found 1 ssc-0c6b5f0e-7d1a-4e5b-9a43-2f8d6b1c7e94 finding:

🟠 High severity issue identified in your code:

Risk: Affected versions of webpack-dev-middleware are vulnerable to Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'). When publicPath has no trailing slash (e.g. /assets), a request such as /assets../secret passes the path traversal check before the prefix is stripped, letting an unauthenticated attacker read files outside the output directory served by webpack-dev-middleware. Upgrade, or add a trailing slash to publicPath.

Fix: Upgrade this library to at least version 7.4.6 at sentry-javascript/pnpm-lock.yaml:42238.

Reference(s): https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-64850, GHSA-g84c-rxfj-3j2c, GHSA-wr3j-pwj9-hqq6, CVE-2026-76844

Semgrep found 2 ssc-6ff8e141-404b-4098-a03b-5f0ca3015c76 findings:

🟠 High severity issue identified in your code:

Risk: Affected versions of @angular/compiler and @angular/core are vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'). Angular's compiler internationalization (i18n) pipeline does not reject static event-handler attributes that are marked for translation with the i18n-on* notation (for example <img src="foo.jpg" onerror="void 0" i18n-onerror />). Angular normally blocks binding to onclick, onerror and similar attributes via validateAttribute()/validateProperty(), but the i18n metadata collection path only rejected Trusted Types sinks, so the handler body is taken from the translation unit instead. A translation file can therefore replace a benign handler with arbitrary JavaScript that executes in the origin of the localized application, leading to session hijacking or actions performed on behalf of the authenticated user.

Manual Review Advice: A vulnerability from this advisory is reachable if you are using Angular's i18n pipeline and also set the matching static on<event> handler attribute on the same element

Fix: Upgrade this library to at least version 20.3.27 at sentry-javascript/pnpm-lock.yaml:3742.

Reference(s): https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-52369, GHSA-jj27-h5hq-8x99

Semgrep found 2 ssc-8ec0dd3e-cfd5-4a9b-9479-f5400432931f findings:

🟠 High severity issue identified in your code:

Risk: Affected versions of sharp are vulnerable to Dependency on Vulnerable Third-Party Component. sharp bundles a vulnerable version of the native libvips library, inheriting four memory-safety flaws: an integer overflow leading to a heap-based buffer overflow in the VIPS loader (vipsload, CVE-2026-33327), an integer overflow in the GIF loader (gifload, CVE-2026-33328) causing a denial of service on 32-bit hosts only, a heap-based buffer overflow in the TIFF loader (tiffload, CVE-2026-35591) when handling JPEG or JPEG2000-encoded tiles, and an out-of-bounds read in the EXIF directory decoder (CVE-2026-35590). An attacker who can supply a crafted image can crash the process or corrupt heap memory. Because sharp selects the libvips loader by sniffing the input bytes, no call site can be shown to be safe, and the EXIF flaw is reachable from the JPEG, TIFF, WebP, PNG and HEIF loaders as well. Upgrade to sharp 0.35.0 or later, which bundles libvips 8.18.3. Blocking the affected loaders with sharp.block({ operation: ["VipsForeignLoadNsgif", "VipsForeignLoadTiff", "VipsForeignLoadVips"] }) is only a partial stopgap and does not mitigate the EXIF out-of-bounds read (CVE-2026-35590), for which no workaround exists.

Fix: Upgrade this library to at least version 0.35.0 at sentry-javascript/pnpm-lock.yaml:37832.

Reference(s): GHSA-f88m-g3jw-g9cj

Semgrep found 1 ssc-1d4c2f6e-9b3a-4f0c-8d21-6e5a7c0b9f44 finding:

🟠 High severity issue identified in your code:

Risk: Affected versions of react-router and turbo-stream are vulnerable to Allocation of Resources Without Limits or Throttling. React Router Framework Mode uses turbo-stream to serialize loader/action data into Single Fetch responses. The underlying serialization algorithm becomes a bottleneck on certain data shapes, so an attacker who can influence the serialized data can cause excessive resource consumption and a Denial of Service.

Manual Review Advice: A vulnerability from this advisory is reachable if you use React Router Framework Mode with Single Fetch enabled (the default in v7 Framework Mode, or opt-in via future.unstable_singleFetch in Remix v2.9.0+) and not Declarative or Data mode

Fix: Upgrade this library to at least version 3.0.0 at sentry-javascript/pnpm-lock.yaml:39550.

Reference(s): https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-33994, GHSA-rxv8-25v2-qmq8, CVE-2026-34077

Semgrep found 1 ssc-2427bad3-7619-448f-8f95-70806990606e finding:

🟠 High severity issue identified in your code:

Risk: Affected versions of @angular/compiler are vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'). A stored XSS vulnerability in the Angular Template Compiler arises because its internal security schema doesn't classify certain URL‐ holding attributes (e.g. xlink:href, math|href, annotation|href) or the attributeName binding on SVG animation elements (<animate>, <set>, etc.) as requiring strict URL sanitization. An attacker who can supply untrusted input to template bindings like [attr.xlink:href] or <animate [attributeName]="'href'" [values]="maliciousURL"> can inject a javascript: URL payload. When the element is activated (e.g. clicked) or the animation runs, the malicious script executes in the application's origin, enabling session hijacking, data exfiltration, or unauthorized actions.

Manual Review Advice: A vulnerability from this advisory is reachable if you allow SVG/MathML attributes (e.g., xlink:href, href) or to the attributeName field of SVG animation tags (, , etc.) in HTML templates

Fix: Upgrade this library to at least version 19.2.17 at sentry-javascript/pnpm-lock.yaml:3727.

Reference(s): https://euvd.enisa.europa.eu/vulnerability/EUVD-2025-200118, GHSA-v4hv-rgfq-gp49, CVE-2025-66412

Semgrep found 6 ssc-17eda294-146f-4ed3-91f7-5ef1b349d687 findings:

🔴 Critical severity issue identified in your code:

Risk: Affected versions of @babel/traverse and babel-traverse are vulnerable to Incomplete List of Disallowed Inputs / Incorrect Comparison. Compiling untrusted code with Babel using plugins that invoke the internal path.evaluate() or path.evaluateTruthy() methods (for example @babel/plugin-transform-runtime, @babel/preset-env with useBuiltIns, or any polyfill‐provider plugin) allows a maliciously crafted AST to execute arbitrary code on the build machine during compilation.

Manual Review Advice: A vulnerability from this advisory is reachable if you use Babel to compile untrusted JavaScript

Fix: There are no safe versions of this library available for upgrade. Library included at sentry-javascript/pnpm-lock.yaml:22254.

Reference(s): https://euvd.enisa.europa.eu/vulnerability/EUVD-2023-2669, GHSA-67hx-6x53-jw92, CVE-2023-45133

@github-actions

Copy link
Copy Markdown
Contributor

size-limit report 📦

Compared: 20e308e (PR test merge using develop at 7f77bb2)

Against: 7f77bb2 (develop) · base run #66275

✅ Baseline matches: this diff contains only this PR's changes.

Path Size % Change Change
@sentry/browser 30.1 kB - -
@sentry/browser - with treeshaking flags 28.3 kB - -
@sentry/browser - with treeshaking flags tracing without tracing 28.2 kB - -
@sentry/browser (incl. Tracing) 52.28 kB - -
@sentry/browser (incl. Tracing + Span Streaming) 52.29 kB - -
@sentry/browser (incl. Tracing, Profiling) 55.25 kB - -
@sentry/browser (incl. Tracing, Replay) 92.82 kB - -
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags 81.6 kB - -
@sentry/browser (incl. Tracing, Replay with Canvas) 97.21 kB - -
@sentry/browser (incl. Tracing, Replay, Feedback) 110.6 kB - -
@sentry/browser (incl. Feedback) 47.73 kB - -
@sentry/browser (incl. sendFeedback) 30.69 kB - -
@sentry/browser (incl. FeedbackAsync) 35.69 kB - -
@sentry/browser (incl. Metrics) 31.43 kB - -
@sentry/browser (incl. Logs) 31.71 kB - -
@sentry/browser (incl. Metrics & Logs) 32.37 kB - -
@sentry/react 32.11 kB - -
@sentry/react (incl. Tracing) 54.95 kB - -
@sentry/vue 38.3 kB - -
@sentry/vue (incl. Tracing) 55.24 kB - -
@sentry/svelte 30.12 kB - -
@sentry/remix (Remix 3 client bundle) 58.06 kB - -
CDN Bundle 31.87 kB - -
CDN Bundle (incl. Tracing) 52.7 kB - -
CDN Bundle (incl. Logs, Metrics) 34.67 kB - -
CDN Bundle (incl. Tracing, Logs, Metrics) 55.26 kB - -
CDN Bundle (incl. Replay, Logs, Metrics) 75.7 kB - -
CDN Bundle (incl. Tracing, Replay) 90.72 kB - -
CDN Bundle (incl. Tracing, Replay, Logs, Metrics) 93.33 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback) 96.09 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback, Logs, Metrics) 98.69 kB - -
CDN Bundle - uncompressed 92.98 kB - -
CDN Bundle (incl. Tracing) - uncompressed 155.45 kB - -
CDN Bundle (incl. Logs, Metrics) - uncompressed 101.33 kB - -
CDN Bundle (incl. Tracing, Logs, Metrics) - uncompressed 163.08 kB - -
CDN Bundle (incl. Replay, Logs, Metrics) - uncompressed 231.44 kB - -
CDN Bundle (incl. Tracing, Replay) - uncompressed 275.61 kB - -
CDN Bundle (incl. Tracing, Replay, Logs, Metrics) - uncompressed 283.24 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 287.4 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback, Logs, Metrics) - uncompressed 295.02 kB - -
@sentry/nextjs (client) 58.45 kB - -
@sentry/sveltekit (client) 53.48 kB - -
@sentry/core/server 44.73 kB - -
@sentry/core/browser 14.3 kB - -
@sentry/node 151.32 kB -0.01% -4 B 🔽
@sentry/node/import (ESM hook with diagnostics-channel injection) 83.3 kB - -
@sentry/node - without tracing 88.56 kB -0.01% -5 B 🔽
@sentry/node - without channel injection 140.26 kB -0.01% -5 B 🔽
@sentry/aws-serverless 98.93 kB -0.01% -6 B 🔽
@sentry/cloudflare (withSentry) - minified 205.88 kB - -
@sentry/cloudflare (withSentry) 477.87 kB - -
@sentry/nextjs/cloudflare (withSentry) - minified 231.06 kB - -

View base workflow run

@sentry-junior

sentry-junior Bot commented Nov 16, 2026

Copy link
Copy Markdown
Contributor Author

Re the Semgrep supply-chain findings: these aren't new. This PR doesn't change any resolved versions. Old and new lockfiles have the same 3464 package versions, and @babel/runtime@7.18.9, esbuild@0.15.5/0.15.18/0.21.5, vite@5.4.21 and jsondiffpatch@0.6.0 are all already in develop's pnpm-lock.yaml. Semgrep reports them here because the v13 format rewrites every line of the lockfile. Bumping those dependencies is out of scope for this PR.

@msonnb msonnb closed this Nov 16, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Optional E2E tests

Some optional checks were not successful. They do not block the merge. 3 not successful, 60 successful. See the run.

Check Status
❌ CI: Optional E2E Tests / E2E react-send-to-sentry Test (optional) Failing after 5m Details
❌ CI: Optional E2E Tests / E2E cloudflare-workers-send-to-sentry Test (optional) Failing after 4m Details
❌ CI: Optional E2E Tests / E2E nextjs-16-cacheComponents (cloudflare) Test (optional) Failing after 11m Details
Successful checks
Check Status
✅ CI: Optional E2E Tests / E2E cloudflare-mastra Test (optional) Successful in 53s Details
✅ CI: Optional E2E Tests / E2E solidstart-2 Test (optional) Successful in 59s Details
✅ CI: Optional E2E Tests / E2E node-openai-decisions (latest) Test (optional) Successful in 44s Details
✅ CI: Optional E2E Tests / E2E solidstart-2-tunnel Test (optional) Successful in 41s Details
✅ CI: Optional E2E Tests / E2E astro-7-static Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E cloudflare-flue-send-to-sentry Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E cloudflare-agent Test (optional) Successful in 47s Details
✅ CI: Optional E2E Tests / E2E nuxt-5-sourcemaps Test (optional) Successful in 39s Details
✅ CI: Optional E2E Tests / E2E cloudflare-think (ai v6) Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E node-express-mcp-v1 Test (optional) Successful in 43s Details
✅ CI: Optional E2E Tests / E2E astro-7 Test (optional) Successful in 2m Details
✅ CI: Optional E2E Tests / E2E cloudflare-pi-durable (latest) Test (optional) Successful in 51s Details
✅ CI: Optional E2E Tests / E2E nuxt-5-tunnel Test (optional) Successful in 56s Details
✅ CI: Optional E2E Tests / E2E vue-3 (no Options API) Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E nextjs-16 (vinext, bun) Test (optional) Successful in 2m Details
✅ CI: Optional E2E Tests / E2E supabase-nextjs Test (optional) Successful in 2m Details
✅ CI: Optional E2E Tests / E2E node-mastra (latest) Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E tanstackstart-react-sourcemaps Test (optional) Successful in 29s Details
✅ CI: Optional E2E Tests / E2E nuxt-5 (development) Test (optional) Successful in 56s Details
✅ CI: Optional E2E Tests / E2E nextjs-15 (turbo) Test (optional) Successful in 2m Details
✅ CI: Optional E2E Tests / E2E react-router-7-framework-instrumentation Test (optional) Successful in 2m Details
✅ CI: Optional E2E Tests / E2E tanstackstart-react-cloudflare Test (optional) Successful in 37s Details
✅ CI: Optional E2E Tests / E2E nuxt-5 (kv-cache) Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E cloudflare-pi-durable Test (optional) Successful in 49s Details
✅ CI: Optional E2E Tests / E2E cloudflare-think Test (optional) Successful in 57s Details
✅ CI: Optional E2E Tests / E2E nestjs-12 (deno) Test (optional) Successful in 50s Details
✅ CI: Optional E2E Tests / E2E nuxt-5-cloudflare Test (optional) Successful in 28s Details
✅ CI: Optional E2E Tests / E2E tanstackstart-react (latest) Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E nuxt-5 Test (optional) Successful in 2m Details
✅ CI: Optional E2E Tests / E2E nuxt-5-sourcemaps (client source maps kept) Test (optional) Successful in 55s Details
✅ CI: Optional E2E Tests / E2E node-pi-durable Test (optional) Successful in 38s Details
✅ CI: Optional E2E Tests / E2E node-flue (latest) Test (optional) Successful in 2m Details
✅ CI: Optional E2E Tests / E2E node-flue Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E nextjs-15 (latest) Test (optional) Successful in 3m Details
✅ CI: Optional E2E Tests / E2E node-eve (orchestrion) Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E cloudflare-workers-without-tracing-send-to-sentry Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E nextjs-14 (latest) Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E node-eve (content off, latest) Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E node-eve Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E gen-ai-libraries Test (optional) Successful in 46s Details
✅ CI: Optional E2E Tests / E2E nextjs-16-tunnel (cloudflare) Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E nextjs-16 (cloudflare, latest) Test (optional) Successful in 2m Details
✅ CI: Optional E2E Tests / E2E nestjs-12 (bun) Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E nestjs-12 (latest) Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E node-mastra Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E gen-ai-libraries (latest) Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E debug-id-sourcemaps Test (optional) Successful in 49s Details
✅ CI: Optional E2E Tests / E2E deno (latest) Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E node-pi-durable (latest) Test (optional) Successful in 48s Details
✅ CI: Optional E2E Tests / E2E node-fastify-6 Test (optional) Successful in 43s Details
✅ CI: Optional E2E Tests / E2E nuxt-5-sourcemaps (static / nuxt generate) Test (optional) Successful in 37s Details
✅ CI: Optional E2E Tests / E2E node-eve (latest) Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E node-openai-decisions Test (optional) Successful in 49s Details
✅ CI: Optional E2E Tests / E2E gen-ai-libraries (cloudflare) Test (optional) Successful in 58s Details
✅ CI: Optional E2E Tests / E2E nextjs-16 (vinext) Test (optional) Successful in 2m Details
✅ CI: Optional E2E Tests / E2E node-express-send-to-sentry Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E node-express-mcp-v2 Test (optional) Successful in 53s Details
✅ CI: Optional E2E Tests / E2E nestjs-12 (cloudflare) Test (optional) Successful in 47s Details
✅ CI: Optional E2E Tests / E2E node-express-send-to-sentry-static Test (optional) Successful in 1m Details
✅ CI: Optional E2E Tests / E2E nextjs-orpc Test (optional) Successful in 1m Details

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant