Repository navigation
chore: version packages - #25
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 5, 2026 10:20
742ec20 to
09f8f68
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
@managers/server@0.5.0
Minor Changes
#24
db06a62Thanks @edspencer! - The CLI contract's remainingserviceandserveoptions (SPEC §1, §3), ported from Paddock (paddock#996). What a script can see:managers 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. The npx refusal now suggestsnpm i -g @edspencer/managersrather thannpm link, which this refusal would catch.service installrefuses 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.--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 7234.managers serve --quiet(-q) prints only the first line,Managers <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.Patch Changes
02c7989Thanks @edspencer! -managers service installno longer prints a linger line whenloginctlcan't answer; it prints thesudo loginctl enable-lingerline only when linger is off, as CLI contract 1.0 (§7) says.doctorstill reports that case as a skipped check. The copied reference files now name contract 1.0 in their headers.@managers/web@0.5.0