@software-dlc/cli 0.166.2 → 0.167.0

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # @software-dlc/cli
 
+## 0.167.0
+
+## 0.166.3
+
+### Patch Changes
+
+- 4824934: Graph: `@software-dlc/cli` and `@software-dlc/graph` publish with public npm access, so anyone can install the `sdlc` command and the graph libraries with `npm install -g @software-dlc/cli`, with no npm login. Both READMEs and npm descriptions say SoftwareDLC is in Beta, and the cli README's quick start says to have Git ignore `sdlc/` and `.sdlc/` before `sdlc workspace init`.
+
 ## 0.166.2
 
 ### Patch Changes

package/README.md

@@ -1,10 +1,17 @@
 # @software-dlc/cli
 
+**Beta.** SoftwareDLC is in Beta: commands, stored formats and the graph
+schema can still change between versions.
+
 The `sdlc` command and the local MCP servers that read and change an SDLC
 graph of your code on your own machine. It needs no SoftwareDLC account: a
 graph lives in your repository's Git common directory, and nothing is written
 to your tracked files.
 
+`sdlc workspace init` refuses until Git ignores `sdlc/` and `.sdlc/`. List
+them in `.git/info/exclude` to leave your tracked files unchanged, then run it
+in the repository:
+
 ```bash
 npm install -g @software-dlc/cli
 sdlc workspace init
@@ -16,7 +23,7 @@ It ships three commands:
 | Command | What it does |
 | --- | --- |
 | `sdlc` | the local graph workflow: workspaces, commits, source evidence, packages, `sdlc viewer`, and the hosted sync when a project is connected |
-| `sdlc-worktree-mcp` | the MCP server the SoftwareDLC plugin starts in a repository you approved with `sdlc allow-mcp` |
+| `sdlc-worktree-mcp` | the MCP server the SoftwareDLC plugin starts: from the repository's own install, with its `.env.local`, once you approved the repository with `sdlc allow-mcp`, and otherwise from the install on your `PATH` |
 | `sdlc-graph-to-code-mcp` | the MCP server for a hosted project's Developer API |
 
 The graph libraries it uses are `@software-dlc/graph`, which it depends on at
@@ -24,8 +31,8 @@ an exact version.
 
 ## Changes and migrations
 
-The installed package carries its changelog and migration guides:
-`node_modules/@software-dlc/cli/CHANGELOG.md` and
-`node_modules/@software-dlc/cli/migrations/`, one `<version>.md` guide for
-each version that needs a migration. Each guide starts with a JSON header
-naming the features and stores it changes, then the steps.
+The installed package carries its changelog,
+`node_modules/@software-dlc/cli/CHANGELOG.md`. No version has needed a
+migration yet; when one does, the package gains a `migrations/` folder with
+one `<version>.md` guide for each such version. Each guide starts with a JSON
+header naming the features and stores it changes, then the steps.

package/package.json

@@ -1,11 +1,11 @@
 {
   "name": "@software-dlc/cli",
-  "version": "0.166.2",
-  "description": "The sdlc command and its local MCP servers: build, commit and read an SDLC graph of your code on your own machine.",
+  "version": "0.167.0",
+  "description": "(Beta) The sdlc command and its local MCP servers: build, commit and read an SDLC graph of your code on your own machine.",
   "type": "module",
   "license": "FSL-1.1-ALv2",
   "publishConfig": {
-    "access": "restricted",
+    "access": "public",
     "registry": "https://registry.npmjs.org/"
   },
   "files": [
@@ -74,7 +74,7 @@
     "sdlc-worktree-mcp": "./dist/mcp/stdio/worktree.js"
   },
   "dependencies": {
-    "@software-dlc/graph": "0.40.1",
+    "@software-dlc/graph": "0.40.2",
     "elkjs": "^0.10.0",
     "zod": "^4.3.6"
   }