Repository navigation
Pipe v0.50.1
Patching from the /web page shows the real result
- Patching from the public
/webpage could end with "The install failed" and a bare "Error" even though it had
worked. Refreshing thepipe-webcontainer, the last step, cuts the page's connection, so the result never reached
the browser. The page now goes back for the result after the connection drops - When the connection does not come back, the card says it lost the connection before the result, instead of claiming
that the install failed - Protocol: the new read-only
patch_statuscommand returns the progress and result of the running or just finished
patch. It starts nothing
Images (linux/amd64, linux/arm64):
docker pull ghcr.io/kvmyk/pipe:0.50.1
docker pull ghcr.io/kvmyk/pipe-telegram:0.50.1
Signature (cosign, keyless):
cosign verify ghcr.io/kvmyk/pipe:0.50.1 \
--certificate-identity-regexp '^https://github.com/Kvmyk/Pipe/\.github/workflows/release\.yml@' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com