Skip to content

chore: refresh mature build and CI dependencies - #334

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

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

Conversation

@roboclaw-bot

Copy link
Copy Markdown
Contributor

Requested by @vincentkoc.

Work sessions

Linked for team reference; these sessions aren’t public.

Maintainer edits

MUST: Keep Allow edits from maintainers enabled for this PR so maintainers can help update the branch when needed.

What Problem This Solves

ClickClack's CI, container builds, and desktop packaging are behind on compatible dependency updates that have cleared the seven-day waiting period.

User Impact

No user-visible change or migration. The build and packaging pipelines pick up eligible maintenance updates without raising the supported Node minimum or changing signing, deployment, or release triggers.

Why This Change Was Made

Update both supported Node lines, the pinned Node and Alpine images, Electron's packaging tool, existing npm overrides, and the Go and GitHub Actions tools used by CI. Keep newer dependencies already on main and leave the pnpm runtime at 12.15.0 so the release workflow still accepts signed tags that declare it. The Electron runtime, Playwright browser/image pairing, SQLite/libc pairing, and release-age settings are unchanged.

Evidence

  • Frozen pnpm install passed with lifecycle scripts disabled locally. Offline validation passed 98 web tests on each Node line, 31 FakeCo tests, 69 desktop tests (one platform skip), typechecks, lint/format, docs and SDK builds, two byte-identical embedded app builds, and go test ./... without a PostgreSQL service. SQLite pairing passed; the updated deadcode and govulncheck reported no findings. Workflow structure and changed action inputs were checked. Independent review found no remaining P0–P2 issues after deferring the pnpm bump.
  • GitHub CI covers normal lifecycle installation, PostgreSQL-backed coverage, browser E2E, Docker, CodeQL, and hosted desktop packaging. No deployment or release workflow was dispatched.
Fixed-cutoff audit

Baseline: 8e42adba0f87d3f028fa155c4fc7299194c19be9. Inclusive cutoff: 2026-11-14T01:46:00Z.

  • Node 26.13.1 and 24.22.3: GitHub releases 2026-11-11T16:44:25Z and 2026-11-11T16:44:08Z; official Linux tarball checksums verified. Docker Hub published the pinned Node index (6bd9ab43) 2026-11-11T20:41:10.145231Z and the pinned Alpine 3.24.4 index (f59abe65) 2026-11-08T14:24:43.040363Z.
  • npm registry timestamps: electron-builder@26.18.1 and its newly resolved packaging dependencies, 2026-10-26T12:33:25.848Z–12:34:27.048Z; brace-expansion@1.1.22, 2026-11-11T12:32:33.050Z; brace-expansion@5.0.13, 2026-11-11T12:27:55.676Z; tar@7.5.23, 2026-11-11T18:11:10.985Z; undici@7.30.2, 2026-11-05T09:06:58.994Z. All 11 new lock identities were matched to registry integrity and timestamp, with no resolution downgrades or bootstrap lock changes.
  • Go proxy: deadcode module v0.52.0, 2026-10-10T19:29:17Z; govulncheck module v1.9.0, 2026-10-11T03:39:53Z; newly selected transitives all predate the cutoff.
  • Stable GitHub action release dates: download-artifact v8.0.2 (9000827, 2026-10-07T10:09:51Z); upload-artifact v7.0.2 (cf430e0, 2026-10-07T10:08:14Z); setup-node v7.1.0 (949feb2, 2026-10-08T02:52:34Z); pnpm/action-setup v6.1.1 (73e4699, 2026-11-03T13:50:23Z); and CodeQL v4.39.3 (33d7b85, 2026-11-04T16:49:20Z). The Azure login label is corrected to v3.1.0; its SHA is unchanged.

Worked on by

roboclaw-bot and others added 2 commits November 21, 2026 03:20
Refresh supported Node and Alpine artifacts, desktop packaging, existing npm overrides, and CI tooling against the fixed seven-day cutoff. Keep the pnpm bootstrap and signed release selectors on 12.15.0.

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: 0072c782-c9a5-4c5c-bd25-73b04b6164cb
@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
Contributor

🦞👀
ClawSweeper picked this up.

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

ClawSweeper review blocked

Automated review did not run, so no review verdict was produced.

Reason: The input-safety check rejected material in this revision. No detected value, path, or scanner output is reproduced here.

Automatic review is on hold, including after source changes. Request a fresh re-review after resolving the failure; maintainers can also release the hold through an intentional scanner-policy update.

Next step: If this is a genuine credential, remove and rotate it. If it is an intentional test fixture, a maintainer must review and qualify it.

View the workflow run.

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant