@elitedcs/ghl-mcp 3.34.10 → 3.36.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/CHANGELOG.md +22 -0
  2. package/dist/index.js +1556 -26
  3. package/package.json +1 -1
package/CHANGELOG.md CHANGED
@@ -1,5 +1,27 @@
1
1
  # Changelog
2
2
 
3
+ ## 3.35.0 — `create_social_post` is now draft-first (closes the silent "everything published at once" trap)
4
+
5
+ **Behavior change.** `create_social_post` no longer defers go-live to GoHighLevel's
6
+ server-side default. Before, when `status` was omitted the field was dropped from the
7
+ request and GHL decided whether the post went live — an undocumented default that, in
8
+ a loop, is exactly the "all posts fired at once, no error, no warning" failure operators
9
+ hit. The most expensive failures are the silent ones, so the tool now takes a defensive
10
+ stance by default.
11
+
12
+ - **Draft-first default.** Omit `status` and the post is created as a `draft` (editable,
13
+ never live). Going live is now an explicit choice (`status:"published"`).
14
+ - **Scheduling is coupled to status.** Pass `scheduledAt` with no `status` and it
15
+ auto-resolves to `"scheduled"`. Pass `scheduledAt` alongside any *other* status, or
16
+ `status:"scheduled"` with no `scheduledAt`, and the call is rejected with an actionable
17
+ error instead of silently publishing now or falling back to the server default. This
18
+ kills the "I thought it was scheduled" class of failure (CHANGELOG 3.18.0 always
19
+ required both fields; nothing enforced the pairing until now).
20
+ - Logic extracted to the pure, tested `resolvePostStatus(status, scheduledAt)` helper;
21
+ tool and field descriptions updated to document the contract. 5 regression tests added.
22
+ - **Migration:** any caller that relied on an un-statused post going live must now pass
23
+ `status:"published"` explicitly. No other tool is affected.
24
+
3
25
  ## 3.34.10 — `get_free_slots` accepts ISO dates; `update_form` name fallback for fresh forms
4
26
 
5
27
  Two small fixes that close rough edges found while live-verifying v3.34.9 through