chore: update frontmatter date (auto-update)

content/docs/manage/api-keys.md

@@ -4,7 +4,7 @@ enableTableOfContents: true
 redirectFrom:
   - /docs/get-started-with-neon/using-api-keys
   - /docs/get-started-with-neon/api-keys
-updatedOn: '2024-12-04T16:09:42.523Z'
+updatedOn: '2024-12-13T21:17:10.762Z'
 ---
 
 Most actions performed in the Neon Console can also be performed using the [Neon API](https://api-docs.neon.tech/reference/getting-started-with-neon-api). You'll need an API key to validate your requests. Each key is a randomly-generated 64-bit token that you must include when calling Neon API methods. All keys remain valid until deliberately revoked.

content/docs/manage/branches.md

@@ -4,7 +4,7 @@ enableTableOfContents: true
 isDraft: false
 redirectFrom:
   - /docs/get-started-with-neon/get-started-branching
-updatedOn: '2024-12-12T15:31:10.132Z'
+updatedOn: '2024-12-13T21:17:10.765Z'
 ---
 
 Data resides in a branch. Each Neon project is created with a [root branch](#root-branch) called `main`, which is also designated as your [default branch](#default-branch). You can create child branches from `main` or from previously created branches. A branch can contain multiple databases and roles. Plan limits define the number of branches you can create in a project and the amount of data you can store in a branch.

content/docs/manage/databases.md

@@ -2,7 +2,7 @@
 title: Manage databases
 enableTableOfContents: true
 isDraft: false
-updatedOn: '2024-08-13T15:31:30.510Z'
+updatedOn: '2024-12-13T21:17:10.765Z'
 ---
 
 A database is a container for SQL objects such as schemas, tables, views, functions, and indexes. In the [Neon object hierarchy](/docs/manage/overview), a database exists within a branch of a project. While there is no strict limit on the number of databases you can create, we recommend keeping it under 500 per branch.

content/docs/manage/endpoints.md

@@ -2,7 +2,7 @@
 title: Manage computes
 enableTableOfContents: true
 isDraft: false
-updatedOn: '2024-12-13T20:52:57.588Z'
+updatedOn: '2024-12-13T21:17:10.766Z'
 ---
 
 A primary read-write compute is created for your project's [default branch](/docs/reference/glossary#default-branch).

content/docs/manage/orgs-api.md

@@ -1,7 +1,7 @@
 ---
 title: Manage Organizations using the Neon API
 enableTableOfContents: true
-updatedOn: '2024-11-29T18:50:41.470Z'
+updatedOn: '2024-12-13T21:17:10.767Z'
 ---
 
 Learn how to manage Neon Organizations using the Neon API, including creating and using organization-specific API keys, creating projects, transferring projects, and retrieving consumption metrics.

content/docs/manage/projects.md

@@ -5,7 +5,7 @@ isDraft: false
 subtitle: Learn how to manage Neon projects from the Neon Console or the Neon API.
 redirectFrom:
   - /docs/get-started-with-neon/projects
-updatedOn: '2024-12-13T20:52:57.588Z'
+updatedOn: '2024-12-13T21:17:10.767Z'
 ---
 
 With Neon, everything starts with the project. It is the top-level object in the [Neon object hierarchy](/docs/manage/overview). A project can hold as many databases and branches as your application or workflow needs. However, [plan limits](/docs/introduction/plans) define how many projects you can create.

content/docs/manage/roles.md

@@ -4,7 +4,7 @@ enableTableOfContents: true
 isDraft: false
 redirectFrom:
   - /docs/manage/users
-updatedOn: '2024-08-13T15:31:30.511Z'
+updatedOn: '2024-12-13T21:17:10.768Z'
 ---
 
 In Neon, roles are Postgres roles. Each Neon project is created with a Postgres role that is named for your database. For example, if your database is named `neondb`, the project is created with a role named `neondb_owner`. This role owns the database that is created in your Neon project's default branch.

content/docs/shared-content/manage-api-keys.md

@@ -1 +1,4 @@
+---
+updatedOn: '2024-12-13T21:17:10.768Z'
+---
 <Admonition type="note">To learn more about the types of API keys you can create — personal, organization, or project-scoped — see [Manage API Keys](/docs/manage/api-keys).</Admonition>