Skip to content

0.11.1 — 2026-10-26

Choose a tag to compare

@github-actions github-actions released this 26 Oct 20:11

Release Notes

Added

  • repos in pando init --answers: {"repos": {"members": [...], "base": {"<repository>": "<branch>"}}} writes a multi-repo project's
    [repos], checked against the folder first, so a base only one
    repository has can be answered. A base answer some repositories lack
    is refused naming them.
  • signals publishes env_examples: every env example read, whole,
    under its path.
  • The first-run setup knows a folder of repositories. pando init --agent there says the job is a set of worktrees, that a path names
    its repository first, which repositories it reads no app in, and how a
    repository takes a base of its own; run inside a repository of a
    folder pando already runs, it says so. The brief gains a worked
    example of the shape.
  • pando new of a set that lacks a repository's checkout — lost, or of a
    repository that joined the project since — adds just that checkout,
    leaving the others and their work as they are.
  • pando status lists each repository of a set with its checkout's
    branch, and names a process by its repository: api (backend). pando logs --source <repository> reads the logs of the processes in it.
  • The TUI says which repository a process, a log tab and a commit are
    of, keeps a row for a checkout a set lacks, names the dirty
    repository in the remove dialog, lets the create dialog come back to
    each repository's own base, and welcomes a folder of repositories as
    one.

Fixed

  • A folder of repositories, or a repository whose apps sit in sibling
    directories: one app's PORT is no longer proposed as the project's
    port_env, an app's own references reach that app alone, and a key a
    second app also declares is no longer lost.
  • An app is told where a sibling listens when the sibling's port is only
    in its code (process.env.PORT || 3001) or the reference only in the
    app's own gitignored .env.
  • An app directory with a start script and no dev script is offered,
    running it, instead of being left out.
  • The worktree's URL goes to the app that serves pages rather than an
    API that sorts first: the API's table says page = false.
  • A page in an answered process table is written.
  • A multi-repo project's services: a compose file at a repository's root
    (infra/docker-compose.yml) is proposed and run, and an isolated start
    reads the address it rewrites from the repository that keeps it,
    where it failed on every such project. Every directory's real env file
    now speaks before any directory's example.
  • doctor reports a repository whose origin/HEAD is far behind its main
    checkout's branch, with the [repos.base] line that fixes it.

Install pando-cli 0.11.1

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/mertkaradayi/pando/releases/download/v0.11.1/pando-cli-installer.sh | sh

Install prebuilt binaries via Homebrew

brew install mertkaradayi/tap/pando

Download pando-cli 0.11.1

File Platform Checksum
pando-cli-aarch64-apple-darwin.tar.xz Apple Silicon macOS checksum
pando-cli-x86_64-apple-darwin.tar.xz Intel macOS checksum
pando-cli-aarch64-unknown-linux-musl.tar.xz ARM64 MUSL Linux checksum
pando-cli-x86_64-unknown-linux-musl.tar.xz x64 MUSL Linux checksum

Verifying GitHub Artifact Attestations

The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:

gh attestation verify <file-path of downloaded artifact> --repo mertkaradayi/pando

You can also download the attestation from GitHub and verify against that directly:

gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation> --repo mertkaradayi/pando