@dotenvx/primitives
4.4.0 · 6 Nov 2026BSD-3-Clause18.4M / weekRepositorynpmAtom feed
Upgrading @dotenvx/primitives From 1.10.0 to 4.4.0
27 releases in betweennotes for 5
Reading releases, release notes and advisories…
- 4+
- changes to make
- 0
- advisories fixed
- 7+
- new
- ?
- fixes
Counted from 5 of 27 release notes. Advisories are counted from the advisory database, in full.
Before you upgrade
Tick each one off as you go- Breaking2.0.0
- Breaking2.0.0
- Breaking2.0.0
- Breaking2.0.0
Release by release
3.0.0 – 4.4.022 releases, no release note
- New
Use
dotenvx keychain up|downto move your private keys to your macOS Keychain
- New
- New
Support
DOTENV_CONFIG_QUIET=trueas synonym for--quietflag
- New
- New
Add interactive input mode for
set - New
Support leaving
_PLAINsuffixed keys unencrypted duringsetandencrypt - New
Add Windows PowerShell coverage for npm shim encryption of
.env.localfiles
- New
- Breaking
lib/main#
setasync only - Breaking
lib/main#
getasync only - Breaking
Remove the
rotatecommand (it will return in 2.1 or 2.2 soon with a more complete implementation for local and armored keys) - Breaking
Remove the library
doctor,keypair, andgenexampleexports fromlib/main - New
New keyring support - for local and armor providers and to unlock future providers
- Breaking
4 other lines we could not sort, mostly version bumps
- 2.1.0
Return exit code 1 from
getwhen decryption errors are reported - 2.0.0
Route
run,config, andgetthrough shared env and keypair resolvers backed by@dotenvx/primitives - 2.0.0
Route
set,encrypt, anddecryptthrough shared transforms that operate on primitive scan, parse, encrypt, and upsert results - 2.0.0
Update library
parseto use primitive parsing while preserving dotenvx-style encrypted value errors
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.