v0.31.4

The default hubs now track your Peppy version through the new `@{peppy-release}` ref.

Released on September 25, 2026

New installs pin the default hubs with ref: "@{peppy-release}", which reads the peppy-release/<version> tag matching your Peppy version, so their content changes only when you install another version.
Set a git repository's ref to @{peppy-release} in repositories.json5, or pass --ref @{peppy-release} to peppy repo add and peppy repo exclude, to track your version's hub content.
Existing repositories.json5 entries are never rewritten, so a default hub already on main keeps reading main, which can now hold content that only a later Peppy version reads. To follow your Peppy version, set its ref to @{peppy-release}, or delete ~/.peppy/conf/repositories.json5, run peppy repo init to write the default entries again, then run peppy repo refresh.
Before you downgrade to a version earlier than v0.31.4, delete ~/.peppy/conf/repositories.json5 and run peppy repo init with that version: an earlier version cannot read ref: "@{peppy-release}", so it cannot read the default hubs.
After you install a different Peppy version, the daemon reads the @{peppy-release} repositories again at its next start, before it answers any request.
peppy repo list, search, and peppy repo show label a repository on @{peppy-release} with the ref it resolves to, such as reads peppy-release/v0.32.0.