Repository navigation
build(deps): patch fixture vulnerabilities and refresh Weixin - #503
Merged
Merged
Conversation
Contributor
|
🦞👀 Pull request received. I will update this pull request when review starts. ClawSweeper review completeClawSweeper finished reviewing this revision. The review result is being finalized. |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
This was referenced Oct 15, 2026
Patch smol-toml, OpenTelemetry core, and qs in the Codex and TencentDB fixture locks while retaining qualified plugin versions. Accept only Node's exact optional TypeScript warning before TencentDB's known missing-module diagnostic, keeping unrelated failures strict and the captured fixture LF-stable on Windows. Fold in the qualified Weixin 2.4.10 and Zod 4.6.5 update from #475, retaining its four-entry fixture lock without installing OpenClaw host peers. Preserve the native admission/config proof limitations documented there. Co-authored-by: Vincent Koc <vincentkoc@ieee.org> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
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.
Patch four security alerts through smol-toml 1.9.0, OpenTelemetry core 2.11.0 and qs 6.16.0 in the Codex/TencentDB fixture locks. Retain those qualified plugin versions and deduplicate four nested OpenTelemetry copies.
The TencentDB failure-contract fix accepts only Node's exact optional experimental TypeScript warning before the known missing-module diagnostic. Unrelated errors, wrong modules/codes and timeouts still fail. Keep the captured fixture LF-stable on Windows.
Consolidate #475's Weixin 2.4.10 and Zod 4.6.5 update, preserving the four-entry fixture lock and existing host-peer boundary. Its previously recorded native proof covers 24 plugin admission cases and config/account/pairing preservation with external network denied. This is not full Gateway, downstream command, media, or live-provider qualification. Vincent's detailed evidence and raw-workspace audit limitations remain in #475.
Validation: all three changed fixture locks audit clean; Weixin's registry integrity matches the committed lock and its Node minimum is unchanged. All 21 focused security/failure-contract tests pass. The prior exact-tree Codex/TencentDB candidate passed required cross-platform, isolated fixture and every advisory lane, including real Windows compiler controls. This combined candidate adds the already-qualified Weixin patch and current-main dashboard changes; fresh required CI remains enforced by normal protected merge. The independent P0–P2 review covers the final diff.
The 85 separately dismissed alerts inside immutable upstream bundles and shrinkwraps are not claimed patched. No repository version bump, release, tag, deployment, timeout increase, or security-setting change.