25 days ago
Im not really sure what you changed internally, but all i did was update an env variable. There is 0 reason the deploy should be breaking. Not a single line of code has changed. This is pretty frustrating.
Attachments
4 Replies
25 days ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • 25 days ago
25 days ago
Hello icarus612,
your build is failing because eslint-visitor-keys@5.0.1 (pulled in by typescript-eslint@8.59.0) requires node 20.19+, 22.13+, or 24+ and your node version on railway is too old so that's the only reason it's breaking ,nothing to do with your env variable change
just add this to your package.json and redeploy:
"engines": { "node": "22" }domehane
Hello **icarus612,** your build is failing because `eslint-visitor-keys@5.0.1` (pulled in by typescript-eslint@8.59.0) requires node 20.19+, 22.13+, or 24+ and your node version on railway is too old so that's the only reason it's breaking ,nothing to do with your env variable change just add this to your package.json and redeploy: ``` "engines": { "node": "22" } ```
25 days ago
I understand what the issue is and how to resolve it. that's not really my question. I'm trying to understand why this keeps happening. I updated a single env var in railway (not even in my repo), and now the build is broken. That means I'm going to have to make a hotfix into main, which is a pain in the butt. The whole point of using railway is to make my deploy process as easy as possible, even if its a little more expensive than the alternatives. But i feel like debugging builds has become a recurring theme for me when deploying to railway. I feel like i spend just as much time debugging builds as i used to with google cloud and aws. I dont want to be making hotfixes every time i go to deploy a branch. Its a pain, and then i have to resync all the other banches with the hotfix. What is the point of having a CI/CD pipeline if i end up having to manually deploy every time anyway because its always failing.
icarus612
I understand _what_ the issue is and how to resolve it. that's not really my question. I'm trying to understand _why_ this keeps happening. I updated a single env var in railway (not even in my repo), and now the build is broken. That means I'm going to have to make a hotfix into main, which is a pain in the butt. The whole point of using railway is to make my deploy process as easy as possible, even if its a little more expensive than the alternatives. But i feel like debugging builds has become a recurring theme for me when deploying to railway. I feel like i spend just as much time debugging builds as i used to with google cloud and aws. I dont want to be making hotfixes every time i go to deploy a branch. Its a pain, and then i have to resync all the other banches with the hotfix. What is the point of having a CI/CD pipeline if i end up having to manually deploy every time anyway because its always failing.
25 days ago
Its one thing to debug builds when you first get a service up and running, but i shouldnt be debugging working services every other PR.
25 days ago
do you have your pnpm-lock.yaml committed to your repo?