v0.4.5

Added

• A node now runs a bounded number of stages at once, derived from its CPU count, queuing the rest instead of oversubscribing. (#210)
• The stage-concurrency bound is tunable with the DAHRK_MAX_CONCURRENT_STAGES environment variable. (#210)
• A node's health report now shows its stage capacity and how many slots are in use. (#210)
• A run can check out several repositories side by side, so one stage can change both. (#201)
• A run's worktree can be browsed from the portal while the run is in flight or waiting at a gate. (#211)

Changed

• A run's worktrees now sit in a directory of their own, one level deeper than before. (#201)
• A command that changes directory into a read-only location, such as /etc or /usr, is now refused. (#201)

Fixed

• A batch stage is no longer cancelled while its runtime is still working through a long turn. (#206)
• A process a check or setup command backgrounds during a stage is now killed when the stage settles, instead of outliving the node. (#205)
• Two nodes on one host with distinct DAHRK_STATE_DIR values now get their own service and worktree roots, so neither clobbers the other. (#204)
• A node with no Docker installed now reports as healthy, instead of showing a finding for a tool it never uses. (#203)
• The node health report's all-clear no longer claims a repository was checked, since it examines none. (#203)
• A stage can no longer read files outside its worktree by changing directory first. (#201)
• A node that dies mid-run preserves the uncommitted work in every repository of that run. (#201)
• Each repository of a run runs its own setup command. (#201)
• The installer's instructions now suit a box with no sudo, using su or dropping the privileged route entirely. (#199)
• The apt and dnf recipes are a single command, so a partial paste can no longer install an older distro Node. (#199)
• The installer no longer rejects an npm prefix that is configured but not yet created. (#199)
• Node without npm, the shape Debian's own package leaves you in, is explained instead of being called a broken install. (#199)
• The nvm route says to run it as the user that will run the node, not as root. (#199)