vybekiit 0.7.21 → 0.7.23
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -160,7 +160,7 @@ The above `init` command will install the Neon CLI, but the CLI can also be inst
|
|
|
160
160
|
|
|
161
161
|
These commands are included in the `init` command but can be run manually as needed.
|
|
162
162
|
|
|
163
|
-
1. `neon link` — Interactively links the workspace to a Neon org, project, and branch, writing the IDs to a git-ignored `.neon` file. Run once per project. Once linked, project- and branch-scoped commands no longer need `--project-id` or `--branch` (for example, `neon branch list`).
|
|
163
|
+
1. `neon link` — Interactively links the workspace to a Neon org, project, and branch, writing the IDs to a git-ignored `.neon` file. Run once per project. Once linked, project- and branch-scoped commands no longer need `--project-id` or `--branch` (for example, `neon branch list`).
|
|
164
164
|
2. `neon checkout <branch-name>` — Pins a different branch in `.neon`, creating it if it doesn't exist yet, and pulls that branch's env. It drives the [Branch-First Dev Flow](#branch-first-dev-flow) described below.
|
|
165
165
|
3. `neon config init` — Initializes a `neon.ts` file, which declares how you provision and manage Neon services, in the root of the project.
|
|
166
166
|
4. `neon env pull` — Fetches the current branch's Neon environment variables (`DATABASE_URL`, …) into your existing `.env`, or `.env.local` if you don't have one (override the target with `--file`). No branch ID needed; it reads `.neon`. **`link` and `checkout` run this for you by default**, so you rarely call it directly.
|
|
@@ -187,7 +187,7 @@ If the Getting Started account check found credentials, use them. If a command w
|
|
|
187
187
|
|
|
188
188
|
If they cannot sign in or provide a key right now, ask before using Claimable Neon. Continue only after they say yes. That is a temporary workaround.
|
|
189
189
|
|
|
190
|
-
If there is no Neon account yet, follow [references/claimable-neon.md](https://neon.com/docs/ai/skills/neon/references/claimable-neon.md). Do not run `neon init --agent` or `neon auth` on this path; those need a human Neon account. If `neon claim` is missing, the reference has the REST fallback.
|
|
190
|
+
If there is no Neon account yet, follow [references/claimable-neon.md](https://neon.com/docs/ai/skills/neon/references/claimable-neon.md). Do not run `neon init --agent` or `neon auth` on this path; those need a human Neon account. If `neon claim` is missing, the reference has the REST fallback. Unclaimed projects expire at `project_expires_at` (72 hours today). Claim codes expire in `expires_in` (15 minutes today). Add Auth or the Data API with `neon.ts` and `neon deploy` before or after claim.
|
|
191
191
|
|
|
192
192
|
Requests for neon.new, Claimable Postgres, claimable.neon.tech, instant Postgres, or a no-signup database are the same path.
|
|
193
193
|
|
|
@@ -37,13 +37,43 @@ export default defineConfig({
|
|
|
37
37
|
|
|
38
38
|
Before claim, Postgres is always granted; Auth and the Data API are granted when requested. Functions, Object Storage, and AI Gateway come back with `granted: false` and `reason: "requires_claim"`. The CLI prints those as `denied_capabilities`. Report what you were given. Do not retry or strip them.
|
|
39
39
|
|
|
40
|
-
After create, report the `project_id`, `project_expires_at`, and any denied capabilities. Do not invent the window.
|
|
40
|
+
After create, report the `project_id`, `project_expires_at`, and any denied capabilities. Do not invent the window. Unclaimed projects expire at `project_expires_at` (72 hours today). That clock is independent of the claim code.
|
|
41
41
|
|
|
42
42
|
## Claim
|
|
43
43
|
|
|
44
44
|
Do not mint a claim URL until the human is ready. Opening the URL does not freeze access. Continuing to Neon starts the transfer and rotates `DATABASE_URL`. Existing access tokens are revoked. Auth and the Data API stay enabled when they were granted.
|
|
45
45
|
|
|
46
|
-
|
|
46
|
+
A claim code expires in `expires_in` seconds (15 minutes / 900 today). If the unused code expires, mint another: `neon claim accept --no-open` or `POST /v1/projects/{id}/claim`. Each mint cancels the previous unused code. You can mint several times; only the latest unused code works. Re-issue only while `project_expires_at` is still in the future.
|
|
47
|
+
|
|
48
|
+
Continuing to Neon starts a transfer with a new 15-minute window and leaves the project key and database password revoked. If that window expires before the human accepts, mint again. Do not restore pre-claim `DATABASE_URL`.
|
|
49
|
+
|
|
50
|
+
When `reconciled` is true, the pre-claim `DATABASE_URL` no longer works. Auth and Data API URLs stay if they were granted. The human signs in with `neon auth`. Then the agent runs `neon link` and `neon env pull` to write the new `DATABASE_URL`. `neon link` discovers the project after that sign-in.
|
|
51
|
+
|
|
52
|
+
Auth and the Data API stay off unless requested at create or enabled later. On the unclaimed project, `neon.ts` plus `neon deploy` enables them. After claim, the same config talks to Neon directly. An external JWKS is only accepted after claim. Data API with the default auth provider requires Auth:
|
|
53
|
+
|
|
54
|
+
```typescript
|
|
55
|
+
import { defineConfig } from "@neon/config/v1";
|
|
56
|
+
|
|
57
|
+
export default defineConfig({
|
|
58
|
+
auth: true,
|
|
59
|
+
dataApi: true,
|
|
60
|
+
});
|
|
61
|
+
```
|
|
62
|
+
|
|
63
|
+
```bash
|
|
64
|
+
neon deploy
|
|
65
|
+
```
|
|
66
|
+
|
|
67
|
+
```typescript
|
|
68
|
+
export default defineConfig({
|
|
69
|
+
dataApi: {
|
|
70
|
+
authProvider: "external",
|
|
71
|
+
jwksUrl: "https://example.com/.well-known/jwks.json",
|
|
72
|
+
},
|
|
73
|
+
});
|
|
74
|
+
```
|
|
75
|
+
|
|
76
|
+
`neon checkout` does not apply this to an existing branch. `neon deploy` (alias of `neon config apply`) does.
|
|
47
77
|
|
|
48
78
|
### With the CLI
|
|
49
79
|
|
|
@@ -62,9 +92,9 @@ neon claim delete --yes
|
|
|
62
92
|
|
|
63
93
|
### With REST
|
|
64
94
|
|
|
65
|
-
An agent must not complete the claim. Do not `POST /v1/projects/{id}/claim` until the human is ready. The human opens `verification_uri_complete` and accepts the transfer. If the claim code expires, `POST /v1/projects/{id}/claim` again. The live claim response also includes `user_code` and `expires_in`. `auth.md` documents `verification_uri_complete` and the polling `interval`.
|
|
95
|
+
An agent must not complete the claim. Do not `POST /v1/projects/{id}/claim` until the human is ready. The human opens `verification_uri_complete` and accepts the transfer. If the claim code expires, `POST /v1/projects/{id}/claim` again. Each POST replaces the unused previous code. If the human continued to Neon and that transfer expired, POST again for a new code. The live claim response also includes `user_code` and `expires_in`. `auth.md` documents `verification_uri_complete` and the polling `interval`.
|
|
66
96
|
|
|
67
|
-
After the human continues to Neon, existing access tokens are revoked: re-exchange the identity assertion, then poll `GET /v1/projects/{id}/claim` with that token at the interval `auth.md` returns. `claim_in_progress`
|
|
97
|
+
After the human continues to Neon, existing access tokens are revoked: re-exchange the identity assertion, then poll `GET /v1/projects/{id}/claim` with that token at the interval `auth.md` returns. `claim_in_progress` on a new mint means the transfer window is still live: poll, do not mint. After that window expires, POST claim again. Report `verification_uri_complete`, `user_code`, and `expires_in`.
|
|
68
98
|
|
|
69
99
|
When `error.code` is `capability_requires_claim`, preserve the denied capability and give the human a claim link instead of retrying or silently omitting it.
|
|
70
100
|
|
|
@@ -14,7 +14,7 @@ description: >-
|
|
|
14
14
|
|
|
15
15
|
---
|
|
16
16
|
|
|
17
|
-
Latest Stripe API version: **2026-
|
|
17
|
+
Latest Stripe API version: **2026-08-26.dahlia**. Always use the latest API version and SDK unless the user specifies otherwise.
|
|
18
18
|
|
|
19
19
|
Latest SDK versions:
|
|
20
20
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "vybekiit",
|
|
3
|
-
"version": "0.7.
|
|
3
|
+
"version": "0.7.23",
|
|
4
4
|
"description": "Choose your services, sign in, create a VybeKiit app, and open its verified local welcome page.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"publishConfig": {
|
|
@@ -32,13 +32,13 @@
|
|
|
32
32
|
"tsup": "8.5.1",
|
|
33
33
|
"typescript": "5.7.2",
|
|
34
34
|
"vitest": "3.2.6",
|
|
35
|
-
"@vybekiit/
|
|
36
|
-
"@vybekiit/
|
|
37
|
-
"@vybekiit/agent-mcp": "0.7.
|
|
38
|
-
"@vybekiit/
|
|
39
|
-
"@vybekiit/
|
|
40
|
-
"@vybekiit/
|
|
41
|
-
"@vybekiit/payments": "0.7.
|
|
35
|
+
"@vybekiit/agent-kit": "0.7.23",
|
|
36
|
+
"@vybekiit/core": "0.7.23",
|
|
37
|
+
"@vybekiit/agent-mcp": "0.7.23",
|
|
38
|
+
"@vybekiit/db": "0.7.23",
|
|
39
|
+
"@vybekiit/report-mode": "0.7.23",
|
|
40
|
+
"@vybekiit/deploy": "0.7.23",
|
|
41
|
+
"@vybekiit/payments": "0.7.23"
|
|
42
42
|
},
|
|
43
43
|
"scripts": {
|
|
44
44
|
"build": "tsup && node scripts/bundleGlobalSkills.mjs",
|