Skip to content

chore: version packages - #25

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

@managers/server@0.5.0

Minor Changes

  • #24 db06a62 Thanks @edspencer! - The CLI contract's remaining service and serve options (SPEC §1, §3), ported from Paddock (paddock#996). What a script can see:

    • managers 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. The npx refusal now suggests npm i -g @edspencer/managers rather than npm link, which this refusal would catch.
    • service install refuses a port something else holds, exit 1, rather than writing a service that can only crash-loop. A Managers on the port (a reinstall) is fine, and so is the unit's own running service. A Paddock on the port counts as something else.
    • --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 7234.
    • managers serve --quiet (-q) prints only the first line, Managers <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.

Patch Changes

  • #23 02c7989 Thanks @edspencer! - managers service install no longer prints a linger line when loginctl can't answer; it prints the sudo loginctl enable-linger line only when linger is off, as CLI contract 1.0 (§7) says. doctor still reports that case as a skipped check. The copied reference files now name contract 1.0 in their headers.

@managers/web@0.5.0

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 742ec20 to 09f8f68 Compare November 5, 2026 10:20
@edspencer
edspencer merged commit 5622706 into main Nov 5, 2026
1 check passed
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