@posthog/cli 0.7.17 → 0.7.18

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,9 @@
1
1
  # posthog-cli
2
2
 
3
+ # 0.7.18
4
+
5
+ - fix: rename `--env-file` to `--dotenv-file`. The npm package runs the CLI binary through a `node` wrapper script, and Node has its own built-in `--env-file` flag — so Node intercepted the flag before it reached the binary, failing with `node: .env: not found` for a missing file. `--env-file` still works as an alias for native installs.
6
+
3
7
  # 0.7.17
4
8
 
5
9
  - fix: treat a missing `--env-file` as a warning instead of a fatal error — the CLI logs that the file wasn't found and falls back to the other credential sources (process env, then stored credentials). A file that exists but can't be read still errors.
package/README.md CHANGED
@@ -28,9 +28,9 @@ You can authenticate with PostHog interactively for using the CLI locally, but i
28
28
  - `POSTHOG_CLI_API_KEY`: [A posthog personal API key.](https://posthog.com/docs/api#private-endpoint-authentication) (also accepts `POSTHOG_CLI_TOKEN` for backward compatibility)
29
29
  - `POSTHOG_CLI_PROJECT_ID`: The ID number of the project/environment to connect to. E.g. the "2" in `https://us.posthog.com/project/2` (also accepts `POSTHOG_CLI_ENV_ID` for backward compatibility)
30
30
 
31
- These variables can also be loaded from a dotenv-style file via `--env-file <PATH>` (e.g. `posthog-cli --env-file .env query ...`). The process environment always wins; the file is only consulted if the required variables aren't set. `POSTHOG_CLI_HOST` is only read from the same source that supplied the rest, so a stray host in the file cannot redirect a key supplied by the process env.
31
+ These variables can also be loaded from a dotenv-style file via `--dotenv-file <PATH>` (e.g. `posthog-cli --dotenv-file .env query ...`). The process environment always wins; the file is only consulted if the required variables aren't set. `POSTHOG_CLI_HOST` is only read from the same source that supplied the rest, so a stray host in the file cannot redirect a key supplied by the process env.
32
32
 
33
- Full precedence: CLI args → process env → `--env-file` → `~/.posthog/credentials.json` (from `posthog-cli login`).
33
+ Full precedence: CLI args → process env → `--dotenv-file` → `~/.posthog/credentials.json` (from `posthog-cli login`).
34
34
 
35
35
  ## Skipping uploads (dry run)
36
36
 
@@ -19,7 +19,7 @@
19
19
  "hasInstallScript": true,
20
20
  "license": "MIT",
21
21
  "name": "@posthog/cli",
22
- "version": "0.7.17"
22
+ "version": "0.7.18"
23
23
  },
24
24
  "node_modules/detect-libc": {
25
25
  "engines": {
@@ -48,5 +48,5 @@
48
48
  }
49
49
  },
50
50
  "requires": true,
51
- "version": "0.7.17"
51
+ "version": "0.7.18"
52
52
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "artifactDownloadUrls": [
3
- "https://github.com/PostHog/posthog/releases/download/posthog-cli/v0.7.17"
3
+ "https://github.com/PostHog/posthog/releases/download/posthog-cli/v0.7.18"
4
4
  ],
5
5
  "bin": {
6
6
  "posthog-cli": "run-posthog-cli.js"
@@ -114,7 +114,7 @@
114
114
  "zipExt": ".tar.gz"
115
115
  }
116
116
  },
117
- "version": "0.7.17",
117
+ "version": "0.7.18",
118
118
  "volta": {
119
119
  "node": "18.14.1",
120
120
  "npm": "9.5.0"