unoverse 0.1.78 → 0.1.79

package/bin/unoverse.mjs

@@ -114,7 +114,12 @@ switch (cmd) {
       console.log(`\n  ✓ unoverse is now ${v || "up to date"}`);
       spawnSync("unoverse", ["_postupdate"], { stdio: "inherit" });
     } else {
-      console.log(`\n  ✗ global install failed (permissions?). Try:\n\n    sudo npm install -g unoverse@latest\n    npx unoverse@latest    # or skip the global install entirely\n`);
+      // DO NOT GUESS THE CAUSE. This used to say "(permissions?)" whatever happened, so a
+      // registry that had not finished propagating a release — npm resolves `latest` to a
+      // version whose tarball is not servable yet, ETARGET — was reported as a permissions
+      // problem, sending people to sudo for something sudo cannot fix. npm's own error is
+      // already on screen above; name the two real causes and let it speak for itself.
+      console.log(`\n  ✗ Update failed. npm's reason is above.\n\n    "No matching version" — a release is still propagating. Wait a minute and re-run.\n    "EACCES" / permission denied — sudo npm install -g unoverse@latest\n\n  Or skip the global install entirely: npx unoverse@latest\n`);
     }
     process.exit(r.status ?? 0);
   }

package/operator/infra/digitalocean/main.tf

@@ -246,6 +246,21 @@ resource "digitalocean_database_user" "universe" {
   count      = local.pg_managed ? 1 : 0
   cluster_id = local.pg_cluster_id
   name       = "universe"
+
+  # NEVER UPDATE THIS USER IN PLACE. Provider 2.96 grew a `settings` block (Kafka and
+  # OpenSearch ACLs) and an update path that fires whenever it sees any diff on the
+  # resource — including one the provider invented itself on refresh. For a Postgres user,
+  # which has no settings, that path PUTs an empty body and DigitalOcean rejects it:
+  #
+  #   400 request is missing the following required fields: user_settings
+  #
+  # It killed a deploy mid-apply, after the firewall had already changed, on a resource
+  # declaring nothing but a name. We create this user once and never modify it — name and
+  # cluster_id both force replacement anyway — so there is no update we want, and the
+  # safest number of update paths to leave available is zero.
+  lifecycle {
+    ignore_changes = all
+  }
 }
 
 # Transaction-mode pool: ~hundreds of client connections over `pgbouncer` backend

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "unoverse",
-  "version": "0.1.78",
+  "version": "0.1.79",
   "description": "The Unoverse front door — create a Studio project, a universe, or a client app, and launch Studio.",
   "license": "SEE LICENSE IN README.md",
   "type": "module",