From 0c4736ca7677f18e2a2e66f369f8f1def2130db4 Mon Sep 17 00:00:00 2001
From: Paul Asjes <paul.asjes@elevenlabs.io>
Date: Thu, 27 Aug 2026 21:00:32 +0200
Subject: [PATCH] fix: ship README and LICENSE in the npm packages
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The published 1.1.0 launcher tarball contains only bin/cli.js and
package.json, so npmjs.com renders a blank page for @elevenlabs/cli and
reports all six packages as unlicensed.

The launcher takes the repository README and LICENSE from the tagged
checkout. Platform packages take LICENSE from the archive they already
download and verify, and get a short README saying not to install them
directly — the full CLI README would be misleading on a package users
are not meant to install.

npm ships README and LICENSE regardless of the files array, so no files
change is needed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
---
 .github/workflows/ci.yml | 25 +++++++++++++++++++++++++
 1 file changed, 25 insertions(+)

diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index c40277d..3029bc2 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -324,6 +324,26 @@ jobs:
           fi
           install -m 0755 "${BIN}" "${PKG_DIR}/${BINARY_NAME}"
 
+          # npm always ships README and LICENSE regardless of `files`, so
+          # placing them is enough. Without them the package page renders
+          # empty and npm reports the package as unlicensed.
+          LICENSE_SRC=$(find extract -type f -name LICENSE -print -quit)
+          if [[ -n "${LICENSE_SRC}" ]]; then
+            install -m 0644 "${LICENSE_SRC}" "${PKG_DIR}/LICENSE"
+          fi
+
+          # Deliberately not the repository README: this package is not one
+          # users install directly, so it gets a note saying so.
+          cat > "${PKG_DIR}/README.md" <<README
+          # ${PLATFORM_PKG}
+
+          Platform-specific binary for [\`@elevenlabs/cli\`](https://www.npmjs.com/package/@elevenlabs/cli)
+          on ${SUFFIX}.
+
+          Do not install this directly — install \`@elevenlabs/cli\`, which selects
+          the right platform package for you.
+          README
+
           cat > "${PKG_DIR}/package.json" <<PKGJSON
           {
             "name": "${PLATFORM_PKG}",
@@ -417,6 +437,11 @@ jobs:
           }
           PKGJSON
 
+          # The page users actually land on, so it gets the repository README
+          # from the tagged commit. npm ships both regardless of `files`.
+          cp README.md "${PKG_DIR}/README.md"
+          cp LICENSE "${PKG_DIR}/LICENSE"
+
           # Write launcher script
           mkdir -p "${PKG_DIR}/bin"
           cat > "${PKG_DIR}/bin/cli.js" <<'LAUNCHER'