This repository was archived by the owner on Nov 1, 2026. It is now read-only.
Repository navigation
v1.5.2
Changelog
Bug fixes
- f0a3d23 fix: MCP tools pick their server without writing the shared --server flag, so tools run at once don't send each other to the wrong server, nor clear the flag hakobu mcp was started with
- 7a66dff fix: a registry's digest must be sha256: and 64 hex digits, so it can't name a file outside releases/ (state.json, say)
- 85e71c3 fix: a secret of more than 1 MiB is refused when it's set, and an error when it's opened, instead of cut short
- 19155bb fix: an audit check that can't run (Docker restarting, say) leaves its open alerts open instead of closing them as put right
- 41235f8 fix: behind a tunnel apps see the visitor's scheme from cloudflared (https), not http, so their cookies get Secure and their links https
- 878c110 fix: hakobu logs and deploy print an app's output without the control characters a terminal would act on (OSC 52 to the clipboard, a drawn prompt)
- 18c24b6 fix: init and secret set write no file through a link in the repository, and init takes only a branch's and an image's name into the workflow, not YAML
- 5832a74 fix: mail with a line break in its from or to isn't sent, and one in a subject (a carriage return too) becomes a space, so neither can add headers
- b4e4cbc fix: only the release image that deployed a project may deploy it again, so a release naming another project can't take its databases; removing such an image needs the admin token
- 33770e9 fix: the API listens on loopback or a tailnet address alone: [::], names and public addresses are refused, not only 0.0.0.0
- 0741523 fix: the CLI and MCP tools escape the project and app they put in the API's query, so a name can't add parameters
- 4662f9e fix: the app proxies give up on an app that takes a request and sends no headers in 5 minutes, and the web's connections idle for 2 minutes at most
- 0ae4d9b fix: the installer keeps a root key's from= and expiry-time= when it gives the key to deploy, and won't take over a deploy user whose marker or home isn't root's, or is a link