@koda-sl/baker-cli 0.179.0 → 0.180.1

package/README.md

@@ -508,6 +508,10 @@ baker ads google campaigns create --customer-id 1234567890 --name "Brand — Sea
 # locations) or PRESENCE_OR_INTEREST (also people interested in them). Google applies
 # PRESENCE_OR_INTEREST when the flag is omitted, so pass PRESENCE for local/in-store/service-area
 # campaigns; --negative-geo-target-type does the same for excluded locations.
+# --networks search|search-partners|display|partner-search (comma-separated) sets which networks
+# the campaign serves on; every network not listed is turned OFF. A SEARCH campaign staged
+# without --networks publishes on Google Search only — Google's own default would add Search
+# partners and the Display network. Other channel types keep Google's behaviour.
 # Campaign URL options stage on create and update: --final-url-suffix (bare query params),
 # --tracking-template "https://tracker.example/?url={lpurl}" (must carry {lpurl}), and
 # --custom-param key=value (repeatable, up to 8; --clear-custom-params empties the set).
@@ -5018,6 +5022,7 @@ This CLI is designed for AI agent consumption. Key patterns:
 - **0.179.0**: `baker ads google keywords update --final-url` / `--clear-final-url` — changing where one keyword sends its clicks no longer costs the keyword its history. The write contract has always accepted `finalUrls` on a keyword update (`baker capabilities google-ads` reported it as a field of `google.keyword.update`), but no CLI flag reached it, so an agent that followed capabilities got "update needs at least one field" and the only route left was remove + re-add — a new criterion to Google, learning from zero, for a change that was only ever about the destination. `--clear-final-url` stages the empty set Google reads as "inherit the ad's landing page", which is the undo for the misuse `--final-url` already warns about. Same nudge as `add` on the way in.
 
   A keyword's final URL now also shows on its row when the keyword is being **removed**. 0.178.0 read it from the stage-time snapshot, but the snapshot never asked Google for it, so the removal half of that change silently did nothing — the card said which keyword was going away but not which landing page it had been sending its clicks to. The batch hint says outright that `--final-url` has no per-keyword form rather than implying destinations could differ within one call, and the tool doc now lists each `keywords` subcommand's own flags instead of one shared set (`--ad-group-ref`, `--text` and `--match-type` are `add`-only; `remove` takes a target and nothing else).
+- **0.180.1**: `baker tag-manager --help` said the container version Baker cuts at publish is **NOT** published, and told the agent to have the user publish it in Tag Manager. The executor publishes it — a clean run takes the client's container live — so the help understated an irreversible change to a production site. Corrected, and the stale `versionPendingMessage` helper (no callers, same wrong claim) removed from `@baker/api/tag-manager`. `draft list` already reported both outcomes correctly and is unchanged.
 
 ## Publishing
 

package/dist/{chunk-P2T3IZRE.js → chunk-QPVJGKV7.js}

@@ -7,9 +7,9 @@ import {
   __toESM
 } from "./chunk-YL3HDEIJ.js";
 
-// ../../node_modules/.pnpm/safe-stable-stringify@2.5.0/node_modules/safe-stable-stringify/index.js
+// ../../.pnpm-store/v10/links/@/safe-stable-stringify/2.5.0/810146e81bae4e3a061fe487864f2fde80c4b03b886877dc0f1fffbc6480b67e/node_modules/safe-stable-stringify/index.js
 var require_safe_stable_stringify = __commonJS({
-  "../../node_modules/.pnpm/safe-stable-stringify@2.5.0/node_modules/safe-stable-stringify/index.js"(exports, module) {
+  "../../.pnpm-store/v10/links/@/safe-stable-stringify/2.5.0/810146e81bae4e3a061fe487864f2fde80c4b03b886877dc0f1fffbc6480b67e/node_modules/safe-stable-stringify/index.js"(exports, module) {
     "use strict";
     var { hasOwnProperty } = Object.prototype;
     var stringify = configure2();
@@ -1075,7 +1075,7 @@ function resolveAdaptFormats(params) {
   return params.formats ?? [];
 }
 
-// ../../node_modules/.pnpm/safe-stable-stringify@2.5.0/node_modules/safe-stable-stringify/esm/wrapper.js
+// ../../.pnpm-store/v10/links/@/safe-stable-stringify/2.5.0/810146e81bae4e3a061fe487864f2fde80c4b03b886877dc0f1fffbc6480b67e/node_modules/safe-stable-stringify/esm/wrapper.js
 var import__ = __toESM(require_safe_stable_stringify(), 1);
 var configure = import__.default.configure;
 var wrapper_default = import__.default;
@@ -8028,4 +8028,4 @@ export {
   defaultRegistry,
   createEngineFromEnv
 };
-//# sourceMappingURL=chunk-P2T3IZRE.js.map
+//# sourceMappingURL=chunk-QPVJGKV7.js.map