Skip to content

chore: version packages - #995

Merged
edspencer merged 1 commit into
mainfrom
changeset-release/main
Nov 5, 2026
Merged

edspencer merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 5, 2026 •

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@paddock/server@0.83.0

Minor Changes

  • #994 cd8e29b Thanks @edspencer! - paddock doctor [--json] [--offline] — check that Paddock can run here, with a fix for each problem. The --help and the updating guide already named it; now it exists. One line per check, starting ✓, ! (a warning), ✗ (a failure) or - (doesn't apply here), with a fix: line under every warning and failure.

    • The CLI contract's eight checks, with the ids every tool uses: node-engines, install-method, unit (installed, running and answering; its Node and CLI still there; the same install as this CLI), running-version, port (free, or held by Paddock), linger (Linux), data-home and update. Then Paddock's own: config (the config loads as serve would load it), projects (the projects folder is writable), claude-login (which kind of Claude login it would use — never the login itself) and claude-cli (a claude on PATH, which the sweeper always needs and driveMode: batch needs for every turn).
    • What a script can see: exit 1 if any check failed, 0 otherwise (warnings don't count), 2 for a usage error. --json prints one document on stdout, { ok, version, checks: [{ id, status, message, fix? }] }, matching the contract's schemas/doctor.schema.json; the update notice goes to stderr.
    • The update check asks the npm registry — only because you ran it — and writes <data-dir>/update-check.json the way update --check does, so service status repeats it — into a data dir that's already there only, so doctor never creates an instance. An unreachable registry is a warning, not a failure. --offline skips it. doctor writes nothing else.
    • --offline is a usage error (exit 2) on every other command, like --force, --check and --refresh.
  • #996 0e2b624 Thanks @edspencer! - The CLI contract's remaining service and serve options (SPEC §1, §3). What a script can see:

    • paddock service install --dry-run prints the unit it would write (the systemd unit or the launchd plist) on stdout, says where it would go on stderr, and writes nothing — not the unit, not a folder. It works with --refresh too, and with --json ({ ok, action, dryRun, unit, contents }).
    • service install refuses to run from a git checkout (or an npm link), exit 1, unless you add --from-checkout: a unit that runs a working tree follows every rebuild, branch switch and move of it. A global install is unaffected.
    • service install refuses a port something else holds, exit 1, rather than writing a service that can only crash-loop. A Paddock on the port (a reinstall) is fine, and so is the unit's own running service.
    • --json on service install, uninstall, start, stop and restart: one document on stdout, { ok, action, error?, …the service's status afterwards } (the same fields as service status --json), with every word of prose on stderr. The exit codes don't change; error is busy for a 75 and not installed for a 4.
    • Running service install again keeps the installed unit's settings — its port, host, data dir and verbosity — unless a flag says otherwise (SPEC §1). It used to do that only with --refresh, so a plain reinstall over a --port 9000 service moved it to 7233.
    • paddock serve --quiet (-q) prints only the first line, Paddock <version>: <url>.
    • Flags belong to their commands: --dry-run and --from-checkout (service install only), --quiet (serve only) and --json on a command that has no JSON document — serve, service logs, config eject — now exit 2. They used to be accepted and ignored.
    • A first service install that systemd or launchd refuses no longer leaves its unit behind (re-synced with cli-contract's reference/service/); a reinstall that fails keeps the unit that was there.

@paddock/web@0.83.0

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Nov 5, 2026 •

Copy link
Copy Markdown

Deploying paddock with  Cloudflare Pages  Cloudflare Pages

Latest commit: 062a1c8
Status: ✅  Deploy successful!
Preview URL: https://b232e562.paddock-7u2.pages.dev
Branch Preview URL: https://changeset-release-main.paddock-7u2.pages.dev

View logs

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 9498ab4 to 7560b11 Compare November 5, 2026 08:54
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 7560b11 to 062a1c8 Compare November 5, 2026 09:06
@edspencer
edspencer merged commit 87ae569 into main Nov 5, 2026
2 checks passed
@edspencer
edspencer deleted the changeset-release/main branch November 5, 2026 09:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant