mirror of https://github.com/openai/codex.git synced 2026-09-03 14:59:03 +00:00

Files

Charlie Marsh 84aa75204a Format Python scripts across the repository (#42109 )

## Why

The root Python formatting pass only covered `scripts/`, leaving Python utilities elsewhere in the repository outside `just fmt` and `just fmt-check`.

## What changed

- Run the scripts Ruff formatter from the repository root.
- Exclude `sdk/python`, which has its own formatter pass, and `codex-rs/vendor`.
- Apply Ruff formatting to the newly covered Python files and update the formatter coverage test.

GitOrigin-RevId: 73ac82b8bb9c713d589724f6c4f926399febb513

2026-09-01 17:47:29 +00:00

build_npm_package.py

Format Python scripts across the repository (#42109 )

2026-09-01 17:47:29 +00:00

init_firewall.sh

feat: add common package registries domains to allowed-domains list (#414 )

2025-04-29 12:07:00 -07:00

README.md

npm: remove legacy package artifact synthesis (#23836 )

2026-05-21 20:43:48 +00:00

run_in_container.sh

chore(cli) deprecate --full-auto (#20133 )

2026-04-29 04:41:30 +00: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 required native package archive artifacts, 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.

Direct build_npm_package.py invocations are still useful for package-specific debugging, but native packages expect --vendor-src to point at a prehydrated vendor/ tree. Release packaging should use scripts/stage_npm_packages.py.