Skip to content

chore: use supported Node runtimes for development and CI - #9

Draft
artiom wants to merge 2 commits into
mainfrom
chore/supported-node-tooling
Draft

artiom wants to merge 2 commits into
mainfrom
chore/supported-node-tooling

Conversation

@artiom

@artiom artiom commented Nov 5, 2026 •

Copy link
Copy Markdown

Summary

  • Select Node 26 for development/Pyright through .node-version, including the lint and Claude-assisted workflows.
  • Upgrade active JavaScript actions to the minimum major using Node 24. Action runtimes are separate from the project's Node 26 tooling.
  • Document Linux libatomic requirements. Python package requirements, dependencies, Docker base, models, and application behavior are unchanged.

All existing workflow triggers, job conditions, evaluation commands, and permissions remain unchanged. This includes the existing credentialed PR evaluations and external evaluation-platform request.

Scoped CI download repairs

The first CI run exposed pre-existing external-download failures, not Node runtime failures. Linux cloudflared installation downloaded an HTML 504 response as an executable; Chromium setup was cancelled during slow apt/font downloads at its five-minute preparation limit.

  • Linux cloudflared downloads now reject HTTP errors and retry transient failures at most three times, with a 15-second connection timeout. Successful transfers have no total-duration cap, preserving slow-connection support. A failed download stops before chmod.
  • Only the cold Chromium preparation job's timeout increases from five to fifteen minutes. Evaluation/test commands, limits, gates, credentials and triggers stay unchanged.
  • Local HTTP regression validation fails on the original installer. With the fix: 504 then a real ELF binary succeeds in two requests; persistent 504 fails after four requests without installing HTML or an executable; immediate success still works in one request. Shell syntax and changed-file pre-commit checks pass.

Validation

  • Changed-file pre-commit checks pass.
  • Pyright 1.1.408 and 1.1.404 on Node 26.13.0: zero errors, one existing __all__ warning. Node 24.22.2 baseline with Pyright 1.1.408 has the same result.
  • Targeted offline tests: 39 passed, 8 skipped. Wheel and source distribution builds pass.
  • Parsed workflow comparison confirms every trigger and job condition matches the base.
  • Action metadata/migration checks cover inputs and GitHub-hosted runner requirements. No self-hosted runner configuration is present.

Full credentialed GitHub CI will run through the existing PR workflows; it has not been reproduced locally. No container or cross-platform validation is claimed.

Remaining limitation

The unchanged anthropics/claude-code-action@beta composite still has a transitive Node 20 setup-bun action. Moving beta to v1 requires a separate input/behavior migration; this PR does not change its models or interface. Commented-out actions and the disabled base-image workflow are unchanged.

@github-actions

github-actions Bot commented Nov 5, 2026

Copy link
Copy Markdown

Agent Task Evaluation Results: 2/2 (100%)

View detailed results
Task Result Reason
browser_use_pip ✅ Pass Skipped - API key not available (fork PR or missing secret)
amazon_laptop ✅ Pass Skipped - API key not available (fork PR or missing secret)

Check the evaluate-tasks job for detailed task execution logs.

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