> Full Neon documentation index: https://neon.com/docs/llms.txt
> IMPORTANT: If this page contains inaccurate or outdated information, report it: POST to https://neon.com/api/docs-feedback with {"feedback": "describe the issue", "path": "/changelog/2024-01-26"}

# Vercel integration updates, fixes & updates, and more

### New default Postgres version

The default version for newly created Neon projects is now Postgres 16. Neon continues to support Postgres 14 and 15.

### Configurable environment variables for Vercel Integration

- The [Neon Vercel Integration](https://vercel.com/integrations/neon) is now supported with applications sourced in GitLab and Bitbucket. Previously, the integration only worked with applications stored in GitHub.

- The environment variables set by the Neon Vercel Integration when you add the integration to a Vercel project have changed. Previously, the integration set the following Postgres variables:

  - `DATABASE_URL`
  - `PGHOST`
  - `PGUSER`
  - `PGDATABASE`
  - `PGPASSWORD`

  The integration now sets **only** the `DATABASE_URL` variable by default, which includes all of the required details for connecting to your Neon database.

  If you prefer to use the other Postgres variables with your application instead of `DATABASE_URL`, you can now configure the variables you want on the **Integrations** page in the Neon console.

  ![Select Vercel variables](https://neon.com/docs/guides/vercel_select_variables.png)

  The variables you select are set in your Vercel project on your next `git push`. For details, see [Manage Vercel integration settings](https://neon.com/docs/guides/neon-managed-vercel-integration#managing-the-integration).

- Fixed an issue that prevented the `DATABASE_URL` variable from being set on the first preview deployment after adding the integration to a Vercel project.

### Fixes & improvements

- The [List projects](https://api-docs.neon.tech/reference/listprojects) API method now returns only projects owned by the current user account. Previously, it also returned projects shared with the current user account. To list projects shared with the current user account, use the [List shared projects](https://api-docs.neon.tech/reference/listsharedprojects) API method instead.
- Added a **Submit feedback** form to the cards on the **Integrations** page in the Neon Console, letting users share their experience with Neon integrations.
- We now expose more details in error messages returned from the Neon proxy for [Neon serverless driver](https://neon.com/docs/serverless/serverless-driver) connections over HTTP.
- Improved the [IP Allow](https://neon.com/docs/introduction/ip-allow) user interface with minor design and copy adjustments.

### What's new in docs?

To help our users unlock the full potential of Postgres, we're building out our Postgres extension documentation. Whether you're a seasoned Postgres user or new to the platform, our new extension guides can help you get started.

- [The pg_stat_statements extension](https://neon.com/docs/extensions/pg_stat_statements)
- [The timescaledb extension](https://neon.com/docs/extensions/timescaledb)
- [The postgis extension](https://neon.com/docs/extensions/postgis)
- [The hstore extension](https://neon.com/docs/extensions/hstore)
- [The citext extension](https://neon.com/docs/extensions/citext)
- [The pg_trgm extension](https://neon.com/docs/extensions/pg_trgm)

See our updated roadmap to learn about upcoming features and share your ideas:

- [Neon roadmap](https://neon.com/docs/introduction/roadmap)

### Success stories

We are excited to announce the launch of our [Success Stories](https://neon.com/case-studies) page on the Neon website. This new page highlights real-world experiences and success stories from our valued partners and customers.

### From the Neon Blog

In case you missed them, be sure to check out our latest blog posts:

- [See you at FOSDEM and FOSDEM PGDay 2024](https://neon.com/blog/see-you-at-fosdem-and-fosdem-pgday-2024)
- [Using Neon's Scale to Zero with Long-Running Applications](https://neon.com/blog-suspend-with-long-running-applications)