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.

Installing

  • Castellan installs and updates it by itself. To install it by hand, unpack the zip anywhere and run node src\cli.ts install (Node 22.18 or later). SHA256SUMS.txt lists its SHA-256 (PowerShell: Get-FileHash).

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.

Installing

  • Castellan installs and updates it by itself. To install it by hand, unpack the zip anywhere and run node src\cli.ts install (Node 22.18 or later). SHA256SUMS.txt lists its SHA-256 (PowerShell: Get-FileHash).

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.

Installing

  • Castellan installs and updates it by itself. To install it by hand, unpack the zip anywhere and run node src\cli.ts install (Node 22.18 or later). SHA256SUMS.txt lists its SHA-256 (PowerShell: Get-FileHash).

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.

Installing

  • Castellan installs and updates it by itself. To install it by hand, unpack the zip anywhere and run node src\cli.ts install (Node 22.18 or later). SHA256SUMS.txt lists its SHA-256 (PowerShell: Get-FileHash).

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.

Installing

  • Castellan installs and updates it by itself. To install it by hand, unpack the zip anywhere and run node src\cli.ts install (Node 22.18 or later). SHA256SUMS.txt lists its SHA-256 (PowerShell: Get-FileHash).

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.

Installing

  • Castellan installs and updates it by itself. To install it by hand, unpack the zip anywhere and run node src\cli.ts install (Node 22.18 or later). SHA256SUMS.txt lists its SHA-256 (PowerShell: Get-FileHash).

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.

Installing

  • Castellan installs and updates it by itself. To install it by hand, unpack the zip anywhere and run node src\cli.ts install (Node 22.18 or later). SHA256SUMS.txt lists its SHA-256 (PowerShell: Get-FileHash).

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.

Installing

  • Castellan installs and updates it by itself. To install it by hand, unpack the zip anywhere and run node src\cli.ts install (Node 22.18 or later). SHA256SUMS.txt lists its SHA-256 (PowerShell: Get-FileHash).

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.

Installing

  • Castellan installs and updates it by itself. To install it by hand, unpack the zip anywhere and run node src\cli.ts install (Node 22.18 or later). SHA256SUMS.txt lists its SHA-256 (PowerShell: Get-FileHash).

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.

Installing

  • Castellan installs and updates it by itself. To install it by hand, unpack the zip anywhere and run node src\cli.ts install (Node 22.18 or later). SHA256SUMS.txt lists its SHA-256 (PowerShell: Get-FileHash).

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.

Installing

  • Castellan installs and updates it by itself. To install it by hand, unpack the zip anywhere and run node src\cli.ts install (Node 22.18 or later). SHA256SUMS.txt lists its SHA-256 (PowerShell: Get-FileHash).

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.

Installing

  • Castellan installs and updates it by itself. To install it by hand, unpack the zip anywhere and run node src\cli.ts install (Node 22.18 or later). SHA256SUMS.txt lists its SHA-256 (PowerShell: Get-FileHash).

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.

Installing

  • Castellan installs and updates it by itself. To install it by hand, unpack the zip anywhere and run node src\cli.ts install (Node 22.18 or later). SHA256SUMS.txt lists its SHA-256 (PowerShell: Get-FileHash).

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).

Installing

  • Manor installs and updates it by itself. To install it by hand, unpack the zip anywhere and run node src\cli.ts install (Node 22.18 or later). SHA256SUMS.txt lists its SHA-256 (PowerShell: Get-FileHash).