Repository navigation
build(deps): refresh eligible dependencies and source-map security fix - #270
Conversation
|
🦞👀 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. |
|
Codex review: needs maintainer review before merge. What this changesUpdates four direct dependencies and the remaining source-map-js resolution, with an Unreleased changelog entry. Example: A frozen dependency installation prepares Vitest coverage tooling.
Review scores
ProductKind: Maintenance · Worth it: Yes · Fix scope: Complete Merge readiness✅ Ready for maintainer review Keep open: this PR completes a useful security update and dependency refresh that current main does not contain; no actionable patch defect was found, and all seven checks pass on the reviewed head. Priority: P2 Before mergeNone. FindingsNone. Tests
Agent review detailsHow this fits togetherThe manifest and lockfile supply libraries for Poltergeist’s terminal panel, logging, file-pattern matching, and development tooling. flowchart TD
A[Dependency installation] --> B[Manifest and lockfile]
B --> C[Panel logging and glob libraries]
C --> D[Poltergeist CLI]
B --> E[Vitest coverage tooling]
E --> F[Magicast]
F --> G[Source map processing]
Technical reviewBest possible solution: Land the compatible dependency refresh with the single repaired source-map resolution and existing runtime requirements preserved. Do we have a high-confidence way to reproduce the issue? No Poltergeist failure is reported or reproduced; upstream source and regression tests establish the security repair supplied by source-map-js 1.2.2. Is this the best way to solve the issue? The existing dependency owners and published versions provide the repair without application changes, and inspected consumer contracts reveal no required adaptation. AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning medium; reviewed against b7d441c4118a. Provenance checked
TestingProof path: unit tests only. SecurityNone. EvidenceWhat I checked:
Likely related people:
Review metrics
LabelsLabel changes: No label changes. Label justifications:
Rating scale6/6 🦀 challenger crab · 5/6 🦞 diamond lobster · 4/6 🐚 platinum hermit · 3/6 🦐 gold shrimp · 2/6 🦪 silver shellfish · 1/6 🧂 unranked krab. Overall follows the weaker of proof and patch quality; ✨ marks media proof (a screenshot, video, or linked artifact) that directly shows the changed behavior. WorkflowClawSweeper edits this one comment on every review. Comment HistoryReview history (14 earlier review cycles; latest 8 shown)
Reviewed October 10, 2026, 6:58 AM ET / 10:58 UTC (Revision 15). |
Bumps the npm_and_yarn group with 1 update in the / directory: [source-map-js](https://github.com/7rulnik/source-map-js). Updates `source-map-js` from 1.2.1 to 1.2.2 - [Release notes](https://github.com/7rulnik/source-map-js/releases) - [Changelog](https://github.com/7rulnik/source-map-js/blob/main/CHANGELOG.md) - [Commits](7rulnik/source-map-js@v1.2.1...v1.2.2) --- updated-dependencies: - dependency-name: source-map-js dependency-version: 1.2.2 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
754b565 to
e526654
Compare
Update the remaining
source-map-js1.2.1 resolution to 1.2.2, including the upstream indexed source-map denial-of-service fix (CVE-2026-93749). Fold in the currently eligible compatible updates to pi-tui, LogTape, arkregex, and Vite.Resolved with pnpm's strict release-age policy. Keep Node.js 24, TypeScript 6 for TypeDoc compatibility, and Vitest 4. The Unreleased changelog credits @dependabot.
Validation: frozen install, build, lint, typecheck, complete Linux CI test suite, coverage, release-guard tests, API documentation generation, and built CLI smoke tests on AWS Crabbox. The Go example passes
govulncheck ./...using Go 1.27.2. Independent Codex autoreview is clean through P2. All seven checks passed at final PR head28ecc426b81b4528b1701d731312c3aeab642ac3; post-merge main CI and coverage also passed. Dependabot alert #32 is confirmed fixed.Original dependency update by @dependabot.