Repository navigation
chore: version packages - #86
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
November 5, 2026 09:01
4c654fe to
e911bcb
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 5, 2026 09:18
e911bcb to
bab43bd
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
local-review@0.17.0
Minor Changes
#87
50372f8Thanks @edspencer! ---jsononservice install,uninstall,start,stopandrestart(cli-contract SPEC §1), asservice statusalready had. With it, stdout carries exactly one JSON document,{ ok, action, error?, … }followed by everyfield of
service status --jsonas it is afterwards, and the messages that used to go to stdout go to stderr. Theexit code is the one without
--json.errorisbusyon exit 75,not installedon exit 4, and the reason on exit1, including an install that's refused (npx's cache, a checkout, a port in use). Each command adds what it found:
installdryRun(anddefinition, the file it would write),refreshedandchanged;startandstopwasRunning;restartrewritten;uninstallwasInstalled. It's the same shape as Hallway's.Scripts that passed
--jsonto these commands used to get a usage error (exit 2); now they get the document.service logs --jsonis still a usage error.Patch Changes
#89
e64b022Thanks @edspencer! -service installchecks linger on Linux (cli-contract SPEC §7) instead of always printing a reminder. It asksloginctl show-user <user> -p Linger, and only when linger is off does it say why it matters (the service stops whenyou log out) and print
sudo loginctl enable-linger <user>, the same linedoctorgives. It never runssudo. Whenlinger is on, or
loginctlcan't answer (no logind, a container), it says nothing about it. With--json, theadvice is in the document's
warnings. The old reminder line,loginctl enable-linger $USERwithoutsudo, hasgone from the install output.
#85
464432cThanks @edspencer! - The service's log is rotated.servenow rotates<data>/logs/service.logitself, when it starts and every 15minutes: past 8 MB it's copied to
service.log.1and truncated in place (launchd and systemd keep it open), oldercopies shift down, and three are kept,
service.log.1to.3. Until now it grew without limit. You'll see thenumbered copies next to it in
logs/once it passes 8 MB; a foregroundlocal-reviewhas no service log and doesnothing.
A first
service installthe service manager refuses no longer leaves a unit behind. When systemd refuses toreload, enable or start it, or launchd refuses to bootstrap it,
installstill fails (exit 1, with the reason), but itnow removes the unit or LaunchAgent it had just written, so
service statussays it isn't installed (exit 4) ratherthan installed and not running, and the next login doesn't try it again. A reinstall that's refused keeps the unit it
had.