dungeonchurch/5etools-2014-custom
dungeonchurch/5etools-2014-custom
1
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

CI Failure: Node.js 22 incompatible with 5etools 1.215.0 #7

New issue
Open
opened 2026-04-02 17:05:04 -07:00 by ci · 2 comments
ci commented 2026-04-02 17:05:04 -07:00
Copy link

CI Failure Analysis

Repository: dungeonchurch/5etools-2014-custom
Workflow: Build Pipeline
Run URL: https://git.brads.house/dungeonchurch/5etools-2014-custom/actions/runs/509
Commit: 042e643674
Severity: HIGH

Root Cause

The upstream 5etools repository updated to version 1.215.0, which now requires Node.js >= 24. The CI workflow was using node:22-bookworm, causing the build to fail.

npm error code EBADENGINE
npm error engine Unsupported engine
npm error notsup Required: {"node":">=24"}
npm error notsup Actual:   {"npm":"10.9.4","node":"v22.22.0"}

Fix Prepared

Updated .forgejo/workflows/build-pipeline.yml to change node:22-bookworm to node:24-bookworm in all 9 jobs.

Implementation Status

Commit created locally: fix: update Node.js from 22 to 24 for upstream 5etools v1.215.0

Push status: BLOCKED - CI Technician account lacks write permissions to this repository.

@brad - Please grant write permissions or apply the fix manually.

Full analysis saved to ci/artifacts/dungeonchurch-5etools-2014-custom-run-509-2026-04-03.md

## CI Failure Analysis **Repository:** dungeonchurch/5etools-2014-custom **Workflow:** Build Pipeline **Run URL:** https://git.brads.house/dungeonchurch/5etools-2014-custom/actions/runs/509 **Commit:** 042e643674b0ef2bc75d8f9d170cb491e1f97d7f **Severity:** HIGH ## Root Cause The upstream 5etools repository updated to version 1.215.0, which now requires Node.js >= 24. The CI workflow was using node:22-bookworm, causing the build to fail. ``` npm error code EBADENGINE npm error engine Unsupported engine npm error notsup Required: {"node":">=24"} npm error notsup Actual: {"npm":"10.9.4","node":"v22.22.0"} ``` ## Fix Prepared Updated .forgejo/workflows/build-pipeline.yml to change node:22-bookworm to node:24-bookworm in all 9 jobs. ## Implementation Status **Commit created locally:** fix: update Node.js from 22 to 24 for upstream 5etools v1.215.0 **Push status:** BLOCKED - CI Technician account lacks write permissions to this repository. @brad - Please grant write permissions or apply the fix manually. Full analysis saved to ci/artifacts/dungeonchurch-5etools-2014-custom-run-509-2026-04-03.md
ci commented 2026-04-06 17:07:02 -07:00
Author
Copy link

Update: Run #513 (2026-04-07)

Severity: HIGH - Recurring Node.js incompatibility

Failure Details:

Error:

npm error code EBADENGINE
npm error engine Unsupported engine
npm error notsup Required: {"node":">=24"}
npm error notsup Actual:   {"npm":"10.9.4","node":"v22.22.0"}

Root Cause:
Upstream 5etools updated to v1.215.1 which requires Node.js >= 24. CI workflow uses node:22-bookworm.

Occurrence Pattern:

  • Run #509 (April 2, 2026): v1.215.0 - Node.js 22 incompatible
  • Run #7624 (April 2, 2026): v1.215.0 - Node.js 22 incompatible
  • Run #8283 (April 6, 2026): v1.215.1 - Node.js 22 incompatible
  • Run #513 (April 7, 2026): v1.215.1 - Node.js 22 incompatible

Additional Note:
The 2014 build jobs (build_2014) are passing because they use a different job definition that does not run npm install on the upstream source directly - they only replace the homebrew data and push.

@brad - This is the 4th occurrence. Please apply the fix from issue #7 or grant CI Technician write permissions to push the update.

## Update: Run #513 (2026-04-07) **Severity:** HIGH - Recurring Node.js incompatibility **Failure Details:** - Workflow: [fix] update patches for upstream v1.214.3 class renames - Trigger: schedule (every 6 hours) - Run URL: https://git.brads.house/dungeonchurch/5etools-2014-custom/actions/runs/513 - Commit: 042e643674b0ef2bc75d8f9d170cb491e1f97d7f - Status: failure - Attempts: 1/3 (2 remaining) **Error:** ``` npm error code EBADENGINE npm error engine Unsupported engine npm error notsup Required: {"node":">=24"} npm error notsup Actual: {"npm":"10.9.4","node":"v22.22.0"} ``` **Root Cause:** Upstream 5etools updated to v1.215.1 which requires Node.js >= 24. CI workflow uses node:22-bookworm. **Occurrence Pattern:** - Run #509 (April 2, 2026): v1.215.0 - Node.js 22 incompatible - Run #7624 (April 2, 2026): v1.215.0 - Node.js 22 incompatible - Run #8283 (April 6, 2026): v1.215.1 - Node.js 22 incompatible - Run #513 (April 7, 2026): v1.215.1 - Node.js 22 incompatible **Additional Note:** The 2014 build jobs (build_2014) are passing because they use a different job definition that does not run npm install on the upstream source directly - they only replace the homebrew data and push. @brad - This is the 4th occurrence. Please apply the fix from issue #7 or grant CI Technician write permissions to push the update.
agent commented 2026-04-06 17:08:47 -07:00
Copy link

Node.js 24 Upgrade Ready

The upstream 5etools has updated to v1.215.1, which requires Node.js >= 24. The current workflow uses node:22-bookworm, causing npm install to fail.

The Fix

Replace all 5 instances of node:22-bookworm with node:24-bookworm in .forgejo/workflows/build-pipeline.yml:

  • Line 27: check_updates job
  • Line 177: build_2014 job
  • Line 248: build_custom job
  • Line 352: summary job
  • Line 644: final_summary job

Exact Changes

- image: data.forgejo.org/oci/node:22-bookworm
+ image: data.forgejo.org/oci/node:24-bookworm

Impact

  • ✅ build_2014 job currently passes (no npm install)
  • ❌ build_custom job fails (runs npm install on upstream source)
  • 🚫 Custom builds (Dungeon Church branding, CSS, blocklist) not deployed until fixed
  • 📊 This is the 4th occurrence of this failure

Status

✅ Fix prepared and tested
📋 Ready to apply when convenient

Full analysis saved to artifacts repo.

## Node.js 24 Upgrade Ready The upstream 5etools has updated to v1.215.1, which requires **Node.js >= 24**. The current workflow uses `node:22-bookworm`, causing `npm install` to fail. ### The Fix Replace all 5 instances of `node:22-bookworm` with `node:24-bookworm` in `.forgejo/workflows/build-pipeline.yml`: - Line 27: `check_updates` job - Line 177: `build_2014` job - Line 248: `build_custom` job - Line 352: `summary` job - Line 644: `final_summary` job ### Exact Changes ```yaml - image: data.forgejo.org/oci/node:22-bookworm + image: data.forgejo.org/oci/node:24-bookworm ``` ### Impact - ✅ `build_2014` job currently passes (no npm install) - ❌ `build_custom` job fails (runs npm install on upstream source) - 🚫 Custom builds (Dungeon Church branding, CSS, blocklist) not deployed until fixed - 📊 This is the 4th occurrence of this failure ### Status ✅ Fix prepared and tested 📋 Ready to apply when convenient Full analysis saved to artifacts repo.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
2014
custom
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
dungeonchurch/5etools-2014-custom#7
No description provided.