@malloy-publisher/create-malloy-package 0.0.59 → 0.0.61

package/README.md

@@ -311,7 +311,8 @@ All of that describes the script this tool writes. In a directory that already h
 runs whatever `start` was already there, binding wherever that command says. The same
 goes for everything else on this page that reads off a flag: `--port` and `--mcp_port`
 decide the URLs, `--server_root` and `--config` decide which workspace is served at
-all, and `--watch-env` decides whether an edit on disk is picked up without a reload.
+all, and `--watch-env` decides whether an edit on disk is picked up at all: without it
+the package is served as a published version, which a reload does not change.
 Read them out of the command you are about to run rather than off this page.
 
 Then read it off the server, which is the only ground truth. On boot it prints

package/dist/index.js

@@ -573,7 +573,7 @@ var MCP_PORT = 4040;
 var ALT_PUBLISHER_PORT = PUBLISHER_PORT + 100;
 var ALT_MCP_PORT = MCP_PORT + 100;
 var BIND_HOST = "127.0.0.1";
-var SERVER_VERSION = "0.12.5";
+var SERVER_VERSION = "0.13.0";
 function startCommandFor(envName) {
   return `npx -y @malloy-publisher/server@${SERVER_VERSION} --server_root . ` + `--config ./publisher.config.json --host ${BIND_HOST} ` + `--watch-env ${envName}`;
 }
@@ -690,7 +690,7 @@ function createPackage(options, result) {
   const dataDir = path2.join(packageDir, "data");
   assertWithinWorkspace(dataDir, options.cwd, `${name}/data`);
   fs3.mkdirSync(dataDir, { recursive: true });
-  writeFile(path2.join(packageDir, "publisher.json"), JSON.stringify({ name }, null, 2) + `
+  writeFile(path2.join(packageDir, "publisher.json"), JSON.stringify({ name, version: "0.1.0" }, null, 2) + `
 `, options.cwd);
   writeFile(path2.join(packageDir, "malloy-config.json"), JSON.stringify({
     connections: {
@@ -1360,7 +1360,9 @@ function workspaceGitignoreEntries() {
     "publisher.db*",
     "*.log",
     ".DS_Store",
-    "malloy-config.json"
+    "malloy-config.json",
+    ".env",
+    "*.env"
   ];
 }
 function workspaceGitignore() {

package/package.json

@@ -1,7 +1,7 @@
 {
    "name": "@malloy-publisher/create-malloy-package",
    "description": "Scaffold a Malloy Publisher package and a local agent workspace, so one command takes you from nothing to an agent that can query your data.",
-   "version": "0.0.59",
+   "version": "0.0.61",
    "license": "MIT",
    "type": "module",
    "engines": {
@@ -45,12 +45,12 @@
       "test:e2e": "bun test --timeout 180000 ./tests/e2e"
    },
    "dependencies": {
-      "@malloy-publisher/skills": "^0.1.51",
+      "@malloy-publisher/skills": "^0.1.53",
       "commander": "^12.1.0"
    },
    "devDependencies": {
       "@eslint/js": "^8.57.0",
-      "@malloydata/malloy": "^0.0.436",
+      "@malloydata/malloy": "^0.0.438",
       "@modelcontextprotocol/sdk": "^1.31.0",
       "@types/bun": "^1.2.21",
       "@types/node": "^24.10.0",
@@ -59,5 +59,5 @@
       "eslint": "^8.50.0",
       "typescript": "^5.3.3"
    },
-   "publisherServer": "0.12.5"
+   "publisherServer": "0.13.0"
 }

package/templates/AGENTS.md

@@ -28,7 +28,9 @@ Five flags decide whether the rest of this file is true:
 - `--port` and `--mcp_port` are absent from a command that uses the defaults above,
   which is the usual case. Where either one is present, it moves every URL here.
 - `--watch-env` is not a default, so watch mode is on only if you can see it. Without
-  it, an edit on disk is not picked up at all until you reload the package.
+  it, each package is published at boot as the immutable version its `publisher.json`
+  declares, and an edit on disk is never picked up, reload or not: to ship one, bump
+  that `version` and publish the package again.
 - `--server_root` and `--config` say which workspace is being served. Pointing either
   one outside this directory serves a different workspace entirely, and then nothing
   below describes what you are talking to.