Skip to content

v0.11.0: Merge pull request #183 from pandemicsyn/changeset-release/main

Choose a tag to compare

@github-actions github-actions released this 09 Nov 17:45
049ab53

Beachside v0.11.0

@beachside/adapter

Minor Changes

  • #187 ae8c05a Thanks @pandemicsyn! - Snapshots can carry labels. snapshot({ labels }) sets them at capture where the adapter keeps them, and snapshots.list({ labels }) keeps only matching snapshots.

    • Adapters: an adapter opts in with snapshotCapture.labels: true, and listed SnapshotInfo reports labels. Elsewhere a labelled capture is rejected before anything is captured.
    • Capability: capabilities().snapshots.capture.value.labels says whether labels are kept.
    • Runloop: labels are stored as snapshot metadata, next to the adapter's own beachside_ keys, which stay reserved.
    • Setup: box.runSetup() takes env for every step, kept out of the digest, and runStartup: false, which records startup steps without running them so a snapshot can be taken in between.

    Setup.parallel([...steps]) runs setup steps at the same time as one step; its steps' events and output carry step.group.

beachside

Minor Changes

  • #187 ae8c05a Thanks @pandemicsyn! - Sandboxes can now be set up as they start. sandboxes.create(), sandboxes.with() and snapshot.restore() take setup (steps that run once per sandbox: shell lines, argv arrays, inline scripts or Setup.file() scripts) and startup (steps that run whenever the sandbox comes up without its processes, including after a fresh resume()). Setup.define() makes named setups that compose. Beachside runs the steps over exec on every provider, streams their output through onSetupOutput, records progress in the sandbox so a restored snapshot skips setup it already holds, and throws SetupFailedError naming the failed step. A sandbox whose setup fails is destroyed unless onSetupFailure: "keep". box.runSetup() runs setup on an existing sandbox.

  • #187 ae8c05a Thanks @pandemicsyn! - Snapshots can carry labels. snapshot({ labels }) sets them at capture where the adapter keeps them, and snapshots.list({ labels }) keeps only matching snapshots.

    • Adapters: an adapter opts in with snapshotCapture.labels: true, and listed SnapshotInfo reports labels. Elsewhere a labelled capture is rejected before anything is captured.
    • Capability: capabilities().snapshots.capture.value.labels says whether labels are kept.
    • Runloop: labels are stored as snapshot metadata, next to the adapter's own beachside_ keys, which stay reserved.
    • Setup: box.runSetup() takes env for every step, kept out of the digest, and runStartup: false, which records startup steps without running them so a snapshot can be taken in between.

    Setup.parallel([...steps]) runs setup steps at the same time as one step; its steps' events and output carry step.group.

Patch Changes

  • Updated dependencies [ae8c05a]:
    • @beachside/adapter@0.11.0

@beachside/daytona

Patch Changes

  • Updated dependencies [ae8c05a]:
    • @beachside/adapter@0.11.0

@beachside/e2b

Patch Changes

  • Updated dependencies [ae8c05a]:
    • @beachside/adapter@0.11.0

@beachside/boxd

Patch Changes

  • Updated dependencies [ae8c05a]:
    • @beachside/adapter@0.11.0

@beachside/boat

Patch Changes

  • Updated dependencies [ae8c05a]:
    • @beachside/adapter@0.11.0

@beachside/runloop

Minor Changes

  • #187 ae8c05a Thanks @pandemicsyn! - Snapshots can carry labels. snapshot({ labels }) sets them at capture where the adapter keeps them, and snapshots.list({ labels }) keeps only matching snapshots.

    • Adapters: an adapter opts in with snapshotCapture.labels: true, and listed SnapshotInfo reports labels. Elsewhere a labelled capture is rejected before anything is captured.
    • Capability: capabilities().snapshots.capture.value.labels says whether labels are kept.
    • Runloop: labels are stored as snapshot metadata, next to the adapter's own beachside_ keys, which stay reserved.
    • Setup: box.runSetup() takes env for every step, kept out of the digest, and runStartup: false, which records startup steps without running them so a snapshot can be taken in between.

    Setup.parallel([...steps]) runs setup steps at the same time as one step; its steps' events and output carry step.group.

Patch Changes

  • Updated dependencies [ae8c05a]:
    • @beachside/adapter@0.11.0

@beachside/freestyle

Patch Changes

  • Updated dependencies [ae8c05a]:
    • @beachside/adapter@0.11.0

@beachside/modal

Patch Changes

  • Updated dependencies [ae8c05a]:
    • @beachside/adapter@0.11.0

@beachside/vercel

Patch Changes

  • Updated dependencies [ae8c05a]:
    • @beachside/adapter@0.11.0

@beachside/cli

Minor Changes

  • #187 ae8c05a Thanks @pandemicsyn! - Setup scripts: create and run take --setup <name|path>, --setup-cmd '<shell>', --startup <path> and --startup-cmd '<shell>', which run in the new sandbox once it starts.

    • Named setups: setups in beachside.json defines reusable setups with extends, network and env, and a profile's setup list applies by default (--no-default-setup skips it). beachside setup ls lists them.
    • Startup: startup steps run at create and again after every create --snapshot restore.
    • Failures: a failed step exits 9 with SETUP_FAILED. create keeps the sandbox, or removes it with --rm-on-failure; the record shows each step's outcome.
    • Rerun: beachside setup <sandbox> reruns only the missing steps, and --force reruns everything.
    • Add-ons: --with installs its servers through the same setup engine.

    Setup caches: a setup with "cache": true (or create --cache) is snapshotted after setup and before startup. The next create with the same setup restores it and runs only cache: false steps and startup.

    • The key covers the provider, scope, profile, image, every step and the files in cache.files.
    • Freshness: caches go stale after maxAge (7 days by default) and are rebuilt on the next create.
    • Secrets: a setup whose env holds secrets is refused unless it sets secrets: "allow".
    • Commands: beachside setup cache ls|rm|prune manages caches, and gc prunes stale ones. --no-cache and --refresh-cache control one create.

    Setups can also come from a repository: with "projectSetups": true or BEACHSIDE_PROJECT_SETUPS=1, the CLI reads .beachside/setup.json (setups plus default) from the checkout. A step can be { "parallel": [...] } to run several steps at once as one setup step.

  • #184 05f225d Thanks @pandemicsyn! - beachside create --with rex|herdr installs a server in the new sandbox and puts it on your Tailscale tailnet, with the auth key from TAILSCALE_AUTH_KEY sent only over stdin.

    • Rex: runs on Rex's own Tailscale, and create waits for its HTTPS address.
    • herdr: gets a Tailscale SSH device to attach to with herdr --remote.
    • Connection details: create and inspect print how to connect, the sandbox record keeps the add-ons, and rm logs each device out of the tailnet.
    • Network: --with implies --network internet.

    A create the provider rejects with no image set now keeps the provider's own message, rather than always saying an image is needed. Previously an E2B lifetime over its cap read as "needs an image".

Patch Changes

  • #182 1577530 Thanks @pandemicsyn! - The bundled beachside-cli skill now shows agents Rex's exact split-pane commands: rex run --split=right -s "$REX_SESSION" --keep-open --json, then rex wait and rex capture by the saved pane id. It also explains how to start a Rex server inside a sandbox, following the Rex guide.
  • Updated dependencies [ae8c05a, ae8c05a]:
    • beachside@0.11.0
    • @beachside/adapter@0.11.0