Repository navigation
Cap the Node engine below 27 for App Platform builds - #162
Merged
Merged
Conversation
The DigitalOcean App Platform Node buildpack resolves `>=22.12.0` to Node v27.0.0, which is not released yet (only a v27 alpha is listed and the v27.0.0 tarball returns 404), so every forced rebuild of dusk-docs fails while downloading Node. Capping the range at `<27` makes the buildpack pick the newest Node 26 release, the line the last successful build used. CI keeps using `.nvmrc` (22.12.0). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
HDauven
marked this pull request as ready for review
November 2, 2026 15:37
HDauven
approved these changes
Nov 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The 2026-11-02 forced rebuild of the
dusk-docsApp Platform app failed before building anything:package.jsonallowsnode >=22.12.0, and the buildpack now resolves that to v27.0.0. Node 27 is not released: nodejs.org lists only a v27 alpha, and the v27.0.0 tarball returns 404. Every docs deploy fails until the range is capped.This changes
engines.nodeto>=22.12.0 <27inpackage.jsonand the matching root entry inpackage-lock.json. The buildpack then picks the newest Node 26 release (26.13.0, tarball available), the line the last successful build (26 Oct) used. CI is unaffected: it reads.nvmrc(22.12.0).Validation
engines.nodechanges, in both files. No dependency or lockfile resolution changes.dusk-docsand confirm the build log resolves a v26.x Node and the deploy goes live.🤖 Generated with Claude Code