Node.js `v24` became LTS recently, causing CI failures due to `V8` API incompatibilities with isolated-vm `v5.x`. Pinning to `v22` aligns with our production environment (Alpine `v3.22.1` ships Node.js `v22.16.0`) and ensures build stability. `isolated-vm v6+` will be required for Node.js `v24` support and will be addressed in a future dependency update cycle.
40 lines
910 B
YAML
40 lines
910 B
YAML
name: Node.js CI
|
|
|
|
on:
|
|
push:
|
|
branches: [main, next, patch]
|
|
pull_request:
|
|
branches: [main, next, patch]
|
|
|
|
jobs:
|
|
test:
|
|
name: Test
|
|
runs-on: ubuntu-latest
|
|
|
|
strategy:
|
|
matrix:
|
|
# Pinned to Node.js 22 to maintain compatibility with isolated-vm v5.x
|
|
# Node.js 24 requires isolated-vm v6+ due to V8 API changes
|
|
# TODO: Upgrade to isolated-vm v6 and support Node.js 24 in future dependency update cycle
|
|
node-version: ["22"]
|
|
|
|
steps:
|
|
- name: Checkout
|
|
uses: actions/checkout@v4
|
|
|
|
- name: Setup environment
|
|
run: mv .env.example .env
|
|
|
|
- name: Setup node
|
|
uses: actions/setup-node@v4
|
|
with:
|
|
node-version: ${{ matrix.node-version }}
|
|
|
|
- name: Setup pnpm
|
|
uses: pnpm/action-setup@v3
|
|
with:
|
|
version: 8
|
|
run_install: true
|
|
|
|
- name: Run tests
|
|
run: pnpm test
|