You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maka.apache.org by "me2seeks (via GitHub)" <gi...@apache.org> on 2026/09/09 08:04:36 UTC
[PR] fix(eval): update DeepSeek Harness security dependencies [maka]
me2seeks opened a new pull request, #5084:
URL: https://github.com/apache/maka/pull/5084
## Summary
Dependabot split the DeepSeek Harness security updates across three lockfile-only PRs. Merging those changes alone would leave the previously built toolchain fingerprint pinned: an old vulnerable tree could remain admitted, while a rebuilt fixed tree would fail verification.
Update the optional Harness toolchain to Hono 4.13.7, sharp 0.35.4, and js-yaml 4.3.2 together. Rebuild it with the pinned linux/amd64 image and record the resulting checksum-manifest fingerprint so the fixed tree is the one Maka admits.
Supersedes #5078, #5079, and #5080.
## Verification
- `npm audit --package-lock-only --omit=dev` in `packages/eval/harbor/deepseek-harness-toolchain`: 0 vulnerabilities
- `node scripts/prepare-deepseek-harness-toolchain.mjs --out /tmp/maka-deepseek-harness-security-toolchain --write` using the repository's pinned linux/amd64 image via nerdctl
- `verifyToolchainDirectory('deepseek-harness', ...)` against the rebuilt tree: passed
- `sha256sum --check --quiet checksums.sha256`: passed
- `npm --workspace @maka/eval run test:dist`: 82 Node tests passed, 1 platform test skipped; 72 Python tests passed, 10 environment tests skipped
- `node --test scripts/script-entrypoints.test.mjs scripts/asf-source-release.test.mjs`: 34 passed
- `npm run build`: passed
- `npm run check:stale`: passed
- `git diff --check`: passed
## AI use
Select exactly one:
- [ ] No generative tool made a substantive contribution
- [x] Generative tooling made a substantive contribution
Tool(s) and scope: Codex investigated the dependency reachability, consolidated the lockfile updates, rebuilt and verified the pinned toolchain, and prepared this change.
## Checklist
- [ ] Tests cover the change and fail without it
- [x] Lint, format, typecheck and the affected suites pass locally
Does this PR entail a change in behavior?
- [x] Yes — described under Summary above
- [ ] No
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org
For additional commands, e-mail: commits-help@maka.apache.org
Re: [PR] fix(eval): update DeepSeek Harness security dependencies [maka]
Posted by "me2seeks (via GitHub)" <gi...@apache.org>.
me2seeks merged PR #5084:
URL: https://github.com/apache/maka/pull/5084
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org
For additional commands, e-mail: commits-help@maka.apache.org
Re: [PR] fix(eval): update DeepSeek Harness security dependencies [maka]
Posted by "me2seeks (via GitHub)" <gi...@apache.org>.
me2seeks commented on PR #5084:
URL: https://github.com/apache/maka/pull/5084#issuecomment-5602966643
Addressed the verification gap in `2816e5a8afa20fde360066d7e7b7a42c43032dc2`.
Core CI now rebuilds the DeepSeek Harness linux/amd64 toolchain whenever its lockfile, build inputs, or pinned identity changes. It compares the rebuilt fingerprint with `TOOLCHAIN_IDENTITIES["deepseek-harness"]` and verifies `checksums.sha256`. The planner and workflow-policy contracts cover the new gate. I also ran the same rebuild locally through nerdctl; its fingerprint and manifest both verified.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org
For additional commands, e-mail: commits-help@maka.apache.org