---
title: Wrapping up 2024, a reminder to update the Neon CLI, and fixes & improvements
---

### Wrapping up 2024

As 2024 comes to a close, we focused on fixes and improvements this past week. But don’t worry — new features are already in development, and exciting updates are coming soon. We’re looking forward to sharing what’s coming in the new year, and there might even be a few interesting announcements before then. Stay tuned!

### Upgrading to the latest Neon CLI version

If you use the [Neon CLI](/docs/reference/neon-cli), here’s a friendly reminder to upgrade to the latest version. The current version is 2.6.0, and all users should now be on a 2.x version. You can check your Neon CLI version with the following command:

```shell
$ neon --version
2.6.0
```

For upgrade instructions, see [Neon CLI upgrade](/docs/reference/cli-install#upgrade).

If you use the Neon CLI in CI/CD tools like GitHub Actions, you can safely pin it to `@latest`, as we prioritize stability for CI/CD processes. For example, in a GitHub Actions workflow, you can install the latest version with `npm`:

```yaml
- name: Install Neon CLI
  run: npm install -g neonctl@latest
```

<details>

<summary>**Fixes & improvements**</summary>

- **Drizzle Studio update**

  The Drizzle Studio integration that powers the **Tables** page in the Neon Console has been updated. For the latest improvements and fixes, see the [Neon Drizzle Studio Integration Changelog](https://github.com/neondatabase/neon-drizzle-studio-changelog/blob/main/CHANGELOG.md).

- **Console updates**
  - Added a link to the Neon API Reference in the information resources menu of the console.
  - The Support ticket modal now supports file attachments in the Neon Console. Attachments must not exceed 5 MB.
  - You can now sort columns in the branches table on the **Branches** page.
  - The organization account project page now includes an **Integrations** column in the projects table for viewing and adding integrations.

- **Neon Authorize**

  It just keeps getting better. Drizzle ORM introduced a new with `db.$withAuth` method, offering a more convenient way to include user JWTs in queries to Neon.

  ```javascript
  return db
    .$withAuth(authToken)
    .select()
    .from(schema.todos)
    .where(eq(schema.todos.userId, sql`auth.user_id()`))
    .orderBy(asc(schema.todos.insertedAt));
  ```

  Find more examples in our [Neon Authorize tutorial](/docs/guides/neon-authorize-tutorial).

- **Vercel Native Integration**
  - Users of the native Neon integration in Vercel can now view the **Archive storage** metric on the **Usage** page under the **Storage** tab in the Vercel Dashboard. For more details about archive storage in Neon, see [Branch archiving](/docs/guides/branch-archiving).
  - Neon's [IP Allow](/docs/introduction/ip-allow) feature is now available for Vercel-managed organizations. This feature is supported on Neon Scale and Business plans.

- **Azure Integration**

  Support is now available for transferring projects from Neon personal accounts to Azure-created Neon organizations. Project transfers are only supported for Neon projects created in an Azure region. For more details, see [Transfer Neon projects to an Azure-created Neon organization](/docs/introduction/billing-azure-marketplace#transfer-existing-neon-projects-to-an-azure-created-neon-organization).

- **Neon API**

  We added `204` response definitions to `DELETE` endpoints for scenarios where a branch, database, role, or endpoint does not exist or has already been deleted. A 204 response code indicates a successful operation that does not return content.

- **Fixes**
  - Fixed an issue in the console where an error toast was not displayed when offline or when the server was unreachable. A `Network error` is now returned in such cases.
  - Corrected a usability issue where the **Project Creation** modal defaulted to an error state, requiring users to adjust autoscaling settings before creating a project.
  - Resolved an issue where users encountered a confusing error message when attempting to link a Microsoft account already logged in with the same email.
  - Fixed a drag-to-zoom failure on **Monitoring** page graphs that occurred when dragging from left to right and releasing the cursor outside of the graph area.
  - Fixed an issue preventing the addition of a read-write compute to a branch if another branch in the project had a read-write compute.
  - Addressed a `Something went wrong` error in the console related to the loading of an organization account.
  - Fixed an issue that prevented **Ctrl+C** query cancellation requests for connections using [passwordless authentication](/docs/connect/passwordless-connect).

</details>