Skip to content
Castellan

All release notes

Assayer: release notes

Each version, newest first.

0.2.5

It carries the Steward's kit 2.45.0: the parts every agent of the manor shares.

What changed

  • The Steward's kit 2.45.0: Each agent Castellan sells checks the trial's end itself, from the license Manor holds.

Before you update

  • Nothing: it updates itself as usual. Manor's own copy of the keys and the license check (its license-keys.ts and license.ts) can move to this kit's license.ts in a later Manor change.

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

It carries the Steward's kit 2.44.0: the parts every agent of the manor shares.

What changed

  • The Steward's kit 2.44.0: A release's notes bring every version merged since the release before; entries can wait in changes/.

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

Faster tests: a branch runs only the tests its change reaches, and your repositories can do the same.

What's new

  • When the Assayer tests one of your branches, or a draft of the Wright's, its unit tests now run only the test files the change reaches, so the run finishes sooner. For node:test it follows the test files' imports, and their imports in turn, so no tags or settings are needed in your repository. For Vitest and Jest it uses their own --changed and --changedSince. Each case on the page says what it ran ("1 of 2 test files: …").
  • Whatever it can't follow runs every test: the TypeScript or npm setup, test fixtures, a file deleted or renamed, or a file no code names. The daily health run and release ready always run everything.
  • Faster tests on a repository: a Node project whose tests run on node:test, Vitest or Jest, and has no test:affected script yet, is offered one. Press Set it up and the Assayer makes a branch, assayer/affected-tests, from the project's branch, tests it, and opens it as a ready pull request for you to merge. For node:test the branch adds scripts/affected-tests.mjs, which needs nothing installed. For Vitest and Jest it adds just the script line. Then npm run test:affected runs only the tests your change reaches, on your PC or in CI.
  • Settings has a switch for it, Test only what a change reaches, on by default.

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

It carries the Steward's kit 2.43.5: the parts every agent of the manor shares.

What changed

  • The Steward's kit 2.43.5: A queue ticket can say what the request is for, and an agent can say it is setting up.

Before you update

  • Nothing: it updates itself as usual.

0.2.1

It carries the Steward's kit 2.43.4: the parts every agent of the manor shares.

What changed

  • The Steward's kit 2.43.4: The kit's MIT license comes with the kit, as src/kit/LICENSE.

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

The Assayer is now the manor's testing specialist: each repository, its test cases, and the tests inside them.

What's new

  • Its page is organized by repository, then test case, then test. Cases are found from each repository's own files: unit tests, typecheck, lint and build from package.json scripts, Python settings (pytest, mypy, ruff), Cargo, .NET, Go and Makefiles, plus a release ready case.
  • Each case shows its tests, read from the test runner's own report (node:test, Vitest, Jest, pytest, dotnet test, cargo test, go test). Every repository, case and test shows its last run, passed or failed, how long it took, its recent history and the failing output. A test that passed and failed on the same commit is marked flaky.
  • Settings › Test cases you set: add a case, change the command of one it found, or turn one off, project by project.
  • Release ready: every 6 hours it checks that each project's versions agree, that every pull request merged since the last release has its changelog line, that the release's checksums match and that CI is green. These are the Aletaster's release checks, and the Assayer now holds the Aletaster's office for developers.
  • What changed: when a case goes from passing to failing, the run names the commits since the last passing run and the tools whose versions changed (Node.js, Python, .NET, Rust and others). It notes the versions of the tools each run used.
  • Put back: when the same commit fails only because a tool changed version, the page offers that tool's last good version, through nvm-windows, pyenv-win, rustup or winget. Nothing changes unless you tick it and press Put back.

What changed

  • A project no longer needs a test command in Manor's Settings: the cases its repository suggests are tested.
  • A branch becomes a pull request only when every case passes, and pull requests, comments and filed issues list each case's result.
  • The daily health run also tests the same commit again when a tool it uses changed version, so a failure caused by the toolchain is told apart from one in the code.
  • The Assayer is for people who write software: it works only while Manor's Developer options are on. With them off, no round runs and its page says so in one line.

Before you update

  • Turn on Developer options in Manor's Settings if they aren't on already: with them off, the Assayer does nothing.
  • Look over the cases it found for each project on its page the first time: a lint or build case you don't want can be turned off in Settings › Test cases you set.

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

Your projects are just projects: the repositories of what you develop.

What changed

  • The Assayer's page and notes call the repositories you list in Manor's Settings your projects, as Manor now does (it called them non-employee projects). What it tests and when is unchanged.

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

It carries the Steward's kit 2.41.0: the parts every agent of the manor shares.

What changed

  • The Steward's kit 2.41.0: A reranker the keeper sets up and keeps: a fourth serve kind, rerank.

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

It carries the Steward's kit 2.40.0: the parts every agent of the manor shares.

What changed

  • The Steward's kit 2.40.0: Settings obey the Developer options switch from the schema alone, and the kit's own parts leak nothing more with it off.

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

It carries the Steward's kit 2.39.0: the parts every agent of the manor shares.

What changed

  • The Steward's kit 2.39.0: Every agent gets Manor's Developer options switch, and the kit's own parts of every page obey it.

Before you update

  • Nothing: it updates itself as usual. On a PC where Manor's Developer options are off, or with no Manor, each agent's Settings page stops showing the settings file's path and the technical lines in Where its work runs. Turn Developer options on in Manor to see them again.

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

It carries the Steward's kit 2.36.1: the parts every agent of the manor shares.

What changed

  • The Steward's kit 2.36.1: GenieX 0.8.0 is the NPU's server on a Snapdragon.

Before you update

  • Nothing: it updates itself as usual. This kit comes after 2.36.0; 2.33.0 (Steward 0.19.4) is still to be released and doesn't depend on it.

0.1.7

Its own page address, so Manor offers it for hire.

What changed

  • Its page moves to http://assayer.localhost:20909/. It had the same port as the Shepherd (20707), and Manor never offers a hire whose port another agent already has: the Assayer's role showed with no one to hire.

Before you update

  • Nothing: it updates itself as usual. A bookmark to its page needs the new address.

0.1.6

It carries the Steward's kit 2.35.0: the parts every agent of the manor shares.

What changed

  • The Steward's kit 2.35.0: A release of an agent Castellan sells goes to the Exchequer, and no longer to the public releases repository.

Before you update

  • Nothing: it updates itself as usual. Agents for sale stop appearing in the public releases repository once the Exchequer 0.6.0 is deployed with its migration applied. Until then, releases go there as before.

0.1.5

It carries the Steward's kit 2.34.0: the parts every agent of the manor shares.

What changed

  • The Steward's kit 2.34.0: An agent's rounds never stop silently.

Before you update

  • Nothing: it updates itself as usual. This kit comes after 2.33.0 (Steward 0.19.4); if 2.33.0 isn't released yet, release it first.

0.1.4

It carries the Steward's kit 2.32.1: the parts every agent of the manor shares.

What changed

  • The Steward's kit 2.32.1: The kit names the app the person bought: Castellan.

Before you update

  • Nothing: it updates itself as usual.

0.1.3

It carries the Steward's kit 2.32.0: the parts every agent of the manor shares.

What changed

  • The Steward's kit 2.32.0: A release goes to the agent's own repository, and to a releases repository only where one is named.

Before you update

  • Nothing: it updates itself as usual.

0.1.2

It carries the Steward's kit 2.31.0: the parts every agent of the manor shares.

What changed

  • The Steward's kit 2.31.0: Local AI on every Copilot+ NPU, installed by setup: Qualcomm Snapdragon, Intel Core Ultra and AMD Ryzen AI.

Before you update

  • The accelerators move from Reeve's config.json to %USERPROFILE%\.manor\accelerators\config.json the first time the Smith (or Reeve's keeper) reads them after updating: a copy, word for word, and Reeve's file is left as it was. Nothing to do.
  • On a PC whose NPU isn't set up yet, the Smith's or Manor's Set up now offers its maker's server and models (several GB) and asks first.

0.1.1

It carries the Steward's kit 2.29.0: the parts every agent of the manor shares.

What changed

  • The Steward's kit 2.29.0: Every agent's page fits a phone: the title bar's action and wide tables no longer push the page sideways.

Before you update

  • Nothing: it updates itself as usual.

0.1.0

The first Assayer: it tests the work in your projects and readies what passes for you.

What's new

  • Your branches. A local branch with commits that aren't on the project's branch, no pull request, and nothing new for a while (2 hours by default) is tested at its newest commit. When it passes, it is pushed (never forced) and opened as a ready pull request, with its commits and the end of the test output. When it fails, nothing is pushed: the page shows the output, and it is tested again once the branch moves.
  • The Wright's drafts. In a project, a draft of the Wright's that the Bailiff approved at its current commit is tested. When it passes, it is marked ready for you with a comment. When it fails, the output goes on the draft and on its issue, and the issue goes back to the Wright once. If it fails a second time, it is labelled wright:needs-you.
  • A daily health run. Once a day it tests each project's branch as GitHub has it. A failure is run again straight away: if the second run passes, the test is called flaky and nothing is filed. If it fails twice, an issue is filed for the Wright (at most 3 a day).
  • Its page, in the manor's page frame: what is ready for you, what didn't pass and the end of its output, each project as the last round saw it, and the recent test runs. Run now, Settings and the theme are in the title bar.
  • A tour. When Manor hires the Assayer it offers its tour: what it does, its jobs, how long a branch is left alone and whether this PC tells you, then its page. Open it again any time at #/tour.
  • Settings: turn each job on or off, how long a branch is left alone before it is tested, and whether a Windows notification tells you when something is ready. How often it looks and when a test run is stopped are under Advanced.
  • Tests run in a throwaway worktree of their own, at below-normal priority: your checkout's working tree is never touched. A Node project uses its checkout's node_modules when the lock files match, so nothing is installed.
  • It never merges, tags or releases anything, and uses no model.

Before you update

  • Nothing to do before the first install. It works in the projects in Manor's Settings that have a GitHub repository and a test command, so add a test command to a project for it to be tested. It needs gh signed in to open pull requests and comment.