edefb6eb9c
- Revert workflow to use internal identifier 'llmx' instead of scoped name - Revert build_npm_package.py to only accept internal identifiers - Restore "Create GitHub Release" step that was incorrectly removed - Package name '@valknarthing/llmx' is read from package.json by the script This matches OpenAI's approach where they use 'codex' not '@openai/codex' in workflow. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
npm releases
Use the staging helper in the repo root to generate npm tarballs for a release. For
example, to stage the CLI, responses proxy, and SDK packages for version 0.6.0:
./scripts/stage_npm_packages.py \
--release-version 0.6.0 \
--package llmx \
--package llmx-responses-api-proxy \
--package llmx-sdk
This downloads the native artifacts once, hydrates vendor/ for each package, and writes
tarballs to dist/npm/.
If you need to invoke build_npm_package.py directly, run
llmx-cli/scripts/install_native_deps.py first and pass --vendor-src pointing to the
directory that contains the populated vendor/ tree.