v0.4.1

What's New

fix: exit 2 when a confirmation is declined, not 0

Answering No to "update the existing item?", "create the vault?" or
op2env's "overwrite the file?" exited 0, the same as a completed push or
pull, so a script calling env2op could not tell that nothing was written.
Declining now exits 2 with "Cancelled: nothing written". Ctrl-C or Escape
at the prompt counts as declining too; 0 still means done and 1 failed.

A prompt with no terminal to answer it also counts as declined, with a hint
to pass -f/--force. Before, it hung on a stdin that stayed open, and on one
that closed the process exited 0 with the question unanswered.

The integration tests run both bins against a fake op, answering the
prompts through a pseudo-terminal (script) and without one; they fail if
declining exits 0. They type only once the prompt is on screen: sent
earlier, Ctrl-C would be a real SIGINT and a letter would sit in the line
buffer.

feat: ENV2OP_NO_UPDATE_CHECK turns off the update check and notice

Setting ENV2OP_NO_UPDATE_CHECK to any non-empty value other than "0" or
"false" skips the automatic update check in both env2op and op2env: no
request to the npm registry, no write to ~/.env2op/update-check.json, and no
"update available" notice. It is meant for tools that bundle env2op at a
pinned version, where the notice would point at the global install rather
than the copy being run. An explicit --update does not go through this path
and still works.

The update cache directory is now resolved per use, with a test-only
override, so the tests can prove nothing is written without touching the
real ~/.env2op.

chore: update manifests for v0.4.0

---

Installation

Homebrew (macOS/Linux)

brew install tolgamorf/tap/env2op-cli

Package Managers (macOS/Linux/Windows)

# Using bun
bun add -g @tolgamorf/env2op-cli

# Using npm
npm install -g @tolgamorf/env2op-cli

# Using pnpm
pnpm add -g @tolgamorf/env2op-cli