From db1faef9fbe5c4e944eb51dceaf90165bfeb5ad3 Mon Sep 17 00:00:00 2001 From: enricobuehler Date: Mon, 3 Aug 2026 16:00:48 +0200 Subject: [PATCH] docs(plugins): don't name a release that doesn't exist yet The /tmp troubleshooting note said PrivateTmp=yes shipped "until 0.23.1". 0.23.0 is the latest tag and the next number isn't decided, so that could be wrong on arrival. "In earlier releases" is true whichever number it gets. Co-Authored-By: Claude Opus 5 (1M context) --- docs-site/content/docs/plugins.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs-site/content/docs/plugins.mdx b/docs-site/content/docs/plugins.mdx index 81d1472d..9de18f07 100644 --- a/docs-site/content/docs/plugins.mdx +++ b/docs-site/content/docs/plugins.mdx @@ -335,7 +335,7 @@ plugins (stop it with Ctrl+C): **A plugin can't reach a service running on the same box (Linux)** — plugins that drive a local daemon usually talk to it over a socket or FIFO in `/tmp`. The runner's unit shipped with -`PrivateTmp=yes` until 0.23.1, which gave it a private `/tmp` and hid all of it: the plugin would +`PrivateTmp=yes` in earlier releases, which gave it a private `/tmp` and hid all of it: the plugin would launch the vendor's binary happily and then time out reaching the daemon behind it, while the same command worked perfectly in your own shell. If you are on an older host, or you have a drop-in that reinstates it, put the real `/tmp` back: