Summary
The CLI version output is inconsistent with the actual installed npm package version.
- pnpm global list shows @dokploy/cli@0.29.4
- dokploy -V reports 0.3.0
This makes version-based debugging and issue triage confusing.
Steps to Reproduce
-
Install latest global package (or use existing install)
-
Run:
pnpm -g list --depth 0
-
Run:
dokploy -V
Actual Behavior
- pnpm reports: @dokploy/cli@0.29.4
- dokploy -V prints: 0.3.0
Expected Behavior
- dokploy -V should print the same version as the installed package version (0.29.4 in this case).
Environment
- OS: Windows (Git Bash)
- Package manager: pnpm
- Global package path: D:\sdks\pnpm-bin\global\v11
- CLI resolved from PATH: D:\sdks\pnpm-bin\bin\dokploy
Additional Debug Info
The installed package metadata appears correct:
- package.json version: 0.29.4
But the built entrypoint contains a hardcoded different version string, which is what commander uses for -V output.
If helpful, I can share full command outputs and exact shim target path.
Summary
The CLI version output is inconsistent with the actual installed npm package version.
This makes version-based debugging and issue triage confusing.
Steps to Reproduce
Install latest global package (or use existing install)
Run:
pnpm -g list --depth 0
Run:
dokploy -V
Actual Behavior
Expected Behavior
Environment
Additional Debug Info
The installed package metadata appears correct:
But the built entrypoint contains a hardcoded different version string, which is what commander uses for -V output.
If helpful, I can share full command outputs and exact shim target path.