Skip to content

fix: try to fix "Stage npm package" step in ci.yml#15092

Merged
bolinfest merged 1 commit intomainfrom
pr15092
Mar 18, 2026
Merged

fix: try to fix "Stage npm package" step in ci.yml#15092
bolinfest merged 1 commit intomainfrom
pr15092

Conversation

@bolinfest
Copy link
Collaborator

@bolinfest bolinfest commented Mar 18, 2026

Fix the CI job by updating it to use artifacts from a more recent release (0.115.0) instead of the existing one (0.74.0).

This step in our CI job on PRs started failing today:

- name: Stage npm package
id: stage_npm_package
env:
GH_TOKEN: ${{ github.token }}
run: |
set -euo pipefail
# Use a rust-release version that includes all native binaries.
CODEX_VERSION=0.74.0
OUTPUT_DIR="${RUNNER_TEMP}"
python3 ./scripts/stage_npm_packages.py \
--release-version "$CODEX_VERSION" \
--package codex \
--output-dir "$OUTPUT_DIR"
PACK_OUTPUT="${OUTPUT_DIR}/codex-npm-${CODEX_VERSION}.tgz"
echo "pack_output=$PACK_OUTPUT" >> "$GITHUB_OUTPUT"

I believe it's because this test verifies that the "package npm" script works, but we want it to be fast and not wait for binaries to be built, so it uses a GitHub workflow that's already done. Because it was using a GitHub workflow associated with 0.74.0, it seems likely that workflow's history has been reaped, so we need to use a newer one.

@bolinfest bolinfest merged commit 392347d into main Mar 18, 2026
32 checks passed
@bolinfest bolinfest deleted the pr15092 branch March 18, 2026 20:52
@github-actions github-actions bot locked and limited conversation to collaborators Mar 18, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants