skydive-cli 0.4.0 → 0.4.1-beta.2

package/CHANGELOG.md

@@ -7,6 +7,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+### Added
+
+- `skydive fs` — a namespace for working with the files on an agent's computer (its sandbox) from your own machine. Its first subcommand, `skydive fs edit <path>`, reads a remote file down over the same relay `skydive sandbox` uses, opens it in your local editor (`$VISUAL`/`$EDITOR`, override with `--editor`, defaults to `vi`), and writes your changes back atomically when you save and close — so you can edit a remote file as if it were local without opening the chat TUI. A path that doesn't exist yet is created on save; no changes means nothing is written. Access is gated on EDIT permission for the agent, exactly like `skydive sandbox`. (A first-class `fs` relay channel and `skydive fs mount` land in follow-ups.)
+
 ## [0.4.0] - 2026-08-07
 
 ### Added

package/README.md

@@ -521,3 +521,54 @@ Mach-Os, OpenTUI's tree-sitter worker needs explicit embedding, and
 `NODE_ENV=production` silently breaks highlight repaints) — see the header
 comment in `scripts/build-binary.ts` before changing any of the flags it
 passes.
+
+## Releasing
+
+The CLI ships on two channels, both driven by merges to `anyone`
+(`release-skydive-cli.yml` for npm, `release-skydive-cli-binaries.yml` for the
+standalone binaries — they always publish the same version for a given commit).
+
+Versions come from [yarn's release workflow][yarn-release]: **a PR that changes
+this workspace declares how it affects the next release**, and the declaration is
+reviewed as part of the diff.
+
+```sh
+yarn workspace skydive-cli version patch --deferred    # bug fix
+yarn workspace skydive-cli version minor --deferred    # new feature
+yarn workspace skydive-cli version major --deferred    # breaking change
+yarn workspace skydive-cli version decline --deferred  # no user-visible change
+```
+
+Each writes a small record to `.yarn/versions/*.yml` — commit it.
+`yarn version check --interactive` picks the strategy from a menu instead, and
+`yarn version check` is what CI enforces (scoped to this workspace by
+`check-skydive-cli-version-record.yml`). A PR that only bumps `version` in
+`package.json` is exempt: the bump is itself the declaration.
+
+**canary** (automatic, opt-in for users) — every merge affecting the CLI or a
+workspace it depends on publishes a prerelease of the _next_ version to the npm
+`beta` dist-tag and the `canary` binary channel: `0.3.1-beta.4` while `0.3.0` is
+the release. The `beta.N` counts betas already on that line, so it restarts at 1
+after each release. A merge with no version record (a dependency-only change)
+falls back to a patch line.
+
+> The version is a prerelease of the **next** version, never of the released one.
+> `0.3.0-beta.4` sorts _below_ `0.3.0` per semver, which is how canary once ended
+> up permanently "older" than stable while carrying newer code. The resolver
+> refuses to publish a canary that doesn't sort above the released stable — see
+> `scripts/resolve-release-version.mjs`.
+
+**stable** (deliberate) — cutting a release is a reviewed PR that consumes the
+accumulated records and cuts the changelog:
+
+```sh
+yarn version apply --all          # records -> the new version in package.json
+```
+
+Then move `CHANGELOG.md`'s `[Unreleased]` entries under the new version heading
+and open the PR. Merging it publishes to the npm `latest` dist-tag and the
+`stable` binary channel — a plain `npm i -g skydive-cli` and the default
+`install.sh` resolve that. Review of the bump PR is the release gate; nothing
+publishes to stable automatically.
+
+[yarn-release]: https://yarnpkg.com/features/release-workflow

package/dist/js/{billing-blocked-euid6MN9.mjs → billing-blocked-Dgu5-oDy.mjs}

@@ -1,4 +1,4 @@
 #!/usr/bin/env node
-import { a as billingBlockedOutcomeSchema, i as billingBlockedOutcomeFromSendResponse, n as BillingBlockedError, r as billingBlockedJsonResult, t as BILLING_BLOCKED_EXIT_CODE } from "./billing-blocked-CwfG1BTR.mjs";
+import { a as billingBlockedOutcomeSchema, i as billingBlockedOutcomeFromSendResponse, n as BillingBlockedError, r as billingBlockedJsonResult, t as BILLING_BLOCKED_EXIT_CODE } from "./billing-blocked-2wju4gC_.mjs";
 
 export { BILLING_BLOCKED_EXIT_CODE, BillingBlockedError, billingBlockedJsonResult };