@farthershore/cli 0.45.0 → 0.46.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.
- package/CHANGELOG.md +13 -1
- package/README.md +34 -4
- package/dist/index.js +604 -144
- package/package.json +3 -3
package/CHANGELOG.md
CHANGED
|
@@ -4,7 +4,19 @@ All notable changes to the `farthershore` CLI are documented here. The CLI
|
|
|
4
4
|
versions independently from the SDKs. Pre-1.0: minor versions may include
|
|
5
5
|
breaking changes. Releases before 0.35.0 are recorded only in the git history.
|
|
6
6
|
|
|
7
|
-
## [
|
|
7
|
+
## [0.46.0] - 2026-11-21
|
|
8
|
+
|
|
9
|
+
### Added
|
|
10
|
+
|
|
11
|
+
- `farthershore business release <business>`: release what is on the default branch of a live business. It picks major, minor or patch from what changed and cuts the release; `--dry-run` shows the plan, `--bump` / `--version X.Y.Z` override it, `--wait` follows it until it is live. In a terminal it asks before releasing and releases exactly the commit you confirmed.
|
|
12
|
+
- `farthershore business release-tag set <business> --prefix <prefix> | --clear`: choose the prefix of release tags (`v` by default).
|
|
13
|
+
|
|
14
|
+
### Changed
|
|
15
|
+
|
|
16
|
+
- `farthershore skills install` installs the Farther Shore skills bundle
|
|
17
|
+
v4.0.4. The backend skill now uses `FS_SECRET_KEY`, the default secret key
|
|
18
|
+
that serves every environment and `--for all` shared bindings, and adds
|
|
19
|
+
guidance on host tooling, infrastructure as code and preview databases.
|
|
8
20
|
|
|
9
21
|
## [0.45.0] - 2026-11-21
|
|
10
22
|
|
package/README.md
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
Create and operate [FartherShore](https://farthershore.com) software businesses
|
|
4
4
|
from the terminal.
|
|
5
5
|
|
|
6
|
-
**Status: `0.
|
|
6
|
+
**Status: `0.46.0`.** Pre-1.0 — the command surface is stable but may still
|
|
7
7
|
change between minor versions. Pin an exact version in CI.
|
|
8
8
|
|
|
9
9
|
FartherShore lets you define a software business as code, then sells, meters,
|
|
@@ -20,13 +20,13 @@ takes `--format json` for non-interactive scripting.
|
|
|
20
20
|
## Install
|
|
21
21
|
|
|
22
22
|
```bash
|
|
23
|
-
npm install -g @farthershore/cli@0.
|
|
23
|
+
npm install -g @farthershore/cli@0.46.0
|
|
24
24
|
```
|
|
25
25
|
|
|
26
26
|
Or run it directly with npx:
|
|
27
27
|
|
|
28
28
|
```bash
|
|
29
|
-
npx -p @farthershore/cli@0.
|
|
29
|
+
npx -p @farthershore/cli@0.46.0 farthershore --help
|
|
30
30
|
```
|
|
31
31
|
|
|
32
32
|
## Authentication
|
|
@@ -358,6 +358,36 @@ farthershore business update weather-api \
|
|
|
358
358
|
|
|
359
359
|
`business publish` enforces the same go-live gates as the dashboard and returns
|
|
360
360
|
stable remediation errors when a prerequisite is missing.
|
|
361
|
+
|
|
362
|
+
`business publish` takes a draft business live with its first release. After
|
|
363
|
+
that, `business release` releases what is on the default branch: it compares
|
|
364
|
+
the branch with the last release that deployed, picks major, minor or patch,
|
|
365
|
+
runs the same go-live checks against the contract being released, and cuts the
|
|
366
|
+
release at that exact commit. In a terminal it shows the commit, version and
|
|
367
|
+
reasons and asks first; `--no-input` skips the question.
|
|
368
|
+
|
|
369
|
+
```bash
|
|
370
|
+
farthershore business release weather-api --dry-run --format json
|
|
371
|
+
farthershore business release weather-api --wait --format json
|
|
372
|
+
farthershore business release weather-api --version 2.0.0 --accept-breaking --no-input
|
|
373
|
+
```
|
|
374
|
+
|
|
375
|
+
`--dry-run` shows the plan and cuts nothing. `--wait` follows the release, and
|
|
376
|
+
the release commit's frontend build when `frontend/` changed, until it is live
|
|
377
|
+
(`--timeout`, default 900 seconds). `--bump major|minor|patch` or
|
|
378
|
+
`--version X.Y.Z` (above the current release) override the version; pass one,
|
|
379
|
+
not both. It refuses with `NOTHING_TO_RELEASE` when nothing changed since the
|
|
380
|
+
last deployed release, and `RELEASE_SOURCE_NOT_READY` while the latest change
|
|
381
|
+
under `business/` is still being checked.
|
|
382
|
+
|
|
383
|
+
Release tags are `<prefix>X.Y.Z`, `v` by default. Changing the prefix continues
|
|
384
|
+
the version numbers and never renames existing tags:
|
|
385
|
+
|
|
386
|
+
```bash
|
|
387
|
+
farthershore business release-tag set weather-api --prefix release- --format json
|
|
388
|
+
farthershore business release-tag set weather-api --clear --format json
|
|
389
|
+
```
|
|
390
|
+
|
|
361
391
|
Recover a Business contract by correcting or reverting its program in Git,
|
|
362
392
|
validating it in preview, and publishing a new release. Use `business status`
|
|
363
393
|
and Apply Timeline to verify the expected release is serving.
|
|
@@ -859,7 +889,7 @@ farthershore skills install
|
|
|
859
889
|
```
|
|
860
890
|
|
|
861
891
|
If the platform-owned skills installer is unavailable, stop and ask the human to run
|
|
862
|
-
`npm install -g @farthershore/cli@0.
|
|
892
|
+
`npm install -g @farthershore/cli@0.46.0`, then repeat the installer help check.
|
|
863
893
|
The CLI keeps itself current (see Staying up to date); do not otherwise install
|
|
864
894
|
or upgrade global tooling autonomously.
|
|
865
895
|
|