Skip to content

Releases

v0.41.1

Choose a tag to compare

@github-actions github-actions released this 17 Nov 15:31
ffc50db

Features

  • feat(connection): wake the plugin inbox per served fleet (W4) (#82)
  • feat(machines): forward computer setup choices (#85)

Fixes

  • fix(ci): test runs leave no container or volume behind, checked without the reaper (#81)

Other changes

  • Commission computer ships with kind trierarch (#84)

Staging walk

  • Smoke passed 13 of 13 steps and PR #85 passed 4 of 4 on candidate ffc50db. Smoke was run by hand with the same steps after a folder-name clash stopped preparation.
  • The walk page remains on agent-host-1 at /home/thomas/walks/0.41.0-714d01f-walker041/page.html; it was not published as an artifact at Thomas's direction.

v0.41.0

Choose a tag to compare

@github-actions github-actions released this 15 Nov 06:15
2e4f2f7

Other changes

  • A credential's secret never reaches a refusal (Fixes #65) (#79)
  • The join takes the harness and repository options and builds the whole setup line (Fixes #75) (#80)

v0.40.0

Choose a tag to compare

@github-actions github-actions released this 13 Nov 14:30
54f2751

Other changes

  • The README sets the MCP configuration through the console's /api/trierarch-plugin route (Fixes #70) (#71)
  • Placement places a request only where every repository it names is offered (Fixes #73) (#74)
  • A user guide tells how the trierarch plugin crews a fleet's ships (Fixes #77) (#78)

v0.39.2

Choose a tag to compare

@github-actions github-actions released this 09 Nov 13:55
f1983bd

No merged pull request carries the label 0.39.2.

v0.39.0

Choose a tag to compare

@github-actions github-actions released this 08 Nov 15:45
587c030

Other changes

  • The plugin answers a ship asking for the enabled models (Fixes #60) (#66)
  • The trierarch plugin tells a ship why its crew request waits (Fixes #61) (#67)

v0.38.0

Choose a tag to compare

@github-actions github-actions released this 08 Nov 14:00
6ae996c

Other changes

  • Design: ships read the enabled models, the plugin refuses a model not available and tells the requester why (Refs #57) (#58)
  • Placement and the check say model not available (Fixes #59) (#62)
  • The AIP goes to every trierarch with the MCP servers (Fixes #63) (#64)

v0.37.0

Choose a tag to compare

@github-actions github-actions released this 07 Nov 07:25
57b838c

Other changes

  • Binary 11/12: the setup line runs the install script (#46)
  • The release workflow checks and closes its milestone (#48)
  • The MCP server list, sent to every trierarch (#49)
  • Placement leaves out a machine that does not offer every named MCP server (Fixes #43) (#50)
  • The secret store, sealed to every trierarch (#51)
  • Secret store follow-ups: a swapped name and value never reach the log, one warning per refused key (#54)
  • Common 0.38.1: a trierarch stating a sealing key is placed (Fixes #53) (#55)
  • Messages to argo open with a headline line (Fixes #45) (#56)

v0.36.1

Choose a tag to compare

@github-actions github-actions released this 03 Nov 12:14

Other changes

  • Connect declares the plugin's scopes when it succeeds (#41)

v0.36.0

Choose a tag to compare

@github-actions github-actions released this 01 Nov 10:51
9765719

No merged pull request carries the label 0.36.0.

v0.34.0

Choose a tag to compare

@github-actions github-actions released this 30 Oct 13:46
dbf3e09

Other changes

  • docs(decisions): the trierarch plugin keeps usage history (0030) (#25)
  • The trierarch plugin keeps each fleet's usage hours, rolled up per UTC day (usage, slice 1) (#26)
  • The console reads the fleet's token usage from the trierarch plugin (usage, slice 7a) (#27)
  • The Usage page's filter menus read a breakdown's values from the trierarch plugin (usage, slice 7b) (#28)
  • The Usage page reads each machine's subscription windows from the trierarch plugin (usage, slice 7c) (#29)
  • The trierarch plugin keeps and reads the estimated cost of each token kind (usage, slice 7d) (#30)