Upgrade of Nixpacks, causes Node downgrade | Railway | Page 1

loud rock Jun 14, 2023, 2:40 PM

#

Hi there

I pushed an update to our Strapi backend hosted on railway today, and suddenly it can't read an environment variable with a private key.

After investigating the build logs, i see my build from May 30, is using Nixpacks v1.5.1 and node 16 and the build from today is using Nixpacks v1.9.0 and node 14.

Could someone explain to me what is going on?

Best regards

oblique tapirBOT Jun 14, 2023, 2:40 PM

#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

neat harnessBOT Jun 14, 2023, 2:40 PM

#

Project ID: 860a5b73-658e-40e5-9897-6aac8389fe03

loud rock Jun 14, 2023, 2:42 PM

#

860a5b73-658e-40e5-9897-6aac8389fe03

candid junco Jun 14, 2023, 3:49 PM

#

that is very odd, can you share your repo?

loud rock Jun 14, 2023, 9:15 PM

#

It's a private repo, but I can add you as collaborator. What is your github username?

candid junco Jun 14, 2023, 9:25 PM

#

brody192

loud rock Jun 15, 2023, 8:43 AM

#

I invited you. Our railway project is on the backend branch

loud rock Jun 15, 2023, 1:34 PM

#

Just tried updating Strapi to the latest version, but the same thing happens. Nixpacks 1.9, but nodejs14.

I don't know what causes it to select (or default?) to 14

candid junco Jun 15, 2023, 3:18 PM

#

pretty simple tbh

#

https://github.com/inklusiv-io/inklusiv/blob/backend/backend/package.json#L45

#

just set that to 18

#Upgrade of Nixpacks, causes Node downgrade