Skip to content

Releases: dahrkai/dahrk-node

v0.4.13

Choose a tag to compare

@github-actions github-actions released this 19 Aug 14:41
14bb1c6

Changed

  • This release carries no user-facing changes; it refreshes the published build.

v0.4.12

Choose a tag to compare

@github-actions github-actions released this 19 Aug 07:04
f0187e5

Changed

  • The node now speaks version 0.29.0 of the hub wire protocol. (#235)

v0.4.11

Choose a tag to compare

@github-actions github-actions released this 17 Aug 12:33
fcd794e

Fixed

  • A node running as PID 1, in a container or a microVM, no longer stops at the update prompt. (#233)
  • A confirmation prompt now gives up after a minute and proceeds as if declined. (#233)

v0.4.10

Choose a tag to compare

@github-actions github-actions released this 16 Aug 10:20
02fe2e9

Added

  • A finished stage now reports input, output and cached token counts in its trace metadata alongside the cost figure. (#229)

Changed

  • The always-on service now carries DAHRK_MAX_CONCURRENT_STAGES through from your shell, so a raised stage cap survives a restart. (#230)

v0.4.9

Choose a tag to compare

@github-actions github-actions released this 16 Aug 07:49
26722be

Added

  • A node's heartbeat now reports which stages it is executing, so a brief disconnection no longer risks a running stage. (#225)

Fixed

  • Repository setup no longer blocks the node while it runs, so a long install cannot make a busy node look unresponsive. (#224)
  • A node now declines a remote update while it is running stages, instead of installing one it cannot restart into. (#224)

v0.4.8

Choose a tag to compare

@github-actions github-actions released this 14 Aug 20:53
d1a8b87

Changed

  • A node's heartbeat now counts only stages that are executing as busy, so queued and push work no longer inflate its reported load. (#221)

v0.4.7

Choose a tag to compare

@github-actions github-actions released this 14 Aug 19:45
0b4c399

Fixed

  • A node now tells the hub its stage-concurrency bound, so a multi-core node runs several stages at once instead of being clamped to one. (#219)

v0.4.6

Choose a tag to compare

@github-actions github-actions released this 13 Aug 21:40
fb79635

Changed

  • Setup trace events now report how long the repository setup command took, or how long the cached path saved.

v0.4.5

Choose a tag to compare

@github-actions github-actions released this 12 Aug 06:15
93768a6

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)

v0.4.4

Choose a tag to compare

@github-actions github-actions released this 09 Aug 13:30
9ac3e49

Changed

  • The installer now detects your operating system and prints the exact Node 22 install commands for it. (#196)

Fixed

  • The installer explains an unwritable global npm prefix and how to fix it, instead of failing with EACCES. (#196)
  • A re-run that continues preserved work now starts from that work, and fails loudly rather than silently branching off the base. (#195)