Skip to content
Castellan

All release notes

Steward: release notes

Each version, newest first.

0.27.12

Each repository's release PC is shown in the staff table now, so it no longer needs a section of its own.

What changed

  • The Release PC section is gone. Each repository's row in the Staff (or Your repositories) table has a Release PC column. It says which PC merges and releases the repository and whether it's kept there, and it holds the Do it here, Keep it on this PC and Unpin buttons.
  • Claims another PC made too, and turns for repositories still being looked at, are listed under the table.

Before you update

  • Nothing: it updates itself as usual.

0.27.11

It hands out kit 2.39.0, which hands every agent Manor's Developer options switch.

What's new

  • Every agent can now follow the Developer options switch on Manor's Settings page. If you don't develop software, Castellan's pages leave the technical detail out. Turning the switch on or off applies to every agent within seconds, with nothing restarted.

What changed

  • When Developer options are off, each agent's Where its work runs says "the local AI" and describes its work in plain words, without the names of tools or model servers. The agent's page doesn't show where its files are kept. Its settings don't show the settings file's path or that file's own error messages.
  • Turn Developer options on to see all of it, as before.

Before you update

  • Nothing: it updates itself as usual. If you want the technical detail on your agents' pages, turn on Developer options on Manor's Settings page.

0.27.10

It hands out kit 2.38.0: Reeve, the Chamberlain and Heiward get their own title-bar scenes, and so do the Thatcher, the Reckoner, the Weigher and the Shepherd.

What's new

  • Three more agents have their own picture in the title bar, moving while they work, in the colours of their icons: Reeve reads a log scrolling past an amber line and keeps count in tally marks; the Chamberlain seals a letter in red wax and files it in its pigeonhole; Heiward's shears trim the sprigs growing out of a hedge.
  • This release brings 0.27.8 too, which was never released on its own: the Thatcher's, the Reckoner's, the Weigher's and the Shepherd's scenes.

Before you update

  • Nothing: it updates itself as usual. Each agent takes the new kit as the Steward rolls it out.

0.27.9

The kit it hands out publishes nothing of Castellan's on GitHub but Heiward.

What changed

  • This brings kit 2.37.0. Every agent's release now goes to Castellan's release service and to its own repository, never to the public releases repository. Agents held back from sale are included. Heiward is the exception and is still published on GitHub. A release the release service doesn't take now fails, with a line saying how to finish it, instead of going to GitHub.
  • Manor can now be published to the release service.

Before you update

  • Nothing: it updates itself as usual.

0.27.8

It hands out kit 2.36.2: the Thatcher, the Reckoner, the Weigher and the Shepherd get their own title-bar scenes.

What's new

  • Each of the four newest agents has its own picture in its title bar, moving while it works, in its own colour: a roof thatched course by course, counters slid across a counting board, a balance that tips and settles, and a sheep walked into its fold. Until now they showed the turning cogs of an agent without one. Their Settings' Where its work runs now says what each round does too.

Before you update

  • Nothing: it updates itself as usual. Each agent takes the new kit as the Steward rolls it out.

0.27.7

An agent's release notes for a new kit never name a repository, and a kit is tried with the notes its rollout will write.

What changed

  • When the Steward rolls out a kit whose changelog it couldn't read, each agent's release notes now say "the parts every agent of the manor shares". Before, they named the repository the kit came from, and those notes are published with each release.
  • When a kit change is tried on every agent before it merges, each agent's notes are now written from that kit's own changelog, as its real rollout will write them. An agent whose tests check its notes no longer fails the trial over a line it would never ship.

Before you update

  • Nothing: it updates itself as usual.

0.27.5

An employee's kit parts are read from its own kit.json, the one place they are kept.

What changed

  • The Steward no longer keeps its own copy of each repository's kit parts. That copy didn't know the React part, so every agent with a React page carried a note on the Steward's page, "kit.json takes node, web, spec, react; Settings say node, web, spec", though nothing was wrong: an agent's kit has always been filled from its kit.json.
  • The page now shows each repository's parts as its kit.json says them, React included, and the note is gone.
  • Settings no longer has a Kit parts field for a repository. To change an agent's parts, change its kit.json.
  • Taking on a repository (Look after, or employ) lists the parts its kit.json takes.
  • Taking on an agent whose src/app.ts writes its id and name in double quotes (or backticks) now takes its name as written: the Crier was taken on as "crier".

Before you update

  • Nothing: it updates itself as usual. The old parts in settings.json are left there and no longer read.

0.27.2

It installs one of your own agents the first time, when Manor's Hire asks.

What's new

  • An agent that is yours alone (built here from its clone, never published) can now be hired the first time: Manor's Hire asks the Steward, which builds the version on its branch and installs it. Before, a release only kept such an agent up to date once it was installed, and the first install was a command run by hand in its clone.
  • In a terminal: node src\cli.ts release --employees <id> --hire.

What changed

  • A hire installs only an agent built here that isn't installed yet. One that is fired stays gone until it is hired again.

Before you update

  • Nothing: it updates itself as usual. Manor shows Hire for your own agents once it is updated too.

0.27.0

Your PCs agree among themselves which one merges and releases each repository, through the repository itself: no licence or Castellan service needed.

What's new

  • Each repository gets one release PC, chosen by your PCs through a small marker in the repository's own remote. It works with any Git host, and for anyone, with or without a licence.
  • The Steward's page shows who has each repository ("Merging and releasing for Clerk: done by DESKTOP-ABC"), with Do it here to move it now, and Keep it on this PC to keep it there. A kept PC that goes quiet for a day can be taken over, and the page says so.
  • Version claims are shared through the repository too, so work started side by side on two PCs never takes the same version. Offline, a claim is made on the PC as before, and shared once it can reach the remote. If another PC took the same version meanwhile, the page says so and the later work gets a new version when it merges.

What changed

  • Only publishing waits for a PC's turn: merging, releasing, and the pushes of a refresh, a kit update or a catch-up. Builds, tests, tastings, bumps and claims never wait, online or offline.
  • When this PC can't reach a repository's remote, the page says releasing waits until it can. Nothing else stops.
  • Taking turns no longer goes through Castellan's release service. The turns from 0.24.0 are gone.

Before you update

  • Nothing: it updates itself as usual. On its first round each PC marks the repositories it looks after. With only one PC, everything works exactly as before.
  • Update the Steward on every PC: an older one doesn't take turns, and the alarm for another Steward names it.

0.26.0

GitHub is no longer required: the Steward finds the source control on your PC and sets itself up for each repository.

What's new

  • The Steward looks at what is installed on your PC (Git, the GitHub CLI, and others such as Mercurial or Subversion) and chooses by itself how to work with each repository. A new Settings choice, Source control, shows what it found and offers only what you have, usually one option. Automatic is the default.
  • Repositories on any host. GitLab, Azure DevOps, Bitbucket, your own server or a shared folder: anything you reach with plain git. The Steward reads each repository's branch and tags from its origin. When the branch carries a version that isn't released yet, it runs your release command (or none, with Release it set to tag) and pushes a v<version> tag to the repository, with that version's changelog entry as the tag's message. There are no pull requests to merge that way: what lands on the branch is released.
  • Look after now offers your clones on any host, not only the ones on GitHub.
  • Repositories on GitHub work exactly as before wherever the GitHub CLI is installed and signed in. Without it, they're worked with plain git too.

What changed

  • A repository's name in Settings can be a host and path, such as gitlab.com/group/app, as well as GitHub's owner/name.
  • Mercurial, Subversion, Perforce and Plastic SCM are found and named, but the Steward doesn't work with them yet.

Before you update

  • Nothing: it updates itself as usual. A PC where the GitHub CLI is installed and signed in keeps working with GitHub as before.

0.25.2

It hands out ports for new agents, as it hands out versions, and says when two agents share one.

What's new

  • claim-port <agent id> gives a new agent its page's port before anyone writes one: the next free one after every port Manor's staff, this PC's own staff, the agents announced on GitHub, each repository's src/app.ts and every earlier claim use, with its development port (+10000) free too. A new agent needs no repository yet. Asking again for the same agent gives the same port; an agent that has one keeps it. release-port gives one back.
  • ports lists every port in use, by whom and where each says so.
  • When two agents have the same port, a round raises an alarm naming both, before either is installed. Manor offers only one of two such agents for hire, so the other's role used to sit empty with no word why: the Assayer and the Shepherd both had 20707.

0.25.1

A Castellan release service that can't be reached never stops a Steward that works alone.

What changed

  • On a PC with a Castellan licence, the Steward 0.24.0 stopped merging and releasing whenever it couldn't reach Castellan's release service, even though it had never taken turns with another PC. Now it goes on exactly as before. Only a PC that was already taking turns waits for the service, so it never merges beside another of your PCs.
  • An answer from the service that says nothing about turns counts as no turns, the same as before.

Before you update

  • Nothing: it updates itself as usual.

0.24.1

Work merged out of order no longer gets stuck on its version: the Steward renumbers the kit too, and keeps the version claims in step.

What's new

  • The kit's version can be claimed, as every repository's can: claim-version kit --branch <b> --for "<what>", and release-version kit <version>. It counts above kit/VERSION, every kit release, every kit version an open pull request names, and every live claim, apart from the Steward's own version.

What changed

  • When another change with a higher version merges first, catching a pull request up now settles the kit as well as the Steward's version: kit/VERSION, the kit's changelog (its entry above the one that merged first, under its new number), the Steward's pin of its own kit, the kit number its own changelog entry names, and its title. Before, a conflict there waited for a person.
  • A pull request caught up to a new version takes its branch's claim with it: the old version is free again, the new one is held, and the work's author asking again is handed the new one.

Before you update

  • Nothing: it updates itself as usual.

0.24.0

Your PCs on one Castellan licence take turns: each repository is merged and released by one Steward, and versions are claimed once for all of them.

What's new

  • On a PC with a Castellan licence, the Steward takes its turn at each repository before it merges or releases there, through the Exchequer. A repository another of your PCs is looking after is left alone, so two Stewards never merge and release the same pull requests.
  • The page says which repositories another PC looks after ("Merging and releasing for Clerk: done by DESKTOP-ABC"), with a Do it here button that moves it to this PC at once.
  • A repository cloned on only one PC is always looked after there.
  • claim-version hands out versions for all your PCs at once, so work started on the desktop and the laptop side by side never takes the same version.

What changed

  • When the Exchequer can't be reached, the Steward keeps looking after the repositories it already had, until its turn runs out, and takes on no others: a round may be slower, but nothing is merged twice.
  • The alarm for another Steward (0.23.2) doesn't count what a PC does in a repository whose turn it has: only a Steward that doesn't take turns raises it.

Before you update

  • Nothing: it updates itself as usual. Without a licence on the PC, or until the Exchequer takes turns (its 0.7.0), everything works exactly as before.
  • For the turns to work, update the Steward on every PC: an older one doesn't take turns.

0.23.5

An old Steward on a second PC updates quietly: it no longer takes itself for the PC that releases Castellan.

What changed

  • A Steward from before 0.19 that updates on a PC without the Exchequer's publisher key now comes up with Castellan's work off: no kit rollout, no releases of its own, nothing merged or released by itself. It waits for your yes in its Settings. Before, any Steward that had run before was taken as Castellan's release machine. On a second PC that made it a second Steward, merging and releasing the same repositories as the first.
  • The PC that holds the key updates exactly as before.

Before you update

  • Nothing: it updates itself as usual. A Steward already on 0.19 or later keeps its Settings as they are.

0.23.2

It raises an alarm when another Steward, or someone else, merges its PRs or releases its agents.

What's new

  • On the PC that releases Castellan, the Steward now notices when one of its own PRs is merged, or one of its agents is released, and no round of its own did it. Most likely another PC runs a Steward signed in to the same GitHub account. One alarm names the agents, the PRs and the releases, in the Steward's page and in Manor, and clears by itself a day after the last one.
  • Did it yourself, by hand? Dismiss the alarm: what it names is taken as yours, and only a new one raises it again. Or mark it as yours, before or after: node src\cli.ts mine porter v0.5.14 (or #65 for a PR).
  • It is seen from what each round already reads from GitHub, plus git in the agent's checkout here. Nothing more is asked of GitHub.

Before you update

  • Nothing: it updates itself as usual. The first round after the update only learns which releases and PRs are already there, so the update itself raises nothing. On every other PC nothing changes.

0.21.3

It hands out the kit 2.36.1: GenieX 0.8.0 is the NPU's server on a Snapdragon.

What changed

  • A Snapdragon PC whose NPU is set up from now on gets GenieX 0.8.0 instead of 0.7.0. It has been run on a Snapdragon X2 Elite: it installs the same way, answers chat and pictures, and uses the same model files.
  • A PC already running 0.7.0 keeps it. The Smith offers 0.8.0 to try under New for your NPU, and puts 0.7.0 back if you remove it.
  • Each agent gets this with its next kit update, through the Steward as usual.

Before you update

  • Nothing: it updates itself as usual.

0.21.2

It hands out the kit 2.36.0: a staff release is published only on the PC that holds the Exchequer's key, so none skips the Exchequer.

What changed

  • A release of one of Castellan's staff now publishes nothing on a PC without the Exchequer's publisher key. That means no GitHub release, public or private. Before, such a release went to GitHub alone, and paying customers never got it from the Exchequer.
  • With the key, as on the PC that releases Castellan, releases go out exactly as before.
  • Manor and Heiward, which are never sold, are released as before.
  • Each agent gets this with its next kit update, through the Steward as usual.

Before you update

  • Nothing: it updates itself as usual.

0.21.0

It hands out the kit 2.35.0: a release of an agent Castellan sells goes to the Exchequer, not the public releases repository.

What changed

  • The release of an agent that Castellan sells is published to the Exchequer, Castellan's release service, and no longer to the public releases repository. The Steward still sees it released, by the agent's own repository.
  • The agents not for sale go to the releases repository as before, and to the Exchequer too. That's Manor, Heiward, and the agents held back from sale.
  • If the Exchequer can't say which agents it sells, or doesn't take a release, the release goes to the releases repository as before. A release is never held back, and nothing becomes an alarm.
  • Each agent gets this with its next kit update, through the Steward as usual.

Before you update

  • Nothing: it updates itself as usual. Agents for sale stop appearing in the public releases repository once the Exchequer says which ones are for sale (its 0.6.0).

0.20.1

A refresh after releases cleans up after itself, however deep its packages go.

What changed

  • A refresh's working copy is removed whatever the length of the paths in it. A site's packages go deeper than git on Windows deletes, so its copy could be left behind, and the next refresh would then have failed to start.
  • One left behind by a refresh cut short (the PC turned off mid-run) is cleared before the next refresh.

Before you update

  • Nothing: it updates itself as usual.

0.20.0

A repository can be refreshed after every release: a site that lists your release notes and downloads stays up to date by itself.

What's new

  • Refresh after releases, a new setting for each repository in Settings, under Repositories. Name a command (a site's npm run sync, say), and after the Steward releases anything, it runs that command in a fresh copy of the repository's branch. When the command changed something, the repository's tests run, and only when they all pass is the change committed ("Release notes and downloads after …") and pushed to the branch, never forced. When nothing changed, nothing is pushed. A round that released nothing runs no refresh.
  • A refresh that fails, or whose tests fail, pushes nothing and is an alarm on the Steward's page and in Castellan, until a later refresh goes through.
  • Note, a new setting for each repository: a word shown first on its row of the Steward's page, such as why its pull requests are left to you.

What changed

  • A version kept in a TypeScript constant (export const VERSION = '1.2.3') is read and claimed like one in version: '1.2.3', and Look after finds it.
  • A Next.js project's tests get their own packages in the Steward's worktree, as its build refuses packages linked from elsewhere. Other projects still share theirs.
  • Settings save when a repository has no kit to fill, as one you looked after from the list of repositories found on this PC. Before, its empty "Fill its kit" stopped the save.

Before you update

  • Nothing: it updates itself as usual. Nothing is refreshed until you name a command for a repository.

0.19.5

It hands out the kit 2.34.0: an agent's rounds never stop silently.

What changed

  • An agent waiting for a setting only you can give now says so in its round record each time a round comes due. Before, it went quiet, and looked to the Surveyor like an agent whose rounds had stopped.
  • A round that hangs, waiting on something that never answers, is let go after its time limit (three intervals, and at least two hours), recorded as failed, and tried again at the next round. Before, one hung round stopped every round after it until the agent was restarted.
  • Each agent gets this with its next kit update, through the Steward as usual.

Before you update

  • Nothing: it updates itself as usual.

0.19.3

When GitHub has a bad hour, the Steward waits it out by itself: no alarm, no Push to press.

What changed

  • A push, pull request or release that GitHub answers with its own error ("Internal Server Error", a 502, 503 or 504, a connection it drops) counts like the network being down: the Steward tries it again on its next round, and raises no alarm. Before, each one was set aside until you pressed Push, with an alarm per agent.
  • Any agent still set aside for that reason is let go on the first round after this update, and pushed then.

Before you update

  • Nothing: it updates itself as usual.

0.19.1

It hands out kit 2.32.1: the agents name Castellan, the app you bought.

What changed

  • Kit 2.32.1: an agent with no local AI set up says "open Castellan and choose Set up local AI" (it said Manor), and the agents' other words that send you to the app name Castellan too.
  • The Steward's card in Castellan shows again: its one-line role is shorter ("Looks after your repositories: claims versions, merges your ready pull requests and releases, where you say yes"), within the 120 characters a card takes.

Before you update

  • Nothing: it updates itself as usual.

0.19.0

The Steward looks after your own repositories: the ones Reeve finds, as you say.

What's new

  • Found on this PC. Its page lists your repositories that Reeve finds here, on GitHub, that you can push to. Look after adds one to Settings (now called Repositories) with how to test it and the files that carry its version, read from your clone.
  • Nothing happens without your yes. For each repository you choose whether it merges your ready, green pull requests (Merges your ready PRs) and whether it releases new versions (Release it): with the repository's own npm run release, or as a GitHub release of the branch it makes itself, its notes your CHANGELOG.md entry. Both are off until you tick them, and so is Merges and releases by itself: until you switch that on, nothing is merged or released but by a button.
  • Versions claimed for any repository. claim-version takes any repository: one you look after, one Reeve found here, or the clone you run it in.
  • Merge your ready PRs and Release buttons for your repositories, and a page and Settings that speak of them only.

What changed

  • Every release goes to the repository's own GitHub repository (kit 2.32.0: the releases repository is a setting now, never built in).
  • Kit 2.32.0: an agent's Back to … link, and its tour's, says your manor's name as before, and Back to Castellan when it has none (it said Back to Manor).
  • The kit, its rollout and the Steward's own releases happen only on the PC that releases Castellan itself (Releases Castellan itself, in Settings' advanced part), with their settings shown only there.
  • The Wright's and the Bailiff's settings show, and their work runs, only where the Wright is installed. A pull request labelled wright is anyone's where it isn't.
  • No alarm that the Surveyor's page doesn't answer where the Surveyor isn't installed.
  • Keeping the staff's pages up and the manor-wide alarms are to move to Manor: once Manor says it does them, the Steward leaves them to it.
  • gh is found on PATH only; without it, you're told to install it and run gh auth login. A .NET SDK is taken from Settings (.NET SDK), DOTNET_ROOT or Program Files.
  • allow-update takes a version again (its check was broken).
  • The code that converted the first agents to the kit is out of the release.

Before you update

  • Nothing: it updates itself as usual. A Steward that was already looking after repositories keeps doing all it did: on its first start it writes into its Settings what it used to assume (that this PC releases Castellan itself, where its releases go, that it merges and releases by itself, and that each repository's ready PRs are merged).

0.18.0

It hands out kit 2.31.0: local AI on every Copilot+ NPU (Qualcomm, Intel, AMD), installed by setup.

What's new

  • Kit 2.31.0: setup finds the NPU whatever its maker, installs that maker's model server and models (checked against pinned checksums, for your user, without an administrator), and uses it only once it has answered a test question. Snapdragon gets GenieX, Intel Core Ultra gets OpenVINO Model Server, and AMD Ryzen AI 300 and later get FastFlowLM. An NPU the manor can't use (AMD's Ryzen 7040 and 8040, or an old driver) is named, with the reason, and the graphics card or the processor does its work.
  • The model setup now lives in a folder Manor owns, so the household agents work without Reeve.

What changed

  • Kit 2.31.0: the model keeper stops a leftover model server only when the manor started it or it is in the manor's own folders, never because of the port it uses. Your own GenieX or another program's server is left alone.
  • The "isn't set up" message now sends you to Manor's Set up local AI instead of Reeve.

Before you update

  • Your model setup is copied from Reeve's settings to Manor's folder the first time it is read after the update, word for word; Reeve's file is left as it was. Nothing to do.

0.17.1

It hands out kit 2.30.0: each staff release is published to the Exchequer, Castellan's release service, as well as to GitHub.

What's new

  • Kit 2.30.0: when an agent is released, the same files that go to GitHub also go to the Exchequer (https://api.castellan-software.com), where the PCs that subscribe will download the staff from. Only the agents it sells are published there (never Manor or Heiward), and only from a PC with the publisher's key. GitHub's releases stay where every Manor looks for now.
  • npm run release -- --exchequer in an agent's checkout publishes a release that is already on GitHub to the Exchequer, from GitHub's own files.

What changed

  • A release that reached GitHub but not the Exchequer (no publisher key on this PC, or the Exchequer down or refusing) is still released: the Steward's page shows it as done, with the reason as a note ("Not published to the Exchequer: …"). It is never a failure or an alarm, and never mistaken for the network failing a release.

Before you update

  • Nothing: it updates itself as usual. Each agent takes the new kit as the Steward rolls it out. To publish to the Exchequer, the PC that releases needs the publisher's key in %USERPROFILE%\.steward\exchequer-publisher.key (or EXCHEQUER_PUBLISHER_KEY); without it, releases go to GitHub alone, as before.

0.17.0

A new agent is taken on with one command: employ.

What's new

  • `employ <its clone>` adds a new agent to the Steward's employees, so its page lists it and its rounds test, merge and release it, with no hand-editing of settings.json. Everything comes from the clone: its id and name (from manor-agent.json, or src/app.ts), its GitHub repository, its kit parts, and how to fill, test, version and release it. --dry-run shows what it would add.
  • An agent that announces itself to Manor is published, so every Manor offers Hire for it. Manor's internal staff, and an agent that doesn't announce itself yet, are built and installed on this PC only.
  • An agent the Steward looks after already, or a folder that isn't a clone with a GitHub origin, is refused, with why.

Before you update

  • Nothing: it updates itself as usual.

0.16.1

It hands out kit 2.29.0: every agent's page fits a phone.

What changed

  • On a phone, an agent's title bar no longer runs off the side: its action button (Run now, Check the fingerprints now) moves under the status instead. A wide table scrolls by itself instead of dragging the whole page sideways. This covers the Steward's own page too.
  • Last stage lists what the stage did (merged, released, refused, failed) first, and folds the employees it skipped, with nothing to do, under their count. After a round, most of the 60-odd lines were "skipped".

Before you update

  • Nothing: it updates itself as usual. Each agent takes the new kit as the Steward rolls it out.

0.14.1

It names no folders of one particular PC.

What changed

  • Its entry for Manor (manor-agent.json) no longer names a Node in a folder only one PC has: it runs on Manor's own Node, or one installed in the usual place.

Before you update

  • Nothing: it updates itself as usual.

0.12.6

A security fix: it hands out kit 2.28.1, where a value with curly quotes can no longer break out of a PowerShell string.

What changed

  • Kit 2.28.1: Windows PowerShell treats the curly quotes ‘ ’ ‚ ‛ as quote marks, and the kit's quoting only escaped the plain one, so a file or folder name with curly quotes in it, handed to PowerShell by an agent, could be read as a command. Every quote mark is escaped now, and each agent is fixed as it takes the new kit.

Before you update

  • Nothing: it updates itself as usual. Each agent takes the new kit as the Steward rolls it out.

0.12.3

It hands out kit 2.28.0: an agent that needs a setting from you waits for it, and its tour asks for it.

What's new

  • Kit 2.28.0: each agent can name the settings it can't work without (the Chamberlain needs a mail account). Until you fill them in, its rounds wait, its page says Waiting for its settings with a Fill them in button, its status says Needs settings, and the first-hire tour won't move past its settings step until they're saved.

Before you update

  • Nothing: it updates itself as usual. Each agent takes the new kit as the Steward rolls it out.

0.12.2

A tour of the Steward's page when you hire it.

What's new

  • When you hire the Steward from Manor, Take the tour walks you through it in three steps: what it does, the three settings only you can choose (whose pull requests it merges, whether it merges and releases by itself, and whether it reopens an agent's page that stopped answering), and its page, part by part. You can take it again any time from its page at #/tour.

Before you update

  • Nothing: it updates itself as usual.

0.12.1

What changed

  • Every agent names the NPU, each graphics card and the processor from what Windows calls them, as Manor shows them: by the model alone, without (R), (TM) or a last "NPU", "CPU" or "GPU": "Qualcomm Hexagon", "Qualcomm Oryon", "Qualcomm Adreno X2-90". A name written in Reeve's config.json is no longer used, and is taken out the next time the file is saved.
  • Nothing else on the Steward's own page: it hands the new kit to every agent.

Before you update

  • Nothing: it updates itself as usual.

0.12.0

The Steward now keeps the rest of the staff up and answering, with or without repositories to look after.

What's new

  • The staff's pages are kept up. No one did this before. In every round, whether or not the Steward has repositories to look after, an agent that is on duty but whose page has stopped answering (it crashed, or an update left it down, so its rounds aren't running) has its page opened again through Manor, as Manor's own Open button would. It gets three tries, five minutes apart, then one an hour. If it still doesn't come back, or Manor can't open it, an alarm says so until it answers. An agent you stopped stays stopped: the Steward never changes anyone's duty, and leaves alone the agents Manor keeps off duty for Developer options.
  • The page has a new section, The staff's pages, listing any agent that's down and the ones lately opened again.
  • A new setting, Keeps the staff's pages up, is on by default. It needs only Manor's page (Settings, Alarms).

What changed

  • No repositories, no GitHub. On a PC where none of the Steward's employees has a clone, and it has no checkout of its own, a round no longer asks GitHub anything. Before, it sent an empty query every round and logged that it had no team. Now keeping the staff's pages up and raising the alarms is the whole round. The page says that's what it is doing and leaves out the kit's stage buttons until you add an employee. Its kit card reads The kit the Steward manages, since there's no one to hand the kit to: the Steward keeps it only to run on.
  • With Merges and releases by itself off, rounds still come on duty to keep the staff's pages up, but they do nothing on GitHub. Run now still does a whole round.
  • If there are no repositories and Keeps the staff's pages up is off, the page says the Steward has nothing to do, and what to add.

Before you update

  • Nothing: it updates itself as usual. Agents on duty whose pages are down are opened again within a round of updating. If you'd rather keep an agent's page down, stop it in Manor (off duty), or switch off Keeps the staff's pages up in the Steward's Settings.

0.11.13

A release that "failed" but is out anyway stops being reported as failed.

What changed

  • When releasing an agent failed in a round, the Steward stopped trying that commit and raised an alarm until someone released it. If the version was in fact published (a retry, or another run that got there first: on 2026-10-06 Reeve 0.6.5 was published, then the round's own attempt found it there and failed), the alarm and the hold stayed, because only a release made by the round cleared them. Now a round that finds the version already released clears its failure too.

Before you update

  • Nothing: it updates itself as usual. Reeve's "release failed at f2e18a8" clears at the first round after the update.

0.11.12

One alarm while the Bailiff can't review, not one more for each Wright PR waiting on it.

What changed

  • While the Bailiff's page doesn't answer, or the Bailiff can't use Claude Code, the Wright's drafts that wait only for its review used to each raise their own "has waited 24 hours" alarm on top of the Bailiff's. Now the Bailiff's alarm lists them ("The Wright's drafts waiting on it: …") and they raise nothing of their own. A draft held for another reason (the Steward's own look, or the Bailiff asking for changes) still has its own alarm. Once the Bailiff reviews again, everything is as before.

Before you update

  • Nothing: it updates itself as usual.

0.11.11

Without the Wright and the Bailiff, the manor keeps itself running but takes on no new work.

What changed

  • New work needs both. The Wright's pull requests are marked ready and merged only after the Bailiff approves them. Before, with no Bailiff on this PC, the Steward's own quick look was enough for a Wright PR to merge. Now it stays a draft and says so: review it yourself and mark it ready, or hire the Bailiff.
  • A removed agent stays removed. If an employee's install folder is gone (it was fired in Manor, or uninstalled), the Steward still looks after its code and kit, but no longer installs it again: not after a merge, and not through a release built on this PC (which installs it). Before, the next kit rollout quietly put the Wright or the Bailiff back. Hire it in Manor to bring it back.
  • No Wright on this PC: work waits for you, and the alarm says so. A failed bump or release is no longer described as "the Wright's page isn't set". The alarm now says the Wright isn't on this PC. Work already filed for a Wright that's since been removed no longer holds its alarm back for a day, since nobody is working on it.
  • No stale "down" alarms. The Wright's and the Bailiff's pages are read only while they're installed, even if Settings still name them, so a removed one can't show as down forever.
  • Everything else carries on without them as before: rounds, merging the team's and the Steward's own PRs, releases, kit rollouts, installs and alarms.

Before you update

  • Nothing: it updates itself as usual. With both the Wright and the Bailiff installed, nothing changes. Without the Bailiff, any open Wright drafts wait for you.

0.11.10

When the Steward copies your employees into Settings and can't find something, it keeps looking and fills it in itself.

What changed

  • When the Steward first copied its employees into Settings, it read what each needs (the command that fills its kit, its tests, its version files, how it's released) from that employee's folder on this PC, as the folder happened to be checked out. A folder left on an old branch looked like it was missing things, so you got an alarm such as "Manor: couldn't tell Fill its kit from its clone" that didn't say what to fill in and only cleared once you saved Settings. Now the Steward reads each employee's main branch (the branch the Steward works from), whatever the folder is checked out on.
  • Until you save Settings, the Steward looks again every few minutes and fills in whatever it now finds. The alarm drops each item it fills, clears once nothing is left, and puts an employee that was left off the kit's stages back on once it has a test command and a release command.
  • The alarm now says what it looked for (for the kit, tools/kit.ts or tools/kit.ps1), on which branch, and that you don't need to do anything if the Steward can find it.

Before you update

  • Nothing: it updates itself as usual. If you have this alarm open, it clears by itself within a few minutes of updating, provided the item is on the employee's main branch. You can still fill it in under Settings, Employees, and save.
  • This release also brings 0.11.9 (below): it wasn't released on its own.

0.11.9

Work for the Wright is filed in a repository that doesn't have the Wright's label yet.

What changed

  • The Steward files work for the Wright as issues carrying the Wright's queue label (manor:work). In a repository that had never had work filed before, such as an agent just added as an employee, GitHub refused the issue because the label didn't exist yet. The alarm then said the work wasn't handed to the Wright, and someone had to create the label by hand. Now the Steward creates the label itself, with the same color and description the other repositories have, and files the issue again. Its log says when it did.

Before you update

  • Nothing: it updates itself as usual.