Skip to content

Use Node 26 for CI tooling - #180

Merged
kvz merged 1 commit into
mainfrom
node26-ci
Oct 21, 2026
Merged

kvz merged 1 commit into
mainfrom
node26-ci

Conversation

@kvz

@kvz kvz commented Oct 21, 2026 •

Copy link
Copy Markdown
Owner

CI tooling should exercise the requested Node 26 Current runtime after the security update in #179.

Select ^26.12.1 with fresh patch resolution on Linux and macOS, and install standalone Corepack 0.36.0 before enabling Yarn. Keep the published Node engine range and the separate Bash 3.2 Docker lane unchanged.

Validation on authenticated Node 26.12.1: Yarn 3.6.0 immutable install, the full shell lint suite with CI’s SHELLCHECK_SEVERITY=warning, and all acceptance tests passed. Workflow structure validation and git diff --check passed. Council review (two reviewers and arbiter, without posting): No issues found. Hosted CI passed Linux and macOS on actual Node 26.12.1, plus the unchanged Bash 3.2 Docker lane. No release was executed.

🤖 Claimed by kvz on framework1/bash3boilerplate since 2026-10-21 · resume: codex resume 01a15ffa-fb3d-7310-8b55-01c2ae2a4b41

@kvz kvz self-assigned this Oct 21, 2026
@kvz
kvz marked this pull request as ready for review October 21, 2026 19:49
@kvz
kvz merged commit 7012aa8 into main Oct 21, 2026
3 checks passed
@kvz
kvz deleted the node26-ci branch October 21, 2026 21:08
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