[🐛 Bug]: new branches are NOT using NODE_VERSION

[jmonster]

next-on-pages environment related information

System:
Platform: darwin
Arch: arm64
Version: Darwin Kernel Version 24.1.0: Thu Nov 14 18:19:02 PST 2024; root:xnu-11215.41.3~13/RELEASE_ARM64_T8132
CPU: (10) arm64 Apple M4
Memory: 16 GB
Shell: /opt/homebrew/bin/fish
Package Manager Used: pnpm (9.15.0)

Relevant Packages:
@cloudflare/next-on-pages: 1.13.7
vercel: N/A
next: N/A

Description

I've successfully deployed my main branch, and can see it loading the version of Node defined by NODE_VERSION. However, I've subsequently pushed out other branches and they do not adhere to this ENV. All builds from other branches are failing, citing the wrong version of node, while my main continues to re-deploy properly using the correct one.

I've gone so far as to take the branch that works, main, and push it as-is to another branch name, which promptly fails.

Lastly, we just merged our changes into main and sure enough -- that branch continues to deploy successfully from the OG working branch [created yesterday]

Working Branch (main)

Failing Branch (any other)

Reproduction

https://github.com/outerbase/workflows

Pages Deployment Method

None

Pages Deployment ID

No response

Additional Information

No response

Would you like to help?

• Would you like to help fixing this bug?