Repository navigation
chore: version packages - #995
Merged
Merged
Conversation
Deploying paddock with
|
| 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 |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 5, 2026 08:54
9498ab4 to
7560b11
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 5, 2026 09:06
7560b11 to
062a1c8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
cd8e29bThanks @edspencer! -paddock doctor [--json] [--offline]— check that Paddock can run here, with a fix for each problem. The--helpand the updating guide already named it; now it exists. One line per check, starting✓,!(a warning),✗(a failure) or-(doesn't apply here), with afix:line under every warning and failure.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-homeandupdate. Then Paddock's own:config(the config loads asservewould load it),projects(the projects folder is writable),claude-login(which kind of Claude login it would use — never the login itself) andclaude-cli(aclaudeon PATH, which the sweeper always needs anddriveMode: batchneeds for every turn).--jsonprints one document on stdout,{ ok, version, checks: [{ id, status, message, fix? }] }, matching the contract'sschemas/doctor.schema.json; the update notice goes to stderr.<data-dir>/update-check.jsonthe wayupdate --checkdoes, soservice statusrepeats it — into a data dir that's already there only, sodoctornever creates an instance. An unreachable registry is a warning, not a failure.--offlineskips it.doctorwrites nothing else.--offlineis a usage error (exit 2) on every other command, like--force,--checkand--refresh.#996
0e2b624Thanks @edspencer! - The CLI contract's remainingserviceandserveoptions (SPEC §1, §3). What a script can see:paddock service install --dry-runprints 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--refreshtoo, and with--json({ ok, action, dryRun, unit, contents }).service installrefuses to run from a git checkout (or annpm 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 installrefuses 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.--jsononservice install,uninstall,start,stopandrestart: one document on stdout,{ ok, action, error?, …the service's status afterwards }(the same fields asservice status --json), with every word of prose on stderr. The exit codes don't change;errorisbusyfor a 75 andnot installedfor a 4.service installagain 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 9000service moved it to 7233.paddock serve --quiet(-q) prints only the first line,Paddock <version>: <url>.--dry-runand--from-checkout(service installonly),--quiet(serveonly) and--jsonon a command that has no JSON document —serve,service logs,config eject— now exit 2. They used to be accepted and ignored.service installthat systemd or launchd refuses no longer leaves its unit behind (re-synced with cli-contract'sreference/service/); a reinstall that fails keeps the unit that was there.@paddock/web@0.83.0