Repository navigation
chore: version packages - #16
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
4 times, most recently
from
November 5, 2026 08:35
0769bc4 to
d91f5e6
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 5, 2026 09:31
d91f5e6 to
7945a0f
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.4.0
Minor Changes
#20
a19f89bThanks @edspencer! - Align themanagersCLI with the CLI contract (SPEC 0.2)serveis now the name for running in the foreground,/api/healthreports theversion it is running,
service statusanswers in scriptable exit codes and--json, there is aservice logs, and the generated units are hardened. Portedfrom Paddock 0.80–0.82, whose CLI this is.
Behaviour changes a script can see. These are why this is a minor:
2, not1. An unknown command, flag or bad valueexits 2 and prints a short usage synopsis after the message.
1now means onlythat something genuinely failed.
service statusnow exits3or4.0when installed, running andanswering;
3when installed but not running, or running and not answering;4when there is no unit.service logs,start,stopandrestartexit4with no unit too.install,startorrestartthat never answers now exits1, not 0.<data-dir>/logs/service.log(the path macOS already used, now one file ratherthan two), which Managers rotates itself at 8 MB, keeping three generations.
An existing unit keeps the path it names until
managers service installisre-run.
serve's first stdoutline is
Managers <version>: <url>. Docker, Kubernetes and the service unitscollect both streams; a log shipper reading stdout ALONE is the one thing that
changes.
Everything else is additive:
managers serveruns the server;managers startstays an alias, for good.GET /api/healthanswers{ ok, version }, with no auth.managers service status --json: installed / running / answering, theinstalled and running versions, port, URL, pid, unit, log file and warnings.
managers service logs [-f] [-n <lines>], the last 50 lines by default.--helplists all sevenserviceactions.PATHwithout per-sessionentries or missing directories, every systemd
ExecStartword quoted, andwarnings for a vanished Node, a running-vs-installed version gap and (Linux)
lingering being off, which is now checked rather than printed at everyone.
install,startandrestartno longer lose a race with launchd(
Bootstrap failed: 5: Input/output error): they wait for a bootout to finish,and retry a bootstrap that returns launchd's race codes 5 or 37.
systemctl --user enable --nowdoes nothing to an active unit, so the oldprocess went on serving the old code.
#21
6be9d28Thanks @edspencer! -managers busy,GET /api/busy, aservice stopthat refuses when Managers is mid-turn, and a SIGTERM that finishes or records the work under wayWave F2 of the CLI-contract rollout (edspencer/cli-contract SPEC 0.2, §4), ported from Paddock 0.81.
New:
managers busy [--json]. Asks the running instance whether it is in themiddle of something a restart would lose. It exits 0 not busy, 75 busy,
3 when nothing answers, and 1 when something answered but not as
Managers' busy check. 75 is
EX_TEMPFAIL, which Watchtower'slifecycle.pre-updatehook reads as "skip this one".service stopandservice restartnow run that check first and refuse withexit 75 unless
--forceis given. A script that stops Managers unconditionallyneeds
--force, or needs to handle 75: that is the behaviour change in thisrelease.
service uninstallandservice startdon't check. A forced stopprints the message it would have refused with, prefixed
Overriding:.--forceanywhere else is now a usage error (exit 2) rather than beingsilently ignored. When the busy work is chat turns, the refusal says to run the
command from a terminal rather than from inside a Managers chat.
New:
GET /api/busy, answering{ busy, version, counts }with four counts:chat(chat turns running, triggers and schedules included),background(background tasks a live session still holds after its turn),
job(herdctlscheduler jobs) and
run(Managers trigger runs in flight: from the moment afire writes its
runningrecord until that record is finished and committed,which is wider than the turn at both ends). No authentication, because it
carries counts and nothing else; in-memory state only.
New:
<data-dir>/runtime.json, written 0600 once the server is listening andremoved when it stops, holding
{ pid, port, url, version, startedAt }.SIGTERM now finishes or records the work under way, instead of closing at
once. If chat turns or trigger runs are in flight, a stop waits up to 8 seconds
for them to end by themselves; whatever is left is recorded — each trigger run's
record is finished as
failed,error: interrupted by shutdown(through its owncompletion hook, so a consolidation still gets its
#reflectionepisode and therecord is committed), and the log names what was cut short. An idle instance
stops at once. Signals are idempotent and the whole stop is bounded at 15
seconds, inside launchd's 20-second kill budget. Under Docker, whose default
docker stoptimeout is 10 seconds, give the container astop_grace_periodofat least 20 seconds to let the wait run.
#22
0b24695Thanks @edspencer! -managers update,managers doctor, andservice install --refreshWave F3 of the CLI-contract rollout (edspencer/cli-contract SPEC 0.2), ported from Paddock 0.82 and the contract's
reference/.New:
managers update [--check] [--to <version|tag>] [--yes] [--force] [--json](upgradeis a hidden alias). It asks the registry, checks the running instance is not busy, stops the service, installs with the package manager this copy came from, hands over to the new CLI to rewrite the unit, waits for/api/healthto report the new version, and rolls back if it doesn't. Exit codes a script can see: 5 this install can't update itself (a checkout, npx, a container, or a managed install: the right command is printed), 6 the update failed and the old version is running again, 7 it failed and could not be rolled back, 75 busy, 2 no terminal and no--yes.--checkexits 0 whether or not there is an update; readupdateAvailablefrom--json. Nothing contacts the registry on its own.New:
managers doctor [--json] [--offline]. SPEC §1's eight checks (Node againstengines, the install method, the unit, the running version, the port, linger, the data dir, a newer version), then Managers' own: the configuration loads, and the security posture/api/securityreports (no authentication, trusted-header, any-audience JWTs, batch drive mode), asked of the running instance or computed from this shell's configuration by the server's own rule. Exits 1 if any check failed.New:
managers service install --refreshre-renders an existing unit from the settings it records (port, host, data dir), and exits 4 with nothing installed.service statusrepeats what the lastupdate --checkordoctorfound (updatein--json, absent rather than null when there's nothing).service startandrestartrunsystemctl --user reset-failedfirst. A firstservice installthat launchd or systemd refuses no longer leaves a unit behind (sostatusdoesn't report it installed); a refused reinstall keeps the unit it had.The image sets
MANAGERS_IN_DOCKER=1and putsmanagersonPATH, sodocker exec <container> managers busyworks as a pre-update hook andmanagers updateinside it prints the image to pull and exits 5. SetMANAGERS_UPDATE_HINTto haveupdateprint your own upgrade command instead (for a container or install managed by Ansible, say).--check,--to,--yes,--refreshand--offlineexit 2 on commands that can't act on them. See UPDATING.md.Patch Changes
#15
f0aba1cThanks @edspencer! - "Wake the manager now" wakes the trigger that asked, not onlywake. A run that sets a task to awaiting-ed now recordsraisedBy: {trigger, run}on it (older tasks are traced through the run id in their log). Answering with wake fires that trigger, or falls back towake, and never a trigger whose behaviour is off.GET …/managers/wakereturns the same target per task (trigger, atasksmap,?task=), and the switch names a trigger other thanwake("runs roadmap").#19
2b760a6Thanks @edspencer! - Dependency security updates:zodgoes to ^4.6.6 (GHSA-mrhx-c7xc-m3w5, memory exhaustion when validating oversized constrained collections; every state write is validated by a strict zod schema) andbody-parserto 2.4.0 (GHSA-27r3-jxmh-p828, via the MCP SDK's express).@managers/web@0.4.0
Patch Changes
f0aba1cThanks @edspencer! - "Wake the manager now" wakes the trigger that asked, not onlywake. A run that sets a task to awaiting-ed now recordsraisedBy: {trigger, run}on it (older tasks are traced through the run id in their log). Answering with wake fires that trigger, or falls back towake, and never a trigger whose behaviour is off.GET …/managers/wakereturns the same target per task (trigger, atasksmap,?task=), and the switch names a trigger other thanwake("runs roadmap").