envstash-cli 0.5.0 → 0.5.1

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.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/src/index.mjs +8 -0
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "envstash-cli",
3
- "version": "0.5.0",
3
+ "version": "0.5.1",
4
4
  "description": "Git-style CLI for EnvStash — keep your .env files in sync with your cloud account.",
5
5
  "keywords": [
6
6
  "env",
package/src/index.mjs CHANGED
@@ -161,6 +161,14 @@ export async function run(argv) {
161
161
  }
162
162
 
163
163
  try {
164
+ // Which binary is actually running, on every command, before it does
165
+ // anything. The incident this answers: a repo-local 0.4.4 ran
166
+ // `push --shared`, silently ignored the flag it predated, and pushed to
167
+ // the project — with nothing on screen saying an old CLI was involved.
168
+ // To stderr, so `envs status --json | jq` and every other stdout consumer
169
+ // stay clean; dim, so it reads as chrome rather than output.
170
+ errOut(style.dim(`envs v${version()}`))
171
+
164
172
  changeDirectory(flags)
165
173
  const code = await command.run(flags, rest)
166
174
  return finish(code ?? 0)