@bensandee/tooling 0.76.0 → 0.77.0

package/README.md

@@ -501,6 +501,17 @@ Available override fields:
 | `detectPackageTypes` | boolean | `true`                                                                           |
 | `pnpmWorkspace`      | `false` | Set to `false` to opt out of `pnpm-workspace.yaml` management                    |
 
+## Environment file
+
+Set `BST_ENV_FILE` to the path of an env file and every `bst` command loads it before anything else runs -- a way to feed tokens to the tools from one annotated file without exporting them into your shell:
+
+```bash
+# in your shell profile
+export BST_ENV_FILE=/home/you/.secrets.env
+```
+
+The file takes `KEY=value` lines, `#` comments, blank lines, and an optional `export ` prefix. A variable already set in the environment always wins over the file, so a container's `-e` or a shell export is never overridden. Unset, no file is touched; set to a file that cannot be read, the command fails before it starts (under `--json`, as the usual `{ok: false}` document). Name the file so it ends in `.env`: the bst-hook then keeps an agent session from reading or writing it while the tools still load it. This is a development convenience -- a production container should receive every variable through `docker run -e` and leave `BST_ENV_FILE` unset.
+
 ## Debug logging
 
 All CLI commands support a `--verbose` flag for detailed debug output. Alternatively, set `TOOLING_DEBUG=true` as an environment variable -- useful in CI workflows: