background-agents 1.0.0 → 1.0.5

package/README.md

@@ -8,14 +8,14 @@ npx background-agents@latest
 
 That's it. The first run downloads the Electron runtime (~once, then cached); every run loads the production app at <https://backgrounder.dev>.
 
-> **Naming:** the TypeScript SDK previously published as `background-agents` now lives at [`@background-agents/sdk`](../agents), which freed the `background-agents` name for this desktop launcher.
+> **Naming:** the TypeScript SDK previously published as `background-agents` now lives at [`@background-agents/sdk`](../sdk), which freed the `background-agents` name for this desktop launcher.
 
 ## How it works
 
 This is a thin launcher published to npm as [`background-agents`](https://www.npmjs.com/package/background-agents):
 
 1. `npx background-agents@latest` resolves the **latest published version** of this package from the npm registry.
-2. npm installs it and its one dependency, **Electron**, downloading the platform binary on first run (cached for later runs).
+2. npm installs it and its dependencies — **Electron** (plus `electron-updater` and `isomorphic-git`) — downloading the Electron platform binary on first run (cached for later runs).
 3. The launcher spawns the bundled Electron app (`app/`) pointed at the production backend, showing a small terminal UI while it starts.
 
 Because every launch pulls the latest npm version, **publishing a new version is the update mechanism** — there's no separate auto-updater to configure or code-sign.
@@ -46,7 +46,7 @@ Environment variable `BACKGROUND_AGENTS_URL` does the same as `--url` (the flag
 
 ## Development
 
-This package lives in the monorepo at `packages/launcher`. Its `app/` directory is generated — it's a copy of the compiled `@background-agents/electron` output.
+This package lives in the monorepo at `packages/launcher`. Its `app/` directory is generated — it's a copy of the compiled `@background-agents/desktop` output.
 
 ```bash
 # From the repo root:
@@ -71,7 +71,7 @@ Pushing a `v*` tag runs the publish workflow, which sets the package version fro
 git tag v1.0.1 && git push origin v1.0.1
 ```
 
-> The workflow ships as `.github/npm-publish-workflow.yml` (outside `.github/workflows/`, mirroring `release-workflow.yml`, because pushing into `.github/workflows/` needs the GitHub `workflow` OAuth scope). **Move it into `.github/workflows/` to activate it.** Note the same `v*` tag also triggers `release-workflow.yml` (the Electron installers), so the desktop installers and the npm launcher publish together.
+> The workflow lives at `.github/workflows/npm-publish.yml` and is active. The Electron desktop installers are built by a separate workflow, `release-workflow.yml`, which currently sits at `.github/release-workflow.yml` — **outside** `.github/workflows/` — so it does **not** run on a tag push until it's moved into `.github/workflows/` (see the [desktop README](../desktop/README.md#automated-releases-github-actions)). Once moved, the same `v*` tag publishes the desktop installers and the npm launcher together.
 
 ### Manual
 

package/app/package.json

@@ -0,0 +1,6 @@
+{
+  "name": "background-agents-app",
+  "version": "0.0.0",
+  "private": true,
+  "type": "module"
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "background-agents",
-  "version": "1.0.0",
+  "version": "1.0.5",
   "description": "Launch the Background Agents desktop app with one command — npx background-agents. Always runs the latest published version.",
   "type": "commonjs",
   "bin": {
@@ -22,7 +22,9 @@
     "typecheck": "node --check bin/background-agents.js && node --check lib/ui.js"
   },
   "dependencies": {
-    "electron": "^33.2.1"
+    "electron": "^33.2.1",
+    "electron-updater": "^6.3.9",
+    "isomorphic-git": "^1.38.3"
   },
   "keywords": [
     "background-agents",