@rebasepro/cli 0.15.0 → 0.16.0

package/dist/utils/libpq-url.d.ts

@@ -0,0 +1,69 @@
+/**
+ * Detect Postgres connection strings that libpq refuses to parse.
+ *
+ * libpq splits a URI query parameter on the FIRST `=` and rejects any further
+ * one in the same parameter:
+ *
+ *   extra key/value separator "=" in URI query parameter: "options"
+ *
+ * That makes a URL like
+ *
+ *   postgresql://u:p@h:5432/db?options=-c%20search_path=public&sslmode=disable
+ *
+ * unusable by every libpq caller — `pg_dump`/`pg_restore` behind
+ * `rebase db backup|restore`, and a plain `psql "$DATABASE_URL"`. It is not a
+ * version quirk: Postgres 15 through 18 all refuse it.
+ *
+ * `rebase init` generated exactly that string until 2026-08-18, and the failure
+ * is invisible day to day because node-postgres parses URLs itself and accepts
+ * it — so `rebase dev` and `rebase db push` work while backups do not. Fixing
+ * the generator does nothing for projects that already exist, which is what
+ * these functions are for: `rebase doctor` reads them off disk and reports.
+ */
+/** A query parameter whose value carries a literal `=`. */
+export interface UnparseableParam {
+    /** The parameter name, e.g. "options". */
+    name: string;
+    /** The raw `name=value` text as it appears in the URL. */
+    raw: string;
+}
+/**
+ * Return the query parameters libpq would reject, or an empty array.
+ *
+ * Deliberately not built on `new URL()`: that parser is happy to accept the
+ * broken form (it splits on the first `=` and keeps the rest as the value),
+ * so it cannot see the defect at all. The rule being checked is libpq's, and
+ * it is about the raw text.
+ */
+export declare function findUnparseableParams(connectionString: string): UnparseableParam[];
+/**
+ * Percent-encode the offending `=` characters, leaving everything else byte for
+ * byte as it was.
+ *
+ * Only the second and later `=` in a parameter are rewritten — the first is the
+ * real separator. Nothing else is touched: re-serialising through `URL` would
+ * also reorder parameters and turn spaces into `+`, which libpq does not decode,
+ * so a "tidy up" would trade one unparseable string for another.
+ */
+export declare function encodeExtraEquals(connectionString: string): string;
+/** One connection string, found somewhere on disk, that libpq cannot parse. */
+export interface LibpqUrlFinding {
+    /** File it came from, relative to the project root. */
+    file: string;
+    /** The variable holding it, e.g. "DATABASE_URL". */
+    variable: string;
+    /** Parameter names libpq objects to. */
+    params: string[];
+    /** The same string with the offending `=` encoded. */
+    suggested: string;
+}
+/**
+ * Scan one file's text for connection strings libpq would reject.
+ *
+ * Handles both shapes a scaffolded project uses, because both shipped with the
+ * defect and a deployed stack is broken by the compose one alone:
+ *
+ *   .env               DATABASE_URL=postgresql://…
+ *   docker-compose.yml   DATABASE_URL: postgresql://…
+ */
+export declare function scanTextForLibpqUrls(file: string, text: string): LibpqUrlFinding[];

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rebasepro/cli",
-  "version": "0.15.0",
+  "version": "0.16.0",
   "description": "Developer tools for Rebase projects",
   "main": "./dist/index.es.js",
   "module": "./dist/index.es.js",
@@ -31,12 +31,12 @@
     "execa": "^9.6.1",
     "inquirer": "14.0.2",
     "jiti": "^2.7.0",
-    "@rebasepro/agent-skills": "0.15.0",
-    "@rebasepro/client": "0.15.0",
-    "@rebasepro/server": "0.15.0",
-    "@rebasepro/server-postgres": "0.15.0",
-    "@rebasepro/codegen": "0.15.0",
-    "@rebasepro/types": "0.15.0"
+    "@rebasepro/agent-skills": "0.16.0",
+    "@rebasepro/client": "0.16.0",
+    "@rebasepro/codegen": "0.16.0",
+    "@rebasepro/server": "0.16.0",
+    "@rebasepro/server-postgres": "0.16.0",
+    "@rebasepro/types": "0.16.0"
   },
   "devDependencies": {
     "@types/node": "^26.1.2",

package/templates/eject/docker-compose.custom.yml

@@ -48,8 +48,8 @@ services:
       - "${PORT:-3001}:3001"
     env_file: .env
     environment:
-      DATABASE_URL: postgresql://rebase_app:${DATABASE_PASSWORD:-changeme}@db:5432/rebase?options=-c%20search_path=public
-      ADMIN_CONNECTION_STRING: postgresql://rebase_app:${DATABASE_PASSWORD:-changeme}@db:5432/rebase?options=-c%20search_path=public
+      DATABASE_URL: postgresql://rebase_app:${DATABASE_PASSWORD:-changeme}@db:5432/rebase?options=-c%20search_path%3Dpublic
+      ADMIN_CONNECTION_STRING: postgresql://rebase_app:${DATABASE_PASSWORD:-changeme}@db:5432/rebase?options=-c%20search_path%3Dpublic
       NODE_ENV: production
       PORT: "3001"
       # {{#frontend}}

package/templates/overlays/baas/README.md

@@ -16,10 +16,10 @@ table is never exposed just by existing — and logs each table it skipped and w
 ```sql
 ALTER TABLE your_table ENABLE ROW LEVEL SECURITY;
 CREATE POLICY your_table_owner ON your_table
-    FOR ALL USING (user_id = auth.uid());
+    FOR ALL USING (user_id = rebase.uid());
 ```
 
-`auth.uid()`, `auth.roles()` and `auth.jwt()` are provided by Rebase and read the
+`rebase.uid()`, `rebase.roles()` and `rebase.jwt()` are provided by Rebase and read the
 identity of the authenticated request.
 
 To serve unprotected tables anyway (development only), set

package/templates/template/.env.example

@@ -10,7 +10,7 @@
 # sslmode=disable matches the local docker-compose database, which has no TLS;
 # schema tooling (atlas) would otherwise default to requiring SSL. Remove it
 # when pointing at a managed/cloud database.
-DATABASE_URL=postgresql://rebase_app:changeme@localhost:5432/rebase?options=-c%20search_path=public&sslmode=disable
+DATABASE_URL=postgresql://rebase_app:changeme@localhost:5432/rebase?options=-c%20search_path%3Dpublic&sslmode=disable
 # DATABASE_URL=mongodb://localhost:27017/rebase
 #
 # Seeing "SSL is not enabled on the server"? Something in your environment
@@ -22,7 +22,7 @@ DATABASE_URL=postgresql://rebase_app:changeme@localhost:5432/rebase?options=-c%2
 # downgrade SSL for you when you have asked for it, not even on localhost:
 # quietly ignoring a security setting is worse than a clear failure. To opt out
 # explicitly for a local database, say so:
-#   DATABASE_URL=postgresql://rebase_app:changeme@localhost:5432/rebase?options=-c%20search_path=public&sslmode=disable
+#   DATABASE_URL=postgresql://rebase_app:changeme@localhost:5432/rebase?options=-c%20search_path%3Dpublic&sslmode=disable
 
 # Separate admin connection string for migrations and schema operations (optional)
 # Falls back to DATABASE_URL if not set
@@ -65,6 +65,9 @@ ALLOW_REGISTRATION=true
 # SMTP_FROM=noreply@yourapp.com
 # SMTP_NAME=
 # APP_NAME=Your App Name
+# Logo atop the default email templates. Absolute http(s) PNG/JPG only —
+# mail clients strip SVG and block data: URIs.
+# EMAIL_LOGO_URL=https://yourapp.com/logo.png
 
 # ── URLs ──────────────────────────────────────────────────────────────────────
 # Canonical frontend URL (used in password-reset / verification emails)

package/templates/template/docker-compose.yml

@@ -75,8 +75,8 @@ services:
     ports:
       - "${PORT:-3001}:3001"
     environment:
-      DATABASE_URL: postgresql://rebase_app:${DATABASE_PASSWORD:-changeme}@db:5432/rebase?options=-c%20search_path=public
-      ADMIN_CONNECTION_STRING: postgresql://rebase_app:${DATABASE_PASSWORD:-changeme}@db:5432/rebase?options=-c%20search_path=public
+      DATABASE_URL: postgresql://rebase_app:${DATABASE_PASSWORD:-changeme}@db:5432/rebase?options=-c%20search_path%3Dpublic
+      ADMIN_CONNECTION_STRING: postgresql://rebase_app:${DATABASE_PASSWORD:-changeme}@db:5432/rebase?options=-c%20search_path%3Dpublic
       JWT_SECRET: ${JWT_SECRET:?set JWT_SECRET in .env — `rebase init` generates one}
       REBASE_SERVICE_KEY: ${REBASE_SERVICE_KEY:?set REBASE_SERVICE_KEY in .env — `rebase init` generates one}
       NODE_ENV: production