History

pakrym-oai 703fb38d2a Make codex-sdk depend on openai/codex (#11503 ) Do not bundle all binaries inside the SDK as it makes the package huge. Instead depend on openai/codex		2026-02-11 16:20:10 -08:00
..
build_container.sh	fix: update scripts/build_container.sh to use pnpm instead of npm (#631 )	2025-04-24 16:38:57 -07:00
build_npm_package.py	Make codex-sdk depend on openai/codex (#11503 )	2026-02-11 16:20:10 -08:00
init_firewall.sh	feat: add common package registries domains to allowed-domains list (#414 )	2025-04-29 12:07:00 -07:00
install_native_deps.py	fix(codex-cli): improve ripgrep download diagnostics (#8486 )	2025-12-23 21:18:35 +00:00
README.md	# Use `@openai/codex` dist-tags for platform binaries instead of separate package names (#11339 )	2026-02-10 10:33:47 -08:00
run_in_container.sh	feat: add common package registries domains to allowed-domains list (#414 )	2025-04-29 12:07:00 -07:00

README.md

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 codex \
  --package codex-responses-api-proxy \
  --package codex-sdk

This downloads the native artifacts once, hydrates vendor/ for each package, and writes tarballs to dist/npm/.

When --package codex is provided, the staging helper builds the lightweight @openai/codex meta package plus all platform-native @openai/codex variants that are later published under platform-specific dist-tags.

If you need to invoke build_npm_package.py directly, run codex-cli/scripts/install_native_deps.py first and pass --vendor-src pointing to the directory that contains the populated vendor/ tree.