@fargowealth/fargo-ai-cli 1.2.0 → 1.2.1

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.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,15 @@
1
1
  # Changelog
2
2
 
3
+ ## 1.2.1
4
+
5
+ - Clarified in `fargo lego deploy --help` that deployment preparation creates a
6
+ ready, unpublished deployment and that production publication is a separate
7
+ explicitly approved Fargo Pass MCP action.
8
+ - Documented the 4,000-character release-note limit and replaced full-changelog
9
+ examples with a concise per-release notes file.
10
+ - Documented that publication normally inherits the security-checked access
11
+ policy stored on the prepared deployment.
12
+
3
13
  ## 1.2.0
4
14
 
5
15
  - Added `--login-required yes|no` to select the target company-account sign-in
package/README.md CHANGED
@@ -78,7 +78,7 @@ fargo lego deploy \
78
78
  --entrypoint index.html \
79
79
  --version 1.4.0 \
80
80
  --name "Navigation refresh" \
81
- --notes-file CHANGELOG.md
81
+ --notes-file RELEASE_NOTES.md
82
82
  ```
83
83
 
84
84
  For Workers use `--target worker`; the default entrypoint becomes `index.js`.
@@ -104,9 +104,15 @@ fargo lego deploy \
104
104
  --login-required yes \
105
105
  --version 1.4.0 \
106
106
  --name "Full-stack release" \
107
- --notes-file CHANGELOG.md
107
+ --notes-file RELEASE_NOTES.md
108
108
  ```
109
109
 
110
+ Release notes are limited to 4,000 characters by both the CLI and hosted
111
+ deployment service. Pass concise notes for one version with `--notes`, or keep
112
+ them in a per-release file such as `RELEASE_NOTES.md`. Do not pass an entire
113
+ multi-version changelog unless it is within the limit and intentionally belongs
114
+ to the new release.
115
+
110
116
  Use repeated `--assets-run-worker-first-route <glob>` options instead of the
111
117
  boolean flag when only selected routes should invoke the Worker first. The
112
118
  hosted LEGO publisher uploads the assets and attaches the binding; Cloudflare
@@ -146,6 +152,18 @@ MCP deployment contract. The result is `ready`, never automatically published.
146
152
  Use `--dry-run` to validate both local packages without authentication or
147
153
  network writes.
148
154
 
155
+ After reviewing the returned deployment and receiving explicit approval,
156
+ publish that exact deployment through Fargo Pass MCP:
157
+
158
+ ```sh
159
+ fargo mcp call lego_deployment_release --args \
160
+ '{"action":"publish","appId":"app_xxx","deploymentId":"dep_xxx"}'
161
+ ```
162
+
163
+ Publication is a separate production write. The prepared deployment already
164
+ contains its security-checked access policy, so callers normally do not need to
165
+ repeat `visibility`, `loginRequired`, or `accessTargets` at publish time.
166
+
149
167
  Deployment artifacts preserve binary bytes and include
150
168
  `.fargo-deploy/manifest.json`. Default limits are 1,000 files, 25 MB total,
151
169
  20 MB per file, and a 25 MB ZIP.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@fargowealth/fargo-ai-cli",
3
- "version": "1.2.0",
3
+ "version": "1.2.1",
4
4
  "description": "Agent-neutral Fargo AI CLI, MCP client, and LEGO project tooling",
5
5
  "type": "module",
6
6
  "bin": {
package/src/cli.mjs CHANGED
@@ -157,7 +157,8 @@ Required:
157
157
  --target <pages|worker> Deployment target
158
158
  --version <version> Release version
159
159
  --name <name> Release name
160
- --notes <text> Release notes (or --notes-file <path>)
160
+ --notes <text> One release's notes, maximum 4000 characters
161
+ --notes-file <path> Read one release's notes from a file; same limit
161
162
 
162
163
  Source and execution:
163
164
  --source <directory> Source snapshot root (default: .)
@@ -188,13 +189,18 @@ Worker Runtime Topology:
188
189
  --queue-max-concurrency <n> Optional maximum concurrent consumers
189
190
  --queue-retry-delay <s> Optional retry delay in seconds
190
191
 
192
+ Result and publication:
193
+ This command creates a ready, unpublished deployment. Production traffic is
194
+ unchanged. After review and explicit approval, publish the returned deployment
195
+ with Fargo Pass MCP lego_deployment_release(action=publish).
196
+
191
197
  Example:
192
198
  fargo lego deploy --app app_xxx --source . \\
193
199
  --deploy-dir .build/worker --target worker --entrypoint index.js \\
194
200
  --assets-dir dist --assets-binding ASSETS \\
195
201
  --assets-not-found-handling single-page-application \\
196
202
  --assets-run-worker-first --version 1.4.0 --name "Full-stack release" \\
197
- --notes-file CHANGELOG.md
203
+ --notes-file RELEASE_NOTES.md
198
204
 
199
205
  .fargo-assets/ is an internal archive directory reserved for Fargo CLI.
200
206
  Do not create or copy it manually; always pass browser output with --assets-dir.
package/src/constants.mjs CHANGED
@@ -1,4 +1,4 @@
1
- export const CLI_VERSION = "1.2.0";
1
+ export const CLI_VERSION = "1.2.1";
2
2
  export const DEVICE_CODE_GRANT_TYPE = "urn:ietf:params:oauth:grant-type:device_code";
3
3
  export const DEFAULT_AUTH_URL = "https://auth.fargowealth.app";
4
4
  export const DEFAULT_API_URL = "https://mcp.fargowealth.app";