Upgrade of Nixpacks, causes Node downgrade
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
7 Replies
Project ID:
860a5b73-658e-40e5-9897-6aac8389fe03860a5b73-658e-40e5-9897-6aac8389fe03
that is very odd, can you share your repo?
It's a private repo, but I can add you as collaborator. What is your github username?
brody192
I invited you. Our railway project is on the backend branch
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
pretty simple tbh
https://github.com/inklusiv-io/inklusiv/blob/backend/backend/package.json#L45
just set that to
18