Skip to content

v0.4.0

Choose a tag to compare

@github-actions github-actions released this 28 Sep 08:17
· 29 commits to main since this release

Changes since v0.3.1:

  • 0.4.0
  • docs: CHANGELOG 0.4.0; README names when a release is minor and when it needs a CHANGELOG entry
  • Changes to package.json
  • Open items read the store, not a listing's window and cap
  • Stamp the users' language on a lead's milestone and on restart resumes
  • tasks: a clipped result keeps its head and tail, in one helper
  • drawer: the rows open the status panel, the counts only word the chip
  • config sync: the contract says what one atomic file replacement and a catchable rollback cover, and that the next sync repairs a process cut between them
  • Resume by session id, one boot order, one owner per saved queue
  • main: requests that land before the boot's unlock wait for it
  • Changes to drawer.test.ts & drawer.ts
  • main: a resumed run's downtime is dated by the stop's turn rows; the doc says who starts a queued row
  • Stop and resume: the stop sequence, the turn resume, the drain removed
  • Open items: one status reading, only 'waiting on you' needs you
  • tasks: the stop's hold on a settling run moves from agent.ts to execution.ts
  • Stop and resume: task runs resume on their own row; pause, drain and SHUTDOWN leave tasks/
  • docs: the updater sentence reads as one clause
  • docs: describe stop and resume behavior
  • Stop and resume: router turn-start and stopping seams, tasks resumeAfterRestart seam, unverified points checked
  • Stop and resume: the restart system-input origin and its text
  • Design: stop and resume — no safe-point wait, unit unchanged, agent runs only
  • Design: stop and resume — systemd owns the restart, Pier the safe point and the resumption
  • Squash commits from lang-stamp-every
  • Squash commits from callback-lang
  • Squash commits from runs-filter
  • Squash commits from approved-callback-state
  • Squash commits from im-abnormal-run-notice
  • Squash commits from badge-tidy
  • Squash commits from model-tier-data
  • Squash commits from run-model-badge
  • Squash commits from goal-dispatcher

pier update stops the service and writes a copy of the database to
~/.pier/db/backups/ before installing. Schema migrations are one-way.
See docs/deploy.md.