Repository navigation
fix: clear critical/high npm advisories, fix red typedoc CI job (lane:2026-11-11d) - #20
Merged
Merged
Conversation
…CI job - handlebars 4.7.9 -> 4.7.10 (critical, dev-only via ts-jest), plus js-yaml, markdown-it/linkify-it, brace-expansion, browserslist, fast-copy, @babel/core via npm audit fix (lockfile only). - overrides: tar >=7.5.21 (critical, PAX/long-name smuggling) and protobufjs >=8.6.6, matching the fixed versions. - CI: the typedoc job ran npm install without the X11/GL headers that gl's node-gyp fallback needs; add the same apt step build-test has. Co-Authored-By: claude-flow <ruv@ruv.net>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
deps:package-lock.json
npm auditwent from 2 critical, 5 high (32 total) to 0 critical, 0 high (21 total).npm ls handlebars --omit=devis empty, and the only path ists-jest. The publisheddspy.ts@2.3.1dependency list (npm view) has no handlebars. So this is a lockfile-only fix, with no release needed.>=7.5.11→>=7.5.21(critical,<=7.5.20). Path: js-pytorch → @eduardoleao052/gpu → gl → node-gyp. It is used at install time for gl's source-build fallback. This override only affects this repo's tree. Downstream is still exposed: node-gyp 10.3.1 declarestar ^6.2.1, and every 6.x is in the critical range. A scratch install ofdspy.ts@2.3.1resolvestar@6.2.1, andnpm audit --omit=devreports tar critical plus node-gyp and cacache high. No floor bump in dspy.ts can reach consumers. Only js-pytorch 1.0 (a semver-major change) or removing js-pytorch fixes it, so no release was cut. That is an owner decision.>=7.5.8→>=8.6.6(moderate, 8.0.0–8.6.5).npm audit fix(non-force) bumped these: js-yaml, markdown-it/linkify-it (typedoc), brace-expansion, browserslist, fast-copy (pino-pretty), and @babel/core.Remaining: 14 moderate and 7 low. They all need a semver-major change: js-pytorch 1.0 (gl/node-gyp/glob/cacache chain), jest/ts-jest, @typescript-eslint, or typedoc. They are out of scope for a lockfile fix.
ci:main-red
Main at 531d66b failed only in the typedoc job (build-test 18/20/22 passed). That job runs
npm installwithout the X11/GL headers. gl has no prebuilt binary for Node 20.20.2, so it falls back tonode-gyp rebuildand fails withPackage x11 was not found. The build-test job already installs these headers. This PR adds the same apt step to the docs job.CI note
The first two attempts (14:21–15:17 UTC) failed in the apt step with
Temporary failure resolving azure.archive.ubuntu.com / security.ubuntu.com. A runner DNS outage hit ruvnet/ruvector's Clippy job in the same window. Neither attempt got past apt. A further re-run was done after the window, since the first re-run fell inside the same outage.Verification (local)
npm run build,npm run typecheck,npm test(32 suites, 193 tests passed), andnpm run docs(0 errors) all pass.🤖 Generated with claude-flow