Repository navigation
Releases
Releases · ThomasHendrickx/aeolus-fleet-trierarch
v0.41.0
v0.40.0
No merged pull request carries the label 0.40.0.
v0.39.1
v0.39.0
Features
- feat: a ship works in its ship folder, main/ and sub-repos//, its root files written at every start (#368)
Other changes
- Design: a trierarch keeps the disk its ships use under control (Refs #343) (#344)
- docs(design): disk control slices as issues #346 to #352 (#353)
- Worktrees 3/4: git worktree prune on each configured repository every pass (Closes #91) (#354)
- The container tests remove what an interrupted run left, by a label of their run (Fixes #345) (#355)
- Worktrees 1/4: every path removes the worktree whatever it holds, logged, argo told nothing (Closes #89) (#357)
- Design: a ship folder with a main repository and sub-repositories, approved (Refs aeolus-fleet#1759) (#358)
- Worktrees 2/4: every folder under the root that no crewed ship uses is removed (Closes #90) (#363)
- Worktrees 4/4: a local branch checked out nowhere whose remote branch is gone is deleted (Closes #92) (#365)
- Disk 1/8: a ship's files live in its own folder, ships/, with no secret in it (Fixes #346) (#366)
- Design: one line joins a machine, picking its harnesses and repositories (Refs #373) (#375)
- Design: a session's permission question reaches its owner in the Aeolus app (Refs #374) (#383)
- Join a machine 5/10: aeolus-trierarch is on PATH in every new terminal (Fixes #380) (#388)
- Ship folder 6/7: one link per skill from every repository, and a clash asks the owner (#389)
- Ship folder 7/7: read-only checkouts go, and a configuration naming checkouts is refused (Fixes #362) (#390)
- docs: setup guide for an operator, with diagrams of the parts and the setup flow (Refs #391) (#392)
v0.38.10
No merged pull request carries the label 0.38.10.
v0.38.9
No merged pull request carries the label 0.38.9.
v0.38.8
No merged pull request carries the label 0.38.8.