ref(profiling-node)!: Remove prune-profiler-binaries bin script (#23104)

Removes the `sentry-prune-profiler-binaries` bin script from
`@sentry/profiling-node`.

The script was already deprecated with a runtime warning and a README
notice pointing at #20567. This PR follows
through on that removal:

* Deletes `scripts/prune-profiler-binaries.js` and its test.
* Removes the `bin` mapping and the script's `files` entry from
`package.json`.
* Drops the pruning walkthrough from the profiling-node README,
replacing it with a short note on the binary naming scheme so users who
want to prune unused binaries can do so themselves as a build step (as
suggested in the issue).
* Removes the "register the new ABI in the profiling pruner" step from
`docs/supporting-a-new-node-version.md`, since the `NODE_TO_ABI` map no
longer needs maintaining.

The MIGRATION.md entry for this removal already exists on `develop`, so
it is unchanged here.

Fixes #20567

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: nicohrubec

docs/supporting-a-new-node-version.md

@@ -93,15 +93,10 @@ Reference: [#20710](https://github.com/getsentry/sentry-javascript/pull/20710)
    - [ ] `@sentry-internal/node-native-stacktrace` in `packages/node-native/package.json`
    - [ ] Run `yarn install` to update `yarn.lock`
 
-3. Register the new ABI in the profiling pruner. In
-   `packages/profiling-node/scripts/prune-profiler-binaries.js`:
-   - [ ] Add the Node major to ABI mapping to the `NODE_TO_ABI` object (e.g. `26: '147'`).
-   - [ ] Add the corresponding `else if (NODE.startsWith('26'))` branch.
-
-4. Allow the new major in the profiling integration, in `packages/profiling-node/src/integration.ts`:
+3. Allow the new major in the profiling integration, in `packages/profiling-node/src/integration.ts`:
    - [ ] Add the version number to the `if (![16, 18, 20, 22, 24, 26].includes(NODE_MAJOR))` guard
    - [ ] Add the version to the supported-versions list in the `console.warn` message below the guard (the string that reads `...prebuilt support for the following LTS versions of Node.js: 16, 18, 20, 22, 24.`)
 
-5. Handle deprecation warnings. Each new Node version tends to deprecate APIs the SDK (or its dependencies) still use, which can break tests that assert on clean stderr or console output.
+4. Handle deprecation warnings. Each new Node version tends to deprecate APIs the SDK (or its dependencies) still use, which can break tests that assert on clean stderr or console output.
 
-6. Fix version-specific test failures, some integrations or test dependencies may not yet work on the new version.
+5. Fix version-specific test failures, some integrations or test dependencies may not yet work on the new version.

packages/profiling-node/README.md

@@ -234,46 +234,8 @@ require('esbuild').build({
 
 Once you run `node esbuild.serverless.js` esbuild wil bundle and output the files to ./dist folder, but note that all of
 the binaries will be copied. This is wasteful as you will likely only need one of these libraries to be available during
-runtime.
-
-> **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
-```
-
-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
-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
-
-```
-Sentry: pruned ./dist/sentry_cpu_profiler-darwin-x64-108-IFGH3SUR.node (90.41 KiB)
-Sentry: pruned ./dist/sentry_cpu_profiler-darwin-x64-93-Q7KBVHSP.node (74.16 KiB)
-Sentry: pruned ./dist/sentry_cpu_profiler-linux-arm64-glibc-108-NXSISRTB.node (52.17 KiB)
-Sentry: pruned ./dist/sentry_cpu_profiler-linux-arm64-glibc-83-OEQT5HUK.node (52.08 KiB)
-Sentry: pruned ./dist/sentry_cpu_profiler-linux-arm64-glibc-93-IIXXW2PN.node (52.06 KiB)
-Sentry: pruned ./dist/sentry_cpu_profiler-linux-arm64-musl-108-DSILNYHA.node (48.46 KiB)
-Sentry: pruned ./dist/sentry_cpu_profiler-linux-arm64-musl-83-4CNOBNC3.node (48.37 KiB)
-Sentry: pruned ./dist/sentry_cpu_profiler-linux-arm64-musl-93-JA5PKNWQ.node (48.38 KiB)
-Sentry: pruned ./dist/sentry_cpu_profiler-linux-x64-glibc-108-NXSISRTB.node (52.17 KiB)
-Sentry: pruned ./dist/sentry_cpu_profiler-linux-x64-glibc-83-OEQT5HUK.node (52.08 KiB)
-Sentry: pruned ./dist/sentry_cpu_profiler-linux-x64-glibc-93-IIXXW2PN.node (52.06 KiB)
-Sentry: pruned ./dist/sentry_cpu_profiler-linux-x64-musl-108-CX7SL27U.node (51.50 KiB)
-Sentry: pruned ./dist/sentry_cpu_profiler-linux-x64-musl-83-YD7ZQK2E.node (51.53 KiB)
-Sentry: pruned ./dist/sentry_cpu_profiler-win32-x64-108-P7V3URQV.node (181.50 KiB)
-Sentry: pruned ./dist/sentry_cpu_profiler-win32-x64-93-3PKQDSGE.node (181.50 KiB)
-✅ Sentry: pruned 15 binaries, saved 1.06 MiB in total.
-```
+runtime. Since the binaries follow the `sentry_cpu_profiler-<platform>-<arch>-<stdlib>-<abi>.node` naming scheme, you can
+delete the ones that do not match your target runtime as part of your build step to reduce the deployment size.
 
 ### Environment flags
 

packages/profiling-node/package.json

@@ -22,9 +22,6 @@
       }
     }
   },
-  "bin": {
-    "sentry-prune-profiler-binaries": "scripts/prune-profiler-binaries.js"
-  },
   "engines": {
     "node": ">=20.19.0 <22.0.0 || >=22.12.0 <23.0.0 || >=23.2.0"
   },
@@ -33,8 +30,7 @@
   },
   "files": [
     "/build",
-    "package.json",
-    "/scripts/prune-profiler-binaries.js"
+    "package.json"
   ],
   "scripts": {
     "clean": "rm -rf build",