Hey there! We've found the following might help you get unblocked faster:

• 🧵 Google API connection problem with n8n

• 🧵 Railway does not update my page?

• 🧵 n8n update failed

If you find the answer from one of these, please let us know by solving the thread!

Heyy!!

If you disconnected the "Source" and can't re-link your GitHub, you can still update n8n by redeploying manually. Go to your Service > Deployments tab > Deploy from GitHub or Docker, or use the "Upload" option to push your updated code or image. If it's a container app, updating the image/tag manually also works.

Hello, I have a problem publishing from the GitHub repository. When I update the repository and publish it, the publishing is canceled and the page cannot be opened.

What is the error coming? You can see that in the deployment/build logs

hulk, what is the actual issue? Isn't your Railway dashboard showing up your repositories?

npm warn config production Use --omit=dev instead.

npm error code EUSAGE

npm error

npm error npm ci can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with npm install before continuing.

npm error

npm error Invalid: lock file's express@5.1.0 does not satisfy express@4.21.2

npm error Missing: path@0.12.7 from lock file

npm error Invalid: lock file's accepts@2.0.0 does not satisfy accepts@1.3.8

npm error Missing: array-flatten@1.1.1 from lock file

npm error Invalid: lock file's body-parser@2.2.0 does not satisfy body-parser@1.20.3

npm error Invalid: lock file's content-disposition@1.0.0 does not satisfy content-disposition@0.5.4

npm error Missing: cookie@0.7.1 from lock file

npm error Invalid: lock file's cookie-signature@1.2.2 does not satisfy cookie-signature@1.0.6

npm error Missing: debug@2.6.9 from lock file

npm error Invalid: lock file's finalhandler@2.1.0 does not satisfy finalhandler@1.3.1

npm error Invalid: lock file's fresh@2.0.0 does not satisfy fresh@0.5.2

npm error Invalid: lock file's merge-descriptors@2.0.0 does not satisfy merge-descriptors@1.0.3

npm error Missing: methods@1.1.2 from lock file

npm error Invalid: lock file's path-to-regexp@8.2.0 does not satisfy path-to-regexp@0.1.12

npm error Invalid: lock file's qs@6.14.0 does not satisfy qs@6.13.0

npm error Invalid: lock file's send@1.2.0 does not satisfy send@0.19.0

npm error Invalid: lock file's serve-static@2.2.0 does not satisfy serve-static@1.16.2

npm error Invalid: lock file's statuses@2.0.2 does not satisfy statuses@2.0.1

npm error Invalid: lock file's type-is@2.0.1 does not satisfy type-is@1.6.18

npm error Missing: utils-merge@1.0.1 from lock file

Remove the package-lock.json file from your code repository, because there are some mismatches in the package.json & the lock file. Then push the same to Railway. Hopefully, it would remove these errors

Did that helped?