Skip to content

v0.1.3

Choose a tag to compare

@github-actions github-actions released this 11 Sep 00:42
· 262 commits to main since this release

Changes since v0.1.2:

  • 0.1.3
  • docs: web/ ceiling to 14k — every pane is the only implementation of its surface
  • chat: hold an inline code span to copy it, and no ring on a pressed file ref
  • web: palette lists unread and subagent sessions under Running
  • settings: Scope picks from a menu, and offers projects only
  • chat: a preview that cannot load names the path it resolved
  • chat: a code span that names a file opens it, at the line it named
  • chat: a link in a reply carries the body's weight, not prose's bold
  • explorer: the changed-file list is relative to the root asked for
  • test: the tool fakes drop the kind field CatalogEntry no longer has
  • packages: Pi's own failure answers 502, as the routes document
  • files: a directory that is not a checkout unfolds its first level only
  • packages: one built-in test on the web side, no branch for an update the Console never asks for
  • packages: a project switch writes what Pi's own config selector writes
  • packages: the pier package's switches are the SettingsStore, not four callbacks around it
  • files: the Console's pane material, and a directory that is not a repository
  • packages: Browse files opens a package, skill or extension in the Files view
  • tools: rtk's Pi extension moves into ubix post_install / pre_remove hooks
  • agent: seed settings.json on a first boot
  • packages: one Packages tree in the Agent nav
  • packages: rtk is a Tool, and rtk.ts a locked local row
  • packages: Settings → Agent drawn from the registry; the bundled catalog deleted
  • packages: the Console over Pi's package manager, backend
  • docs: Pier is the Console over Pi's package manager
  • search: whitespace splits a query into terms, every one of them required
  • test: one scratch root per run, removed at teardown
  • web: background-run cards carry no Stop; the run page is where a run is stopped
  • settings: default model in Settings → Models; settings.json read-only in the Console

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.