Merge pull request #2862 from neondatabase/bgrenon-changelog-stashed-…

…02-07

docs: 2025-02-07 changelog

content/changelog/2025-02-07.md

@@ -0,0 +1,118 @@
+---
+description: Query monitoring, 1Password support, and more
+---
+
+## Monitor queries in the Neon Console
+
+Currently available to members in our [Early Access Program](https://console.neon.tech/app/settings/early-access), you can now monitor your active queries and query history from the **Monitoring** page in your Neon project.
+
+![Neon query history](/docs/relnotes/query_history_relnotes.png)
+
+- The **Active Queries** view displays up to 100 currently running queries for the selected **Branch**, **Compute**, and **Database**.
+- The **Query History** view shows the top 100 previously run queries for the selected **Branch**, **Compute**, and **Database**. Queries can be sorted by **Frequency** or **Average time**.
+
+For more about these new monitoring options, see [Monitor active queries](/docs/introduction/monitor-active-queries) and [Monitor query history](/docs/introduction/monitor-query-history).
+
+## Save your connection details to 1Password
+
+If you've got the [1Password](https://1password.com/) browser extension, you can now save your database connection details to 1Password directly from the Neon Console. In your **Project Dashboard**, click **Connect**, then click **Save in 1Password**.
+
+![1Password button on connection modal](/docs/relnotes/1_password_button.png)
+
+## Renamed Neon Authorize to Neon RLS Authorize
+
+We've renamed our JWT-based authorization feature to **Neon RLS Authorize** to better reflect its core value: connecting your authentication provider's JWTs with Postgres Row-Level Security (RLS) policies. You can now find this feature under **Settings > RLS Authorization** in the Neon Console.
+
+![RLS Authorize in the Settings page](/docs/relnotes/rls_authorize.png)
+
+Learn more about [Neon RLS Authorize](/docs/guides/neon-rls-authorize) or try our [tutorial](/docs/guides/neon-rls-authorize-tutorial).
+
+## Renamed Neon Identity to Neon Auth
+
+We've also renamed our Early Access auth integration feature to **Neon Auth**. Neon Auth lets you automatically sync user profiles from your authentication provider to your database. Learn more about it in [Neon Auth](/docs/guides/neon-auth).
+
+Or sign up to the [Early Access Program](https://console.neon.tech/app/settings/early-access) to try it out.
+
+## Scheduled updates on Free & coming soon to Launch and Scale
+
+Two weeks ago, we announced _scheduled updates_ for Neon, including Postgres version upgrades, security patches, and Neon feature enhancements.
+
+This week, we introduced the **Updates** page in your **Project Settings**. Free Plan users get update notices 24 hours in advance. Updates, which take only a few seconds, are applied at the scheduled time or the next time your compute restarts.
+
+![Free plan updates UI](/docs/manage/free_plan_updates.png)
+
+Launch and Scale Plan users will start seeing update notices in another week or so. We aim to provide 7 days' notice for updates on paid plans. Paid users can also choose a preferred update window — you can do that now, well ahead of any planned updates.
+
+![Paid plan updates UI](/docs/manage/paid_plan_updates.png)
+
+We also support checking for scheduled updates using the [Neon API](/docs/manage/updates#check-for-updates-using-the-neon-api).
+
+For more information about scheduled updates, see our [Updates documentation](/docs/manage/updates). If you have questions, please reach out to us on [Discord](https://discord.gg/92vNTzKDGp) or [contact Neon Support](https://console.neon.tech/app/projects?modal=support).
+
+<details>
+
+<summary>**Fixes & improvements**</summary>
+
+- **Postgres extension updates**
+
+  We updated the [pg_mooncake](/docs/extensions/pg_mooncake) extension version to 0.1.1.
+
+  If you installed this extension previously and want to upgrade to the latest version, please refer to [Update an extension version](/docs/extensions/pg-extensions#update-an-extension-version) for instructions.
+
+- **Time Travel connections**
+
+  Ephemeral computes, used for [Time Travel connections](/docs/guides/time-travel-assist), now use a compute size of 0.50 CU (0.50 vCPU, 2 GB RAM). This is up from the 0.25 CU size used previously. For more, see [Time Travel — Billing considerations](/docs/guides/time-travel-assist#billing-considerations).
+
+- **Console updates**
+
+  - We've updated the **Usage** section on the **Billing** page to make it easier to track your plan allowances, extras, and total usage.
+  - The **Schema-only branch** option on the **Create new branch modal** is now disabled when you reach the root branch limit for your project. For details, see [Schema-only branches allowances](/docs/guides/branching-schema-only#schema-only-branch-allowances).
+
+- **Support for CREATE ROLE ... NOLOGIN**
+
+  Neon now supports creating Postgres roles with the `NOLOGIN` attribute. This allows you to define roles that cannot authenticate but can be granted privileges.
+
+  ```sql
+  CREATE ROLE my_role NOLOGIN;
+  ```
+
+  Roles with `NOLOGIN` are commonly used for permission management.
+
+  Support for `NOLOGIN` was also extended to the Neon API and CLI:
+
+  - The Neon API [Create role](https://api-docs.neon.tech/reference/createprojectbranchrole) endpoint now has a `no_login` attribute.
+  - The Neon CLI [`neon roles create`](/docs/reference/cli-roles#create) command now supports a `--no-login` option.
+
+- **CLI support for schema-only branches**
+
+  We added CLI support for our recently introduced [schema-only branches](/docs/guides/branching-schema-only) feature. You can now create a schema-only branch from the CLI using the `--schema-only` option with the [`neon branches create`](/docs/reference/cli-branches#create) command.
+
+  ```bash
+  neon branches create --schema-only
+  ```
+
+- **Branch archiving**
+
+  Neon now limits each project to 100 unarchived branches. Branches older than 14 days and inactive for more than 24 hours are automatically archived to cost-efficient storage. No action is needed to unarchive a branch—it happens automatically when accessed, usually without noticeable performance impact. If you exceed the 100-unarchived branch limit, Neon will archive branches more quickly to stay within the limit. To learn more, see [Branch archiving](/docs/guides/branch-archiving).
+
+- **Vercel Native Integration**
+
+  Fixed an authentication issue that prevented creating another user from a Vercel team in Neon.
+
+- **Vercel Previews Integration**
+
+  - The [Neon Vercel Previews Integration](/docs/guides/vercel-previews-integration) now supports deployments to [Vercel custom environments](https://vercel.com/docs/deployments/custom-environments). However, [automated branch deletion](/docs/guides/vercel-previews-integration#automatic-deletion) does not remove environment variables created by the Neon integration in custom environments. These variables must be deleted manually in the Vercel dashboard.
+  - Fixed an issue where preview deployments in Vercel custom environments were incorrectly recreated in the preview environment instead of the intended custom environment. Additionally, addressed a problem where preview deployments triggered via the [Vercel CLI](https://vercel.com/docs/cli) failed to be recreated due to missing Git information in the Get Deployment API response. Deployments now correctly redeploy when Git information is unavailable.
+  - For Neon branches created for Vercel preview deployments, we now show the Vercel preview deployment URL and the associated GitHub pull request on the **Branches** page in the Neon Console.
+
+- **Fixes**
+
+  - Resolved an issue where the **System operations** tab on the **Monitoring** page could display system operations from more than one project when switching between projects.
+  - Resolved an issue where the branches list in the Neon Console did not immediately update after restoring a branch.
+  - Fixed a time format issue on the project settings **Updates** page where displayed time values were inconsistent, with one shown in UTC and another in local time.
+  - Fixed an issue related to resetting account passwords and changing account emails.
+  - Fixed a concurrency issue where two branches created from the same parent in close succession collided. Previously, the operations on the parent did not complete fast enough for both create branch operations to work.
+  - Fixed an email validation issue on the **Feedback** form in the Neon Console.
+  - Fixed an issue in the **Neon SQL Editor** where the compute status in the compute drop-down menu remained _Idle_ after running a query.
+
+</details>

content/docs/extensions/pg-extensions.md

@@ -120,7 +120,9 @@ ALTER EXTENSION vector UPDATE TO '0.7.0';
 ```
 
 <Admonition type="important">
-When Neon releases a new extension or new extension version, a compute restart is required to make the new extension or extension version available for installation or update. A compute restart may occur on its own due to Neon's default [scale to zero](/docs/introduction/scale-to-zero) behavior. However, if your compute never restarts because you disabled scale to zero or because your compute is constantly active, you may need to force a restart. To force a restart, you can issue [Restart endpoint](https://api-docs.neon.tech/reference/restartprojectendpoint) API call. Please be aware that restarting a compute temporarily interrupts any connections currently using the compute.
+When Neon releases a new extension or new extension version, a compute restart is required to make the new extension or extension version available for installation or update. A compute restart may occur on its own due to Neon's default [scale to zero](/docs/introduction/scale-to-zero) behavior. However, if your compute never restarts because you disabled scale to zero or because your compute is constantly active, you may need to force a restart. To force a restart, you can issue [Restart endpoint](https://api-docs.neon.tech/reference/restartprojectendpoint) API call (a temporary [compute resize](/docs/manage/endpoints#edit-a-compute) will also resize your compute). Please be aware that restarting a compute temporarily interrupts any connections currently using the compute.
+
+Extensions installations and updates are automatically applied to any read replica computes on the same branch as your primary compute the next time the read replica compute restarts.  
 </Admonition>
 
 ## Extension support notes

content/docs/guides/branching-schema-only.md

@@ -13,7 +13,7 @@ Neon supports creating schema-only branches, letting you create branches that re
 
 You can create schema-only branches in the Neon Console or using the Neon API, in much the same way you create any Neon branch. Support for the Neon CLI will come in a future release.
 
-<Tabs labels={["Neon Console", "API"]}>
+<Tabs labels={["Neon Console", "CLI", "API"]}>
 
 <TabItem>
 
@@ -31,6 +31,18 @@ To create a schema-only branch from the Neon Console:
 
 <TabItem>
 
+To create a schema-only branch using the Neon CLI:
+
+```bash
+neon branch create --schema-only
+```
+
+If you have more than one project, you'll need to specify the `--project-id` option. See [Neon CLI - branch create](/docs/reference/cli-branches#create).
+
+</TabItem>
+
+<TabItem>
+
 <Admonition type="note">
 The API is in Beta and subject to change.
 </Admonition>
@@ -147,3 +159,5 @@ There are certain allowances associated with schema-only branches:
 | Launch   | 5                                 | 3 GB                                             |
 | Scale    | 10                                | 5 GB                                             |
 | Business | 25                                | 20 GB                                            |
+
+Once you use up your root branch allowance, you will not be able to create additional schema-only branches. You will be required to remove existing root branches first.

content/docs/guides/time-travel-assist.md

@@ -26,7 +26,7 @@ However, you can see the history of operations related to the creation and delet
 
 ### How long do ephemeral endpoints remain active
 
-The ephemeral endpoints are created according to your configured [default compute size](/docs/manage/projects#reset-the-default-compute-size). An ephemeral compute remains active for as long as you keep running queries against it. After 30 seconds of inactivity, the timeline is deleted and the endpoint is removed.
+The ephemeral endpoints are created with a .50 CU compute size, which has 0.50 vCPU size with 2 GB of RAM. An ephemeral compute remains active for as long as you keep running queries against it. After 30 seconds of inactivity, the timeline is deleted and the endpoint is removed.
 
 ### History retention
 
@@ -183,5 +183,5 @@ The ephemeral endpoints used to run your Time Travel queries do contribute to yo
 
 A couple of details to note:
 
-- The endpoints are shortlived. They are suspended 10 seconds after you stop querying.
-- Since these endpoints are created according to your default compute size (which applies to all new branch computes you create), you may want to reduce this default if you're performing a lot of time-travel queries for troubleshooting.
+- The endpoints are shortlived. They are suspended 30 seconds after you stop querying.
+- Ephemeral endpoints are created with a .50 CU compute size, which has 0.50 vCPU size with 2 GB of RAM. This is Neon's second smallest compute size. For more about compute sizes in Neon, see [How to size your compute](/docs/manage/endpoints#how-to-size-your-compute). For more about compute usage and billing, see [Usage metrics — Compute](/docs/introduction/usage-metrics#compute).

content/docs/introduction/monitor-query-history.md

@@ -14,7 +14,7 @@ You can monitor query history for your Neon project from the **Monitoring** page
 2. Go to **Monitoring**.
 3. Select the **Query History** tab.
 
-The query history view shows the top 100 previously run queries for the selected **Branch**, **Compute**, and **Database**. Queries can be sorted by **Frequency** or **Average time**. Use the **Refresh** button to load the latest queries.
+The **Query History** view shows the top 100 previously run queries for the selected **Branch**, **Compute**, and **Database**. Queries can be sorted by **Frequency** or **Average time**. Use the **Refresh** button to load the latest queries.
 
 ![Neon query history tab](/docs/introduction/query_history.png)
 

content/docs/manage/updates.md

@@ -31,6 +31,7 @@ Neon applies updates to computes based on the following rules:
 - Computes that have been active for 30 days or more receive updates.
 - Computes that are restarted receive available updates immediately.
 - Computes in a transition state (e.g., shutting down or restarting) at the time of an update are not updated.
+- Computes larger than 8 CU are not updated.
 
 If a compute is excluded from an update, Neon will apply the missed update with the next scheduled update, assuming the compute meets the update criteria mentioned above.
 

content/docs/reference/cli-branches.md

@@ -133,6 +133,7 @@ In addition to the Neon CLI [global options](/docs/reference/neon-cli#global-opt
 | `--suspend-timeout` | Duration of inactivity in seconds after which the compute is automatically suspended. The value `0` means use the global default. The value `-1` means never suspend. The default value is `300` seconds (5 minutes). The maximum value is `604800` seconds (1 week). | number  |                                                     |
 | `--cu`              | The number of Compute Units. Could be a fixed size (e.g. "2") or a range delimited by a dash (e.g. "0.5-3").                                                                                                                                                          | string  |                                                     |
 | `--psql`            | Connect to a new branch via `psql`. `psql` must be installed to use this option.                                                                                                                                                                                      | boolean |                                                     |
+| `--schema-only`     | Create a schema-only branch. Requires exactly one read-write compute.                                                                                                                                                                                                 | boolean |                                                     |
 
 <Admonition type="note">
 When creating a branch from a protected parent branch, role passwords on the child branch are changed. For more information about this Protected Branches feature, see [New passwords generated for Postgres roles on child branches](/docs/guides/protected-branches#new-passwords-generated-for-postgres-roles-on-child-branches).
@@ -292,6 +293,12 @@ When creating a branch from a protected parent branch, role passwords on the chi
   neon branch create --psql -- -c "SELECT version()"
   ```
 
+- Create a schema-only branch:
+
+  ```bash
+  neon branch create --schema-only
+  ```
+
 ## reset
 
 This command resets a child branch to the latest data from its parent.

content/docs/reference/cli-roles.md

@@ -89,12 +89,13 @@ neon roles create [options]
 
 In addition to the Neon CLI [global options](/docs/reference/neon-cli#global-options), the `create` subcommand supports these options:
 
-| Option           | Description                                                                                   | Type   |                      Required                       |
-| ---------------- | --------------------------------------------------------------------------------------------- | ------ | :-------------------------------------------------: |
-| `--context-file` | [Context file](/docs/reference/cli-set-context#using-a-named-context-file) path and file name | string |                                                     |
-| `--project-id`   | Project ID                                                                                    | string | Only if your Neon account has more than one project |
-| `--branch`       | Branch ID or name                                                                             | string |                                                     |
-| `--name`         | The role name. Cannot exceed 63 bytes in length.                                              | string |                       ✓                       |
+| Option           | Description                                                                                   | Type    |                      Required                       |
+| ---------------- | --------------------------------------------------------------------------------------------- | ------- | :-------------------------------------------------: |
+| `--context-file` | [Context file](/docs/reference/cli-set-context#using-a-named-context-file) path and file name | string  |                                                     |
+| `--project-id`   | Project ID                                                                                    | string  | Only if your Neon account has more than one project |
+| `--branch`       | Branch ID or name                                                                             | string  |                                                     |
+| `--name`         | The role name. Cannot exceed 63 bytes in length.                                              | string  |                       ✓                       |
+| `--no-login`     | Create a passwordless role that cannot login                                                  | boolean |                                                     |
 
 If a branch ID or name is not provided, the command creates a role in the default branch of the project.