@sentry/profiling-node 10.49.0 → 10.50.0

package/README.md

@@ -239,13 +239,19 @@ the binaries will be copied. This is wasteful as you will likely only need one o
 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`, use `--help` to see a list of available options or
-`--dry-run` if you want it to log the binaries that would have been deleted.
+script can be invoked via `sentry-prune-profiler-binaries`:
+
+```bash
+npx --package=@sentry/profiling-node sentry-prune-profiler-binaries
+```
+
+Use `--help` to see a list of available options or `--dry-run` if you want it to log the binaries that would have been
+deleted.
 
 Example of only preserving a binary to run node16 on linux x64 musl.
 
 ```bash
-sentry-prune-profiler-binaries --target_dir_path=./dist --target_platform=linux --target_node=16 --target_stdlib=musl --target_arch=x64
+npx --package=@sentry/profiling-node sentry-prune-profiler-binaries --target_dir_path=./dist --target_platform=linux --target_node=16 --target_stdlib=musl --target_arch=x64
 ```
 
 Which will output something like

package/build/esm/package.json

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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sentry/profiling-node",
-  "version": "10.49.0",
+  "version": "10.50.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.49.0",
-    "@sentry/node": "10.49.0"
+    "@sentry/core": "10.50.0",
+    "@sentry/node": "10.50.0"
   },
   "devDependencies": {
     "@types/node": "^18.19.1"