Skip to content

chore: refresh Kova validation and workflow dependencies - #275

Open
roboclaw-bot wants to merge 2 commits into
mainfrom
openclaw/deps-seven-day-kova-nov21
Open

roboclaw-bot wants to merge 2 commits into
mainfrom
openclaw/deps-seven-day-kova-nov21

Conversation

@roboclaw-bot

Copy link
Copy Markdown
Contributor

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 --check passed. 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)
Update Exact dated source
Node 22.23.5 Linux runner artifact, 2026-11-12 01:26:29 UTC
Node 24.22.3 Linux x64 and macOS arm64 runner artifacts, both 2026-11-12 01:26:19 UTC
Node 26.13.1 Linux runner artifact, 2026-11-12 01:26:06 UTC
pnpm 12.21.0 npm registry, 2026-11-13 21:01:11.515 UTC; all 15 exact optional platform packages published 21:00:15.237–21:00:59.808 UTC that day and have no further dependencies
setup-node 7.1.0 Release, 2026-10-08 02:52:34 UTC, commit 949feb2413d6458794dcd2491c4babbbce0c15c1
CodeQL Action 4.39.3 Release, 2026-11-04 16:49:20 UTC, peeled commit 33d7b85da1a04171e211befe2c739303b9a4c066; default Linux CodeQL bundle 2.27.4 uploaded 2026-10-30 13:38:20 UTC
download-artifact 8.0.2 Release, 2026-10-07 10:09:51 UTC, commit 9000827ccba6bdab643e8b6fd33ac0654aef8333
upload-artifact 7.0.2 Release, 2026-10-07 10:08:14 UTC, commit cf430e030ddbb5b0abf93d22962f4752f3646cd9
action-gh-release 3.0.4 Release, 2026-11-05 14:26:38 UTC, peeled commit 8a0cd651e5b2365bd640854a3fa5dfc70e4875f3

The 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

roboclaw-bot and others added 2 commits November 21, 2026 03:19
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
@roboclaw-bot
roboclaw-bot requested a review from a team as a code owner November 21, 2026 03:20
@clawsweeper

clawsweeper Bot commented Nov 21, 2026 •

Copy link
Copy Markdown

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

ClawSweeper review complete

ClawSweeper finished reviewing this revision. The review result is being finalized.

View the workflow run.

@clawsweeper clawsweeper Bot added P3 Low-risk cleanup, docs, polish, ergonomics, or speculative feature. rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR. labels Nov 21, 2026
@clawsweeper

clawsweeper Bot commented Nov 21, 2026

Copy link
Copy Markdown

Codex review: needs maintainer review before merge.

What this changes

Updates Node runtime selections, hydration pnpm, and pinned workflow Actions within their existing major versions.

Example: Linux Node 24 validation

  • Before: CI uses Node 24.22.1 and runs native-owner verification on that row.
  • After: CI uses Node 24.22.3 and keeps native-owner verification on the updated row.

Review scores

Measure Result What it means
Overall readiness 🐚 platinum hermit (4/6) A narrow maintenance patch supported by successful exact-head CI and verified upstream pins.
Proof confidence 🐚 platinum hermit (4/6) This tooling-only refresh requires no separate user-facing proof; exact-head CI exercises the updated runtime matrix and CodeQL Actions, while release publication and hydration were not dispatched.
Patch quality 🐚 platinum hermit (4/6) No actionable review findings were identified.

Product

Kind: Maintenance · Worth it: Yes · Fix scope: Complete
User problem: Validation and release workflows use older compatible tooling releases.
Reason: The maintainer-authorized refresh follows existing maintenance practice without introducing options, APIs, or unrelated changes.

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
Reviewed head: 2122d799fb088ec1ea8c81bd60e11b31acefcb8c

Before merge

None.

Findings

None.

Agent review details

How this fits together

GitHub 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]
Loading

Technical review

Best 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

  • Runtime matrix, shared Node pin, and hydration pnpm keeps the original intent (54280b1: Select patched validation runtimes while preserving the Node support floor and Linux native-owner gate.)
  • Setup Action pins keeps the original intent (60c4dce: Refresh CI tooling while retaining SHA pinning and existing workflow structure.)
  • CodeQL Action pins keeps the original intent (899d738: Preserve PR analysis and language coverage while batching main scans.)
  • Artifact and publication Actions keeps the original intent (8c752f9: The original PR has no body; inspected workflow context retains validation, signed-tag verification, and artifact provenance gates.)

Security

None.

Evidence

What I checked:

  • Pinned introduction reviewed: The introduced diff contains only version and SHA replacements; the Node matrix and native-owner condition move together, with workflow permissions, triggers, release checks, and lockfiles preserved. (.github/workflows/ci.yml:26, 2122d799fb08)
  • Exact-head validation: All four runtime rows, Website, and all three language analyses succeeded on the reviewed head; the separate Proof check was skipped. (2122d799fb08)
  • Policy and discussion: Read the complete root AGENTS.md, CI policy, current PR body, comments, and reviews; no nested AGENTS.md or maintainer-note entries were found. The optional team-session links qualify for the supplied provenance exception and were not treated as proof. (AGENTS.md:1, 2122d799fb08)
  • Setup Action pin verified: The upstream v7.1.0 tag resolves to the selected commit; release notes describe compatible enhancements, fixes, and dependency maintenance. (949feb2413d6)
  • CodeQL pin verified: The annotated v4.39.3 tag peels to the selected commit; its release fixes incorrect alert filtering. (33d7b85da1a0)
  • Download pin verified: The v8.0.2 tag matches the selected commit; upstream describes retry and dependency maintenance. (9000827ccba6)

Preflight source

Source unknown. Source comparison at the observed PR snapshot only. Completion is self-reported; body, policy, tests, execution, and report bytes are not verified.

Labels

Label changes:

  • add P3: Routine compatible tooling maintenance with no demonstrated user-facing regression.
  • add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🐚 platinum hermit and patch quality is 🐚 platinum hermit.
  • add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR.

Label justifications:

  • P3: Routine compatible tooling maintenance with no demonstrated user-facing regression.
  • rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🐚 platinum hermit and patch quality is 🐚 platinum hermit.
  • status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR.

Rating scale

6/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.

Workflow

ClawSweeper edits this one comment on every review. Comment @clawsweeper re-review for a fresh review only. Repair and merge execution lanes are retired.

Reviewed November 20, 2026, 10:32 PM ET / November 21, 2026, 03:32 UTC.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

P3 Low-risk cleanup, docs, polish, ergonomics, or speculative feature. rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant