Neon integration causing GitHub PR to show green check when Vercel build fails

When a Vercel preview build fails, it is supposed to update the Check on the associated GitHub PR to a failed state, which would make the commit show a red X instead of a green checkmark.

This is not happening in our project. Failed builds still show up with a green check.

I’ve asked Vercel support about this, and they say the Neon integration is causing this bug.

I’ve had a look at this deployment and I can see it’s currently linked to the Neon integration, which can cause this specific issue due to the way it creates and updates the database URLs on the project.

This leaves us in a rather untenable situation. Either we disable the Neon integration and have to manually fiddle with configuration every time a new branch is pushed, or we have to manually check that the Vercel build actually succeeded before merging a PR. Neither option is good. We’ve already accidentally merged a failing PR because of this.

Is there anything I can do to fix the issue, or are there any plans for Neon to fix the integration?

Hi @josh373 :wave:

Unfortunately, this issue will most likely not go away soon due to how the integration is built (Vercel’s API has some constraints that prevent us from fixing the issue you’re running into). So we recommend disabling the integration for now.

Alternatively, you can check out this guide that covers how to create a A database for every preview environment using Neon, GitHub Actions, and Vercel - Neon. Here is the code example.

It requires a bit of setup upfront, but after that it should be smooth.

Let us know if you have any questions or run into any other issues.