Skip to content
Castellan

All release notes

Castellan: release notes

Each version, newest first.

0.16.4

The welcome asks one question, then hires the staff for it.

What's new

  • The first time you open Castellan, the welcome asks what this PC is mostly for: Gaming, Software development or Everyday use. Pick one: it's only a starting point.
  • The next screen lists the agents for that use, already ticked. Untick any you don't want, or tick others.
  • A last screen follows the hiring, agent by agent, until everyone is in. You can close it at any time and the hiring carries on.
  • New hires start set up for the use you chose. The Herald, for one, starts as the Gamer on a gaming PC, and with general news, the weather and stocks otherwise. You can change it in its Settings whenever you like.
  • Castellan's setup asks the same question, as one choice, and the staff it hires start set up for it too.

What changed

  • The welcome's five ticked uses (Everyday use, Gaming, Photos and videos, Documents and mail, Writing software) are now three, with one chosen. The agents for photos, videos and papers come with Everyday use.
  • The hire and Employee management popups no longer tag an agent with the variant it runs as (the Herald's "Runs as Gamer"). Its card's details still say which one runs.

Before you update

  • Nothing: it updates itself as usual. An agent you have already hired keeps its own settings.

0.16.3

A demo manor, for showing Castellan without showing your own.

What's new

  • MANOR_DEMO=1 manor serve opens a made-up manor at castellan.localhost:18575: Oakfield Manor on a PC called STUDY-PC, with every role held, a few agents at work, one finding from the Surveyor and a Workshop licence. It's for screenshots and for showing the product.
  • The demo has its own folder in the temp folder and its own port. It asks no agent and nothing online, and never reads or changes your own manor or your agents. Its buttons change nothing, apart from the theme.

What changed

  • In the hire and Employee management popups, an agent's Employed here badge is green, instead of grey as if it were switched off.

Before you update

  • Nothing: it updates itself as usual.

0.16.1

The buttons on a role card are all the same height.

What changed

  • On every role card, Start and Stop are now the same size as Open, Update, Hire and Employee management, so the row of buttons lines up instead of two standing taller than the rest. Buttons across the page keep one height whether they open a page or do something.

Before you update

  • Nothing: it updates itself as usual.

0.15.7

Your own agents can be hired from their role cards, the first time too.

What's new

  • An agent that is yours alone (on this PC, built by the Steward from its clone) now shows Hire on its role card and in the hire popup when it isn't installed yet. Hire asks the Steward to build and install it, and the page follows the install as for any hire. Before, its first install was a command run by hand.

What changed

  • It is offered only where the Steward is installed and looks after that agent; once installed, the Steward keeps it up to date, as before.

Before you update

  • Update the Steward to 0.27.2 or later first: Hire asks it for the install.

0.15.6

The setup shows Castellan's licence terms, and installs once you accept them.

What's new

  • Setting Castellan up now shows its licence terms (the EULA) right after the welcome. Next waits until you tick I accept the licence terms. They're the same terms as on castellan-software.com/terms.
  • From a terminal, the setup asks you to accept them before it installs anything. setup.exe terms shows them, and --accept-terms accepts them for an unattended setup. With --yes alone, nothing is installed.

Before you update

  • Nothing: it updates itself as usual. The terms are asked only when you run the setup.

0.15.5

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

Uninstalling frees your licence's place, Settings says plainly where your backups are, and installs are followed right on Windows in any language.

What changed

  • Uninstalling Castellan without keeping its data now gives this PC's place on your licence back first, so another PC can use it. If the licence service can't be reached, the uninstall says so and carries on; another PC can free the place later from Settings > Licence.
  • Settings shows the full path of the folder your settings backups go to until you choose one: on this PC only, in a folder OneDrive never copies.
  • Moving old backups out of Documents\Manor backups is more careful: one copied to another drive is checked byte for byte before the old one is removed, and one that can't be moved stays where it was and is tried again the next time Castellan starts.
  • Castellan reads whether an install is running from Task Scheduler's own state, not from the English word "Running", so updates and hiring are followed the same way on Windows in any language.

Before you update

  • Nothing: it updates itself as usual. Your settings backups go to Castellan\Backups in your local app data, on this PC only (Settings shows the full path), unless you chose a folder in Back up to, which is kept. Backups still in Documents\Manor backups move there by themselves.

0.15.3

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

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

Your settings backups stay on this PC unless you choose otherwise.

What changed

  • Settings backups now go to %LOCALAPPDATA%\Castellan\Backups, a folder on this PC that OneDrive never syncs. Before, they went to Documents\Manor backups, which OneDrive often copies to the cloud.
  • Backups already in Documents\Manor backups move to the new folder by themselves, once, and the old folder goes when it's empty. Anything else in it is left alone.
  • If you chose a folder in Settings (Back up to), nothing changes: your backups keep going there.

Before you update

  • Nothing: it updates itself as usual. If you'd like your backups to outlive this PC, choose a folder on another drive, or one OneDrive keeps, in Back up to.

0.15.0

Testers can hire the employees still being developed, marked unstable.

What's new

  • A new switch in Settings, Developer options: Allow hiring unstable employees. Hover it to see what it means: employees still being developed and tested, which may not work fully on every PC yet. It's off unless you switch it on.
  • With it on, the Steward, the Aletaster and the Developer Herald can be hired like any other employee: from their role cards with Hire, in the hire popup, and in the welcome. Each is marked Unstable, and hovering the mark says why. Being developer employees, they're offered while Developer options are on.
  • The Auditor still isn't a separate hire: it comes with the local AI's upkeep.

What changed

  • Switching it off only stops offering them: an unstable employee you've already hired stays, and is updated as usual.
  • The welcome lists an unstable employee, marked so, but never ticks it for you.
  • Castellan's setup still never carries unstable employees: hire them from the page.
  • This release also brings 0.14.0, never released on its own: Castellan's licences (its notes are below).

Before you update

  • Nothing: it updates itself as usual.

0.14.0

Castellan's licences: the staff come from the Exchequer, Castellan's release service; Settings > Licence signs a PC in; and the Freehold promise keeps what you have.

What's new

  • Settings > Licence: what this PC holds (none; the 7-day trial and its days left; Household or Workshop and "updates until"; "updates paused since", with Subscribe again), Sign in with the email you bought with, Enter a key, Start the 7-day trial, Manage subscription, Subscribe (Household $4 a month or $36 a year, Workshop $8 a month or $72 a year) and Give this PC's place back.
  • Sign in with the email you bought with: type the email, Send the code, and enter the six-digit code that arrives (it works for 10 minutes). No key to find or copy. A key still works, just below.
  • Licence keys read CASTELLAN-XXXXX-XXXXX-XXXXX-XXXXX. A key that starts MANOR- is the same key and still works.
  • When a licence is on all its PCs, Licence names them, and a PC that's gone can give its place back from here: by email, with no key, or with the key. A licence can do that 3 times in 30 days; past that, Licence says the day it can again.
  • The Freehold licence: stop paying and keep what you have. Everything installed keeps working, without new versions, and nothing checks the licence to run. Only a trial's end puts its agents off duty, their settings and data kept, and a key brings them straight back.
  • Hire cards say an agent's tier, and offer Subscribe (or Start the trial) when the licence doesn't cover it. An agent you've hired is never touched. An agent marked Coming later isn't for sale yet, and isn't offered.
  • Updates say honestly when a newer release is out than your licence covers ("0.5.2 is out. Your updates paused on …: subscribe again to get it."), and never offer it.

What changed

  • The staff's releases come from the Exchequer, checked against their SHA-256 as ever, and never from GitHub. Castellan's own updates and Heiward's stay on GitHub, free. When GitHub can't be read for a while, the staff's updates still come.
  • Castellan's setup carries Castellan, Heiward and Node only: the staff are hired afterwards, with a licence or the trial.

Before you update

  • Sign this PC in after updating: Settings > Licence, Sign in with the email you bought with (or enter your key, or start the 7-day trial). Until it holds a licence, the staff you have keep working as they are, but their updates and new hires wait.
  • Otherwise it updates itself as usual.

0.13.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.13.3

Role cards line up and say only what the green dot doesn't, and the welcome greets your manor by its name.

What changed

  • A role card no longer has an "On duty." line: the green dot says that. When an agent's status says more ("2 documents and 0 messages indexed"), that part still shows.
  • Every role card is at least as tall as a held one with a status line, so the cards of a row line up whether or not their agent has something to say.
  • The welcome says "Welcome to your manor" until you've named it, and then its name: "Welcome to Smith Estates manor!" (a name that already ends in Manor isn't said twice: "Welcome to Weasel Manor!").

Before you update

  • Nothing: it updates itself as usual.

0.13.2

Updating Castellan no longer stumbles when its "Installing an update" page lets go of the address at just the wrong moment.

What changed

  • While Castellan updates itself, an "Installing an update" page holds its address until the new page is ready to take it. If that page let go in the very instant the new page was checking who held the address, the new page could give up and leave the address silent. It now tries once more and takes it.

Before you update

  • Nothing: it updates itself as usual.

0.13.1

The developer roles' cards describe what those agents now do for your own repositories.

What changed

  • The Aletaster's card says it tastes the releases of your own repositories, the ones you pick from those Reeve finds on this PC.
  • The Developer Herald's card says it follows the projects you build on, and suggests what to follow from your own projects' dependencies.
  • The Steward's card, and its place on the About page's household, say it looks after your own repositories: it claims each new version before the work starts, merges your ready pull requests and releases new versions, each only where you say yes.
  • The Auditor's card says it checks that the local AI's models still answer right on every accelerator (the NPU, each graphics card, the CPU) after a driver, server or model change.
  • The Auditor is part of the local AI's upkeep rather than a separate hire, so where it isn't installed its office no longer says "Coming later": it says there's nothing to hire for it. Where it's installed already, it's kept up to date as before.
  • If you're updating from 0.12.0, this release also brings 0.13.0 (below): setting up local AI on this PC from the welcome.

Before you update

  • Nothing: it updates itself as usual.

0.13.0

What's new

  • Set up local AI on this PC, a step of the welcome: it says what this PC's NPU is and which model server runs on it (GenieX on a Snapdragon, OpenVINO Model Server on an Intel Core Ultra, FastFlowLM on an AMD Ryzen AI 300 and later), how much it downloads, and sets it up when you say so: the NPU first, then the graphics card, then the processor. Everything is checked against pinned checksums, installed for you without an administrator, and the NPU is used only once it has answered a test question. It carries on if you move on through the welcome.
  • 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.

What changed

  • The model setup lives in Castellan's folder (%USERPROFILE%\.manor\accelerators\config.json), so the household agents work without Reeve. It is copied from Reeve's settings the first time it is read; Reeve's file is left as it was.
  • The Steward's kit 2.31.0: a leftover model server is stopped only when the manor started it or it's in the manor's own folders, never for the port it uses.
  • The Steward's kit 2.29.0: the title bar's action and wide tables no longer push the page sideways in a narrow window.
  • The Steward's kit 2.32.0: an agent's "Back to" link says Castellan when your manor has no name of its own.

Before you update

  • Nothing to do. The welcome's new step shows when you open it again from Settings.

0.12.0

Castellan keeps your staff answering and tells you what needs you, on every PC.

What's new

  • Your staff are kept answering. When an agent that's on duty stops answering (it crashed, or an update or sign-in didn't bring it back), Castellan opens its page again by itself, and its card says so for a day. It tries three times, five minutes apart, then once an hour, and tells you under Needs you if it still can't. An agent you stopped stays stopped.
  • Needs you is Castellan's own. It lists what needs you across the manor: an agent that can't be brought back, an update Castellan can't read, two agents' pages on one port (or another program on an agent's port), a problem the Surveyor has found, Reeve's alerts, and anything an agent says is waiting for you, such as the Lamplighter's guard needing an update. Each has a link to that agent's page, where its button is.
  • Windows notifications for each new item, following your Notify me setting and quiet hours. One that comes up during the quiet hours is told when they end, if it's still there. Clicking a notification opens Needs you.

What changed

  • When the Lamplighter's guard can't be turned off because Windows' administrator prompt was declined, you're told just what to do (fire it again, or run Uninstall again, and approve the prompt), with no commands to type. The page no longer asks you to run a command when Castellan isn't answering, either: it says to open Castellan from the Start menu.
  • The uninstall no longer shows a command for removing an agent that was on this PC before Castellan: it says to fire it from its card first, or remove it the way it was installed.
  • Where the Steward is also installed, it leaves keeping the staff answering and these alarms to Castellan (from the Steward's next version); an older Steward goes on as before, and you aren't notified twice.

Before you update

  • Nothing: it updates itself as usual.

0.11.0

Castellan keeps your manor: the product has its name, and uninstalling it removes only what it installed.

What's new

  • What you see is called Castellan: the setup's window, the Start menu and desktop shortcuts, the entry in Settings > Apps, and the page's title and heading until you give your manor a name of its own (a name you've set still shows). Your agents are still your manor's household.
  • The page also answers at http://castellan.localhost:18585/, and the shortcuts and links open it there. The old address, manor.localhost, keeps working, and so do each agent's links back to the page.
  • The setup's download is now called Castellan-Setup-<version>-arm64.exe (or -x64.exe).

What changed

  • Uninstalling Castellan from Settings > Apps removes only the agents it installed. A Reeve or a Heiward you had before Castellan stays installed with its data, and the uninstall says so and how to remove it yourself. Castellan now notes which agents it installed and which it found already there; on a PC set up before this version, an agent whose folder is older than Castellan's own counts as yours.
  • Before the Lamplighter is let go (fired from its card, or by the uninstall), its guard, which runs with administrator rights, is turned off first: Windows asks for an administrator once. If you turn that prompt down, the Lamplighter stays installed, its guard stays on, and you're told how to turn it off; the uninstall can be run again from Settings > Apps.
  • Removing your data on uninstall now deletes Castellan's folder only when it really is Castellan's: never your user folder, a drive, or one of Windows' own folders, even if Castellan was pointed at one.

Before you update

  • On this update, the Start menu and desktop shortcuts and the Settings > Apps entry are renamed Castellan, in place of Manor. Nothing else moves: your settings, your agents and their data stay where they are.
  • The page also answers at castellan.localhost: update a bookmark if you like, though manor.localhost still works.

0.9.5

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

What changed

  • The Steward's kit 2.28.1: Security fix: a value with curly quotes in it could break out of a PowerShell string.

Before you update

  • Nothing: it updates itself as usual.

0.9.4

Four agents wait until they're useful on every PC, and a manor's own banners live in its own folder.

What changed

  • The Steward, the Aletaster, the Developer Herald and the Auditor are held back for now: today they only help with their developer's own projects. They're no longer offered for hire, the setup doesn't carry them, and an office only they could hold says Coming later. Where a general agent can hold the office (the Herald, the Reckoner, the Weigher), it's offered as before.
  • Where one of them is installed already, nothing changes: it keeps working, and its updates come as before.
  • A manor's own banners and tab icons are kept in Manor's data folder (%USERPROFILE%\.manor\art\...), named in settings.json as art/...; only .svg files inside that art folder are taken. Its own environments, for manor install --environment <name>, are kept there too (%USERPROFILE%\.manor\environments\<name>). Manor's release no longer carries any manor's own art or environment.
  • Manor's settings backups now include those banners and environments.
  • The staff no longer look for Node, or the GitHub CLI, in a folder only one PC has: Manor's own Node and the usual install folders.

Before you update

  • Nothing to do. If your manor's own banners were kept in Manor's program folder, this update copies them, and your own environments, into %USERPROFILE%\.manor by itself before it replaces the program folder, and the banner switch keeps working.

0.9.2

A security fix in Manor's setup: a folder name with curly quotes in it can no longer break out of its PowerShell commands.

What changed

  • Windows PowerShell treats the curly quotes ‘ ’ ‚ ‛ as quote marks. Manor's setup (making its shortcuts, and the clean-up after an uninstall) now escapes every one of them, so a folder like C:\Users\O’Brien stays a name and is never read as a command.

Before you update

  • Nothing: it updates itself as usual.

0.8.1

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

What changed

  • The Steward's kit 2.28.0: Required settings: an agent that can't work without something from you waits for it, and onboarding asks for it.

Before you update

  • Nothing: it updates itself as usual.

0.8.0

A welcome for a new manor: say how you use this PC, and choose your first staff from the agents that suit it.

What's new

  • The setup asks how you use this PC (Everyday use, Gaming, Photos and videos, Documents and mail, Writing software) and suggests its first staff from that. Each agent shows its name, its office, what it does in a line, and whether it works on its own or works with you. The ones that suit you are ticked, you change any, and the setup hires them along with Manor. Writing software also turns on Developer options.
  • A welcome the first time you open Manor: what Manor is, how the work goes, where Settings are, and, if nobody was hired during setup, the same "How do you use this PC?" and your first hires. It's in Settings any time.
  • Every agent says what it is and how it works: a category (Storage, News, Security…) and a Works on its own mark (circling arrows) or a Works with you mark (a person) on its card, in the hire popup and in the welcome.
  • An agent that can't start without a setting says so. Its card shows Waiting for its settings, with Fill them in, which opens its page right at that step. The agents themselves say so from the Steward's kit 2.28.0 on.
  • The Chamberlain, Thatcher, Reckoner, Weigher and Shepherd are part of Manor's own staff now, so the setup carries them too, and can hire them without the internet.

What changed

  • manor install takes --developer-options on|off, and Manor's setup takes --hire=<id>,... and --developer-options=on|off, for the same choices from a terminal.

Before you update

  • Nothing: it updates itself as usual. An existing manor isn't shown the hiring steps; its welcome opens once, and Skip closes it for good.

0.7.0

Manor's page is drawn with React, the way the agents' pages are, and looks and works as it did.

What changed

  • The whole page (the manor, Settings and About) is rebuilt in React on the Steward's kit's page parts. Every section, card, button and setting is where it was, and does what it did.
  • The manor's settings form is the same one the agents' pages use, so it behaves as theirs do.

Before you update

  • Nothing: it updates itself as usual. If a tab still shows the old page after the update, reload it.

0.6.19

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

What changed

  • The Steward's kit 2.27.0: An accelerator's name is what the PC calls it, never a setting.

Before you update

  • Nothing: it updates itself as usual.

0.6.18

This PC shows the memory on its own line, with its type and speed.

What changed

  • Memory has its own line again on This PC, now with its type and speed: "48 GB · LPDDR5 · 9523 MT/s". Windows reports LPDDR5X memory as LPDDR5.
  • Physical cores and Virtual cores have their line to themselves.

Before you update

  • Nothing: it updates itself as usual.

0.6.17

This PC shows physical and virtual cores, and each accelerator on its own line.

What changed

  • This PC now shows Physical cores and Virtual cores side by side, with Memory beside them. Until Windows has said how many cores are physical, only the virtual ones are shown.
  • Each accelerator on This PC is on a line of its own.

Before you update

  • Nothing: it updates itself as usual.

0.6.16

Shorter names for the NPU, the processor and the graphics card.

What changed

  • On a Snapdragon PC, the NPU and the processor now go by their model alone: "Qualcomm Hexagon" and "Qualcomm Oryon", instead of the whole "Snapdragon X2 Elite Extreme - X2E94100 - …" name.
  • A name no longer ends in "NPU", "CPU" or "GPU", since the badge beside it says which it is. A graphics card is "Qualcomm Adreno X2-90", for example.
  • On the This PC card, each accelerator has its type in brackets: "Qualcomm Hexagon (NPU)".

Before you update

  • Nothing: it updates itself as usual.

0.6.15

The processor's badge says CPU.

What changed

  • On the processor's card in the Accelerators section, the type badge now says CPU instead of "Processor", matching NPU and GPU.

Before you update

  • Nothing: it updates itself as usual.

0.6.14

A graphics card's badge says GPU.

What changed

  • On a graphics card's card in the Accelerators section, the type badge now says GPU instead of "Graphics card".

Before you update

  • Nothing: it updates itself as usual.

0.6.13

Graphics cards go by their real names.

What changed

  • A graphics card is now shown by the name Windows gives it, such as "Qualcomm Adreno X2-90 GPU". Before, a card that Reeve's settings didn't list was shown by an internal ID, like "Graphics card (qualcomm-r-adreno-tm-x2-90-gpu)", and one they did list could go by a name saved there.

Before you update

  • Nothing: it updates itself as usual.

0.6.12

Tidier accelerator and This PC cards, and fewer buttons on the role cards.

What changed

  • Each accelerator's card now shows its name first, then its type and whether it's free, with a line beneath. Under the line is who has it, and Up next appears only when something is waiting.
  • This PC shows Cores and Memory side by side on one line. Manor's own version is no longer listed there, since Updates shows it just above.
  • Updates no longer lists new agents you could hire. Before, they stayed there for good if you chose not to hire them.
  • Role cards no longer have their own Hire or Install button for a particular agent. Choose that agent in Employee management instead. A vacant role keeps its one Hire button.
  • The Wright's and the Bailiff's cards now show their version, with Update automatically always on: the Steward builds and installs each new version as soon as it's merged.

Before you update

  • Nothing: it updates itself as usual.

0.6.11

The NPU always goes by its real name.

What changed

  • The NPU is now always shown by the name Windows gives it, even when the accelerator settings call it something else. Before, a name saved in those settings was shown instead.

Before you update

  • Nothing: it updates itself as usual.

0.6.10

The NPU's card shows the NPU's real name.

What changed

  • The NPU's card in the Accelerators section, the PC's description and manor status now show the NPU's name as Windows and Task Manager give it, such as "Snapdragon X2 Elite Extreme - X2E94100 - Qualcomm Hexagon NPU", instead of "The NPU". If you've given the NPU a name in Reeve's settings, that name is still used.

Before you update

  • Nothing: it updates itself as usual.

0.6.9

On a PC without an NPU, the graphics card shows in its place; and hiring, switching and firing an employee each have their own window.

What's new

  • Hire is now one button on each vacant role's card. It opens a window that lists everyone who could hold the role. Choose one to see their entry beside the list, set out like a page from an old book: their name, whether they're the general or the developer variant and what that means, what they specialize in, what they do, and the history of the office.
  • Employee management on every card with someone in the role opens a window where you can switch to another agent for that role, or fire the current one and leave the role vacant. A switch to an agent that isn't hired yet hires them first. Once they're installed, they take over the role and the previous holder is fired. If the hire fails, nothing changes.

What changed

  • On a PC without an NPU, the Accelerators section shows your graphics card, marked In place of the NPU, even before Reeve is set up. Before, the section could be missing altogether. Manor now checks once a day what hardware the PC has, so it knows whether there's an NPU.
  • Firing an employee now leaves its role vacant, and the next agent you hire for that role takes it up. Before, the role could stay assigned to the agent that had left.
  • Fire has moved from the expanded card into Employee management.

Before you update

  • Nothing: it updates itself as usual.

0.6.8

Manor's own list of staff names only the agents anyone can hire.

What changed

  • Agents that are private to one PC are no longer in the staff and roles Manor ships. Each PC lists its own in staff.local.json in Manor's folder, which Manor reads beside its own lists and an update never touches.

Before you update

  • Nothing: it updates itself as usual.

0.6.7

Manor's page no longer says Manor isn't answering when it is.

What changed

  • Manor's page could show "Manor isn't answering, so this page can't update" and stop updating, even though Manor was running and a refresh didn't help. The cause was a fault in the page itself: the clock used for quiet-hours notifications had the same name as the clock used for update times, so the update times failed to draw and the page took that as Manor not answering. They each have their own name now.
  • The same fault made "Last survey" under Repairs read "Invalid Date". It shows the time again.
  • If the page ever fails to draw what Manor tells it, it now says so ("Manor is running, but this page couldn't draw what it said …") instead of saying Manor isn't answering.

Before you update

  • Nothing: it updates itself as usual. Reload any open Manor tab once it has updated.

0.6.5

It carries the Steward's kit 2.26.0, and still keeps Manor's own repository out of the projects list.

What changed

  • The Steward's kit 2.26.0: the kit names no one's GitHub account, private repository or folder. This release brings the kit that 0.6.4 was meant to bring; 0.6.4 was never released on its own.
  • Settings' projects still refuse Manor's own repository. Manor now learns which one that is from this PC: the Steward's entry for Manor, or, when Manor runs from a clone, that clone's origin. The Steward's other employees are refused as before.

Before you update

  • Nothing: it updates itself as usual.

0.6.3

Reeve's jobs run as soon as an update is installed, without a "Needs approval" wait.

What changed

  • When an update changed one of Reeve's job scripts, the job showed "Needs approval" on Reeve's page until the Steward's next round approved it, up to ten minutes later. Manor now asks the Steward to approve right after it installs an update, and the install's log says what the Steward answered. The Steward still approves only a script that is exactly the one merged on Reeve's main.

Before you update

  • Nothing: it updates itself as usual. It takes effect once the Steward is at 0.11.5 or later; until then, the Steward's rounds approve the jobs as before.