neon 3.2.1 → 3.2.2

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.
package/README.md CHANGED
@@ -673,7 +673,7 @@ $ neon init
673
673
 
674
674
  Run in a terminal it prompts you through those steps. This is what the retired `neon-init` package used to do; `npx neon init` replaces it.
675
675
 
676
- Two side effects worth knowing before you run it. It **installs or upgrades `neonctl` globally**, with whichever package manager invoked it — the flow drives Neon by shelling out to the CLI rather than calling the API in-process. And it **writes `.neon`** in the project directory, the same context file `neon link` and `neon checkout` use.
676
+ Two side effects worth knowing before you run it. It **installs or upgrades `neon` globally**, with whichever package manager invoked it — the flow drives Neon by shelling out to the CLI rather than calling the API in-process. And it **writes `.neon`** in the project directory, the same context file `neon link` and `neon checkout` use.
677
677
 
678
678
  ### Agent mode
679
679
 
@@ -111,7 +111,7 @@ async function buildBulkInspection(options) {
111
111
  ].join("\n"),
112
112
  checks: [
113
113
  {
114
- id: "neonctl",
114
+ id: "neon",
115
115
  description: "The Neon CLI will be installed or updated automatically (no action needed from the agent)",
116
116
  lookFor: []
117
117
  },
@@ -294,27 +294,27 @@ async function executeBatchedInstallation(options) {
294
294
  switch (neonctlResult.status) {
295
295
  case "already_current":
296
296
  results.push({
297
- id: "neonctl",
297
+ id: "neon",
298
298
  description: `Neon CLI is up to date (v${neonctlResult.version})`,
299
299
  status: "success"
300
300
  });
301
301
  break;
302
302
  case "installed":
303
303
  results.push({
304
- id: "neonctl",
304
+ id: "neon",
305
305
  description: `Installed Neon CLI (v${neonctlResult.version})`,
306
306
  status: "success"
307
307
  });
308
308
  break;
309
309
  case "updated":
310
310
  results.push({
311
- id: "neonctl",
311
+ id: "neon",
312
312
  description: `Updated Neon CLI to v${neonctlResult.version}`,
313
313
  status: "success"
314
314
  });
315
315
  break;
316
316
  case "failed": results.push({
317
- id: "neonctl",
317
+ id: "neon",
318
318
  description: "Failed to install Neon CLI",
319
319
  status: "failed",
320
320
  error: neonctlResult.error
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "neon",
3
- "version": "3.2.1",
3
+ "version": "3.2.2",
4
4
  "description": "CLI tool for Neon, the cloud backend primitives built around Lakebase Postgres",
5
5
  "keywords": [
6
6
  "neon",
@@ -63,9 +63,9 @@
63
63
  "yaml": "^2.9.0",
64
64
  "yargs": "17.7.2",
65
65
  "yoctocolors": "^2.1.2",
66
+ "@neon/sdk": "2.0.0",
66
67
  "@neon/config": "1.0.0",
67
- "@neon/config-runtime": "1.0.0",
68
- "@neon/sdk": "2.0.0"
68
+ "@neon/config-runtime": "1.0.0"
69
69
  },
70
70
  "optionalDependencies": {
71
71
  "esbuild": "0.28.1"
@@ -97,8 +97,8 @@
97
97
  "typescript": "^5.9.0",
98
98
  "vitest": "^3.0.9",
99
99
  "@neon-internals/cli-core": "0.0.0",
100
- "@neon-internals/env-core": "0.0.0",
101
- "@neon/e2e-harness": "0.0.0"
100
+ "@neon/e2e-harness": "0.0.0",
101
+ "@neon-internals/env-core": "0.0.0"
102
102
  },
103
103
  "publishConfig": {
104
104
  "access": "public",