@sentry/profiling-node 10.50.0 → 10.52.0

package/README.md

@@ -238,8 +238,10 @@ Once you run `node esbuild.serverless.js` esbuild wil bundle and output the file
 the binaries will be copied. This is wasteful as you will likely only need one of these libraries to be available during
 runtime.
 
-To prune the other libraries, profiling-node ships with a small utility script that helps you prune unused binaries. The
-script can be invoked via `sentry-prune-profiler-binaries`:
+> **Deprecation notice:** This script will be removed in the next major version. If you depend on it, please comment on
+> [this issue](https://github.com/getsentry/sentry-javascript/issues/20567).
+
+To prune the other libraries, profiling-node ships with a small utility script that helps you prune unused binaries:
 
 ```bash
 npx --package=@sentry/profiling-node sentry-prune-profiler-binaries

package/build/esm/package.json

@@ -1 +1 @@
-{"type":"module","version":"10.50.0","sideEffects":false}
+{"type":"module","version":"10.52.0","sideEffects":false}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sentry/profiling-node",
-  "version": "10.50.0",
+  "version": "10.52.0",
   "description": "Official Sentry SDK for Node.js Profiling",
   "repository": "git://github.com/getsentry/sentry-javascript.git",
   "homepage": "https://github.com/getsentry/sentry-javascript/tree/master/packages/profiling-node",
@@ -62,8 +62,8 @@
   },
   "dependencies": {
     "@sentry-internal/node-cpu-profiler": "^2.2.0",
-    "@sentry/core": "10.50.0",
-    "@sentry/node": "10.50.0"
+    "@sentry/core": "10.52.0",
+    "@sentry/node": "10.52.0"
   },
   "devDependencies": {
     "@types/node": "^18.19.1"

package/scripts/prune-profiler-binaries.js

@@ -56,6 +56,10 @@ Arguments:\n
   process.exit(0);
 }
 
+console.warn(
+  '[Sentry] Warning: This script will be removed in the next major version. See: https://github.com/getsentry/sentry-javascript/issues/20567',
+);
+
 const ARGV_ERRORS = [];
 
 const NODE_TO_ABI = {