Repository navigation
0.10.1 — 2026-10-08
Release Notes
Changed
- A placeholder in a command a process, hook or probe runs is quoted for
where it stands: bare, inside double quotes, or inside single quotes.
A path with a space is one word, and a fork's branch namedx$(…)is
text, not a command. A plain value renders as before, andenvvalues
are not commands and stay as they are. .env.localis read before.env, as Next, Vite and dotenv-flow read
them, so pando finds the database and login the app really uses.- In namespaced mode each database the main checkout uses gets one of the
worktree's own.DATABASE_URL'sshopandTEST_DATABASE_URL's
shop_testused to become oneshop__<worktree>, so a test suite that
emptied its test database emptied the worktree's dev data.
Fixed
-
Namespaced mode tells a Redis slot it gave out from the same number on
another Redis answering on the same port. Each slot is marked as the
worktree's, and pando keeps which server process it was on.rmno
longer empties, and a start no longer writes into, another server's
slot. A slot recorded before this is trusted as before. -
Namespaced mode never makes or runs on a database that another
project's state records, such as a second clone of the repository on
the same server. -
The git menu no longer loses an ignored file such as
.env. A pull,
rebase or merge onto a base that has started tracking that path used
to replace it, and the abort after a conflict deleted it. Such a move
is now refused before anything runs, naming the files. -
The git menu moves a branch onto the base it was made from. That is
the branchnew --baseforked it from, or, for a pull request, the
branch the pull request targets. It used to rebase onto the
configured base: a branch cut fromreleaseand rebased ontomain
took every commit ofreleasewith it. -
The git menu refuses a move when
git statusdoes not answer, rather
than reading the tree as clean. Its fetches get five minutes, not
thirty seconds. -
A fork's pull request is fetched from the remote of the repository it
was opened against, such asupstream. Fetching fromorigin, a
contributor's own fork, could check out a different pull request with
the same number. -
pando rmdrops nothing in namespaced mode while it cannot read what
the main checkout's env files name today. Before, an unresolved value,
a renamed service or a moved port meant it decided on the record alone. -
Namespaced mode runs a worktree only on a database pando made. One
that was gone and was made again by something else, between pando's
check and its create, is refused rather than taken over. -
Namespaced mode reaches a server named by an IPv6 address
(postgres://…@[::1]:5432/shop). The clients used to be handed the
address in brackets, which they cannot resolve. -
pando doctornever offers to drop a database that a main checkout
names, even when the name looks like a worktree's. -
Namespaced mode finds a database container whose port on the host
differs from the port inside it (5433:5432). Docker's--filter publish=matches the inside port, so pando used to find nothing. -
The share proxy logs in only requests for the tunnel's own host. A web
page or another process reaching its loopback port directly is
answered421and never gets the session cookie. -
A shared event stream or long poll that is quiet for more than a
minute is no longer cut off. The proxy's upstream deadline now ends at
the first byte of the answer. The header deadline now covers the whole
header block, not each read. -
A Ctrl-C during
pando check's install or start records the check as
interrupted, not as failing settings. -
A Ctrl-C while
newclones files copy-on-write now stops it before
git writes the rest of the checkout and before thepost-checkout
hook runs. -
A port held by a listener on
[::]withIPV6_V6ONLYis no longer
handed out as free. uvicorn's--host ::and nginx'slisten [::]
listen like that. -
A process whose whole group had already exited when it was seen to
fail is never signalled later. That pid may by then belong to
something else. -
The state file is synced to disk before it replaces the old one, so a
crash right after a save cannot leave it empty. -
pando updatedownloads the install script into a new file only you
can write, not to a predictable path in the shared temporary
directory. Pre-release tags are ordered as semver orders them
(rc.10afterrc.9). -
The TUI saves the list's order and the theme when
uiin the config
is an inline or dotted table. It used to report success and write
nothing. -
A workspace member excluded with a negated glob, such as
!apps/legacy, is no longer proposed as an app.
Install pando-cli 0.10.1
Install prebuilt binaries via shell script
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/mertkaradayi/pando/releases/download/v0.10.1/pando-cli-installer.sh | shInstall prebuilt binaries via Homebrew
brew install mertkaradayi/tap/pandoDownload pando-cli 0.10.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/pandoYou 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