Repository navigation
chore: refresh Kova validation and workflow dependencies - #275
roboclaw-bot wants to merge 2 commits into
Conversation
Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com>
Worked on by: - @vincentkoc Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> OpenClaw-Publication: 83bd9d31-f962-4290-96bb-701ee6776ec5
|
🦞👀 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: needs maintainer review before merge. What this changesUpdates Node runtime selections, hydration pnpm, and pinned workflow Actions within their existing major versions. Example: Linux Node 24 validation
Review scores
ProductKind: Maintenance · Worth it: Yes · Fix scope: Complete Merge readiness✅ Ready for maintainer review This PR is a focused maintenance refresh that remains absent from main; the reviewed head passes CI, and no actionable defect was found. Priority: P3 Before mergeNone. FindingsNone. Agent review detailsHow this fits togetherGitHub workflows select tooling for Kova validation, hydration, security analysis, and release packaging and publication. flowchart TD
A[Runtime and Action pins] --> B[Validation workflows]
B --> C[Kova checks and package smoke]
A --> D[CodeQL analysis]
A --> E[Hydration workflow]
A --> F[Release build and publication]
Technical reviewBest possible solution: Land the focused tooling refresh with the existing validation and release safeguards intact. Do we have a high-confidence way to reproduce the issue? This maintenance PR does not report a runtime bug requiring reproduction. Is this the best way to solve the issue? Updating existing pins in place is appropriately scoped and preserves the established workflow owners and gates. AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning medium; reviewed against e0f38eead3ef. Provenance checked
SecurityNone. EvidenceWhat I checked:
Preflight sourceSource unknown. Source comparison at the observed PR snapshot only. Completion is self-reported; body, policy, tests, execution, and report bytes are not verified. LabelsLabel 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 Reviewed November 20, 2026, 10:32 PM ET / November 21, 2026, 03:32 UTC. |
Contributor: @vincentkoc
Work sessions
Linked for team reference; these sessions aren’t public.
What Problem This Solves
Kova's validation jobs are still using older patches of their test runtimes, package manager, and workflow actions even though compatible updates have been available for at least seven days.
User Impact
No user-visible behavior or minimum supported Node.js version changes. Kova maintains the same Linux and macOS validation coverage on patched versions of the existing Node.js lines.
Why This Change Was Made
Move the test matrix and shared runtime pin together, including the condition that runs the Linux native command-owner check. Refresh the hydration tool and SHA-pinned GitHub Actions within their existing major versions. Keep workflow behavior, release gates, and both npm lockfiles unchanged.
Evidence
All 20 CLI snapshots passed on each of the three new Linux Node versions in a credential-free, network-isolated sandbox. Website type checking, all 10 website tests, the static build (with external fonts unavailable offline), web payload validation, and the release dry-run unit test passed on Node 24.22.3. The pnpm CLI reported 12.21.0. Changed workflow YAML parsed and
git diff --checkpassed. Full CI is still needed for the macOS lane and Docker-dependent native owner verification. No release, signing, or workflow dispatch was performed.Seven-day cutoff evidence (inclusive: 2026-11-14 01:46 UTC)
949feb2413d6458794dcd2491c4babbbce0c15c133d7b85da1a04171e211befe2c739303b9a4c066; default Linux CodeQL bundle 2.27.4 uploaded 2026-10-30 13:38:20 UTC9000827ccba6bdab643e8b6fd33ac0654aef8333cf430e030ddbb5b0abf93d22962f4752f3646cd98a0cd651e5b2365bd640854a3fa5dfc70e4875f3The three local Linux binaries matched the checksum lists on
nodejs.org/dist. No npm lockfile dependency was newly resolved. Astro 7.4.13, already on main, was not downgraded.Worked on by