ci: binary-split CITGM source download uses stale repository owner
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, javascript, shell
Research direction
The issue is in the CITGM source download in .github/workflows/node-integration.yml. Look for the matrix entry for binary-split and update its URL from maxogden to max-mapper. Also, update the curl command to include --fail --show-error flags to improve error reporting. Test by running the workflow or checking the syntax of the YAML file.
Written by the indexing model from the issue text.
Description
Summary
The npm 11.20.0 release integration failed in the Node.js 22 and Node.js 23 CITGM jobs before binary-split@1.0.5 could be tested.
Failing workflow
Workflow run: https://github.com/npm/cli/actions/runs/35787155620
Failing jobs:
- Node.js 22: https://github.com/npm/cli/actions/runs/35787155620/job/106973411919
- Node.js 23: https://github.com/npm/cli/actions/runs/35787155620/job/106974673276
Failure
Both jobs attempted to download the source archive from:
https://codeload.github.com/maxogden/binary-split/tar.gz/47044d430f5973380bfd4ef3d179f9d5f3eb54b4
The response was not a gzip archive:
gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
Process completed with exit code 2.
The referenced commit still exists, but GitHub resolves it under the transferred repository:
https://github.com/max-mapper/binary-split/commit/47044d430f5973380bfd4ef3d179f9d5f3eb54b4
The CITGM source URL still uses the former maxogden owner. The old codeload URL returns non archive content, which is streamed directly into tar by .github/workflows/node-integration.yml:
curl -sSL "${{ matrix.url }}" | tar xz -C "$TARGET_DIR" --strip=1
Expected behavior
The integration matrix should use a working source URL for binary-split, and HTTP download failures should be reported as HTTP errors rather than gzip extraction errors.
Suggested changes
- Update the
binary-splitsource URL to use the currentmax-mapperrepository owner. - Use
curl --fail --show-error --locationfor archive downloads so non successful HTTP responses are not passed totar.
The download handling is the same underlying workflow weakness discussed in #10016, although the unavailable Node.js nightly archive and this stale GitHub repository URL are separate upstream conditions.
- Dominant language
- JavaScript
- Stars
- 10.1k
- Forks
- 4.7k
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 19
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from npm/cli
-
Difficulty 1/5 Under an hour Newbie friendliness 80/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Bug Needs Triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
[DOCS] `npm trust circle` docs should warn that OIDC token exchange in SSH reruns isn't supported OpenDocumentation Needs Triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Documentation Needs Triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100
-
Issue-Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
sugarlabs/musicblocks#8924 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
ArduPilot/ardupilot_wiki#8088 ·
-
[BUG] createTool tools cannot be registered with Mastra when exactOptionalPropertyTypes is enabled Opencustomer-eng status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100