@specific.dev/cli 0.1.68 → 0.1.69

package/dist/cli.js

@@ -184496,7 +184496,7 @@ function trackEvent(event, properties) {
     event,
     properties: {
       ...properties,
-      cli_version: "0.1.68",
+      cli_version: "0.1.69",
       platform: process.platform,
       node_version: process.version,
       project_id: getProjectId(),
@@ -194601,8 +194601,8 @@ function compareVersions(a, b) {
   return 0;
 }
 async function checkForUpdate() {
-  const currentVersion = "0.1.68";
-  const response = await fetch(`${BINARIES_BASE_URL}/latest`);
+  const currentVersion = "0.1.69";
+  const response = await fetch(`${BINARIES_BASE_URL}/latest?t=${Date.now()}`);
   if (!response.ok) {
     throw new Error(`Failed to check for updates: HTTP ${response.status}`);
   }
@@ -194739,7 +194739,8 @@ function UpdateUI() {
         if (cancelled) return;
         trackEvent("cli_updated", {
           from_version: state.checkResult.currentVersion,
-          to_version: state.checkResult.latestVersion
+          to_version: state.checkResult.latestVersion,
+          source: "manual"
         });
         writeCheckTimestamp();
         setState((s) => ({ ...s, phase: "success" }));
@@ -194799,7 +194800,7 @@ function updateCommand() {
 var program = new Command();
 var env = "production";
 var envLabel = env !== "production" ? `[${env.toUpperCase()}] ` : "";
-program.name("specific").description(`${envLabel}Infrastructure-as-code for coding agents`).version("0.1.68").enablePositionalOptions();
+program.name("specific").description(`${envLabel}Infrastructure-as-code for coding agents`).version("0.1.69").enablePositionalOptions();
 program.command("init").description("Initialize project for use with a coding agent").option("--agent <name...>", "Agents to configure (cursor, claude, codex, other)").action((options2) => initCommand(options2));
 program.command("docs [topic]").description("Fetch LLM-optimized documentation").action(docsCommand);
 program.command("check").description("Validate specific.hcl configuration").action(checkCommand);

package/dist/docs/index.md

@@ -35,6 +35,7 @@ A full development environment can be started with `specific dev`. To deploy any
 
 The following is a list of common frameworks and libraries with guidance on how to use them with Specific:
 
+- [Python](/integrations/python): Flask, FastAPI, Django, and other Python frameworks
 - [Next.js](/integrations/nextjs): full-stack React framework
 - [Drizzle ORM](/integrations/drizzle): TypeScript ORM with type safety
 - [Prisma](/integrations/prisma): TypeScript ORM with auto-generated client

package/dist/docs/integrations/python.md

@@ -0,0 +1,220 @@
+# Python
+
+Python is supported out of the box with Specific. This guide covers running Python services with virtual environments, module resolution, and common frameworks.
+
+## Basic configuration
+
+Use `base = "python"` for builds. For development, point the dev command at your virtual environment's Python binary:
+
+```hcl
+build "api" {
+  base = "python"
+}
+
+service "api" {
+  build = build.api
+  command = "python app.py"
+
+  endpoint {
+    public = true
+  }
+
+  env = {
+    PORT = port
+    DATABASE_URL = postgres.main.url
+  }
+
+  dev {
+    command = ".venv/bin/python app.py"
+  }
+}
+
+postgres "main" {}
+```
+
+In production, `base = "python"` handles dependency installation automatically (see [Builds](/builds) for details). In development, you manage your own virtual environment.
+
+## Virtual environments
+
+Create a virtual environment in your project before running `specific dev`:
+
+```sh
+python3 -m venv .venv
+.venv/bin/pip install -r requirements.txt
+```
+
+Or with `uv`:
+
+```sh
+uv venv .venv
+uv pip install -r requirements.txt
+```
+
+There are two ways to reference the venv in your dev command:
+
+**Direct path (recommended):**
+
+```hcl
+dev {
+  command = ".venv/bin/python app.py"
+}
+```
+
+**Shell activation:**
+
+```hcl
+dev {
+  command = "source .venv/bin/activate && python app.py"
+}
+```
+
+Both work because service commands run in a shell. The direct path is simpler and avoids potential issues with shell activation scripts.
+
+## Module resolution
+
+Python module imports work naturally because `specific dev` sets the working directory to the service's `root` (or the project root if no `root` is set). Standard imports resolve as expected:
+
+```
+myproject/
+  specific.hcl
+  app.py
+  myapp/
+    __init__.py
+    utils.py
+```
+
+```python
+# app.py
+from myapp.utils import get_greeting  # works
+```
+
+You can also use `python -m` to run modules:
+
+```hcl
+dev {
+  command = ".venv/bin/python -m myapp"
+}
+```
+
+## Monorepo support
+
+For monorepos, use `root` to set the working directory. The venv path is relative to `root`:
+
+```hcl
+build "api" {
+  base = "python"
+  root = "backend"
+}
+
+service "api" {
+  build = build.api
+  command = "python app.py"
+
+  endpoint {
+    public = true
+  }
+
+  env = {
+    PORT = port
+  }
+
+  dev {
+    command = ".venv/bin/python app.py"
+  }
+}
+```
+
+Here `.venv/bin/python` resolves to `backend/.venv/bin/python`.
+
+## Common frameworks
+
+### Flask
+
+```hcl
+build "api" {
+  base = "python"
+}
+
+service "api" {
+  build = build.api
+  command = "flask run --host 0.0.0.0 --port $PORT"
+
+  endpoint {
+    public = true
+  }
+
+  env = {
+    PORT = port
+    FLASK_APP = "app"
+  }
+
+  dev {
+    command = ".venv/bin/flask run --host 0.0.0.0 --port $PORT --reload"
+  }
+}
+```
+
+### FastAPI with uvicorn
+
+```hcl
+build "api" {
+  base = "python"
+}
+
+service "api" {
+  build = build.api
+  command = "uvicorn app:app --host 0.0.0.0 --port $PORT"
+
+  endpoint {
+    public = true
+  }
+
+  env = {
+    PORT = port
+  }
+
+  dev {
+    command = ".venv/bin/uvicorn app:app --host 0.0.0.0 --port $PORT --reload"
+  }
+}
+```
+
+### Django
+
+```hcl
+build "web" {
+  base = "python"
+}
+
+service "web" {
+  build = build.web
+  command = "gunicorn myproject.wsgi --bind 0.0.0.0:$PORT"
+
+  endpoint {
+    public = true
+  }
+
+  env = {
+    PORT = port
+    DATABASE_URL = postgres.main.url
+  }
+
+  pre_deploy {
+    command = "python manage.py migrate"
+  }
+
+  dev {
+    command = ".venv/bin/python manage.py runserver 0.0.0.0:$PORT"
+  }
+}
+
+postgres "main" {}
+```
+
+## Database migrations
+
+Use `pre_deploy` hooks for production migrations and `specific exec` for development:
+
+```sh
+specific exec api -- .venv/bin/python manage.py migrate
+```

package/dist/postinstall.js

@@ -111,7 +111,7 @@ function trackEvent(event, properties) {
     event,
     properties: {
       ...properties,
-      cli_version: "0.1.68",
+      cli_version: "0.1.69",
       platform: process.platform,
       node_version: process.version,
       project_id: getProjectId(),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@specific.dev/cli",
-  "version": "0.1.68",
+  "version": "0.1.69",
   "description": "CLI for Specific infrastructure-as-code",
   "type": "module",
   "main": "dist/cli.js",