@yagni-app/code-staging 1.0.8-staging.1275.1 → 1.0.8-staging.1280.1

package/dist/upgrade.js

@@ -249,13 +249,22 @@ export function parseUpgradeArgs(args) {
     }
     return { ok: true, target, method };
 }
+// npm's informational channels (deprecation warnings, the funding notice,
+// and npm ≥11.13's `allowScripts` notice) are noise under an upgrade the user
+// explicitly asked for; errors and the added-packages summary stay visible.
+// Note the allowScripts notice is advisory only: with the default (non-strict)
+// policy npm still runs the listed scripts, so quieting it changes nothing
+// functionally. Audit findings go to stdout, unaffected by --loglevel.
+const NPM_QUIET_FLAGS = ["--loglevel=error", "--no-fund", "--no-audit"];
 function installArgv(method, target) {
     // brew upgrades to whatever the tap formula publishes; it cannot pin a
     // version, so `target` only tells us an upgrade is worthwhile.
     if (method === "brew")
         return ["upgrade", BREW_FORMULA];
     const spec = `${PACKAGE_NAME}@${target}`;
-    return method === "npm" ? ["install", "-g", spec] : ["add", "-g", spec];
+    return method === "npm"
+        ? ["install", "-g", ...NPM_QUIET_FLAGS, spec]
+        : ["add", "-g", spec];
 }
 function failureHint(method) {
     if (method === "brew") {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yagni-app/code-staging",
-  "version": "1.0.8-staging.1275.1",
+  "version": "1.0.8-staging.1280.1",
   "description": "YAGNI Code: a terminal coding agent that already knows your company. One YAGNI login routes the model and grounds the agent in your team's context.",
   "license": "SEE LICENSE IN LICENSE.md",
   "author": "YAGNI, Inc. <jack@yagni.app> (https://yagni.app)",
@@ -58,5 +58,5 @@
     "turndown": "^7.2.4",
     "typebox": "^1.3.15"
   },
-  "yagniSourceSha": "c49131c2a11910eedfa3b14012735b1e593769df"
+  "yagniSourceSha": "9b213ea65690a4544d0cdf093b6903aab8a1456b"
 }