Python-dotenvx

Changed

* 🐞 fix decrypt re-encrypt of values containing backslashes ([406](https://github.com/dotenvx/dotenvx/pull/407))

Changed

* forward additional signals like `SIGUSR2` ([403](https://github.com/dotenvx/dotenvx/pull/403))

Changed

* if `SIGTERM` or `SIGINT` sent, don't bubble wrapped process error ([402](https://github.com/dotenvx/dotenvx/pull/402))

Added

* support key glob filtering for `encrypt` and `decrypt`. example: `dotenvx encrypt -ek "NEXT_PUBLIC_*"` ([397](https://github.com/dotenvx/dotenvx/pull/397))

Added

* escape user inputted regex groupings like `$1` or `$2`. ([396](https://github.com/dotenvx/dotenvx/pull/396))

Added

* `set` and `encrypt` preserve leading spaces ([395](https://github.com/dotenvx/dotenvx/pull/395))

sh
HELLO=world


Changed

* improve escape and quote handling for `set`, `encrypt`, and `decrypt` ([395](https://github.com/dotenvx/dotenvx/pull/395))
* 🐞 fix `encrypt`, then `decrypt`, then `encrypt` on a json value ([377](https://github.com/dotenvx/dotenvx/issues/377))

Note: the underlying `replace` engine to support these changes now wraps your values in single quotes. the prior `replace` engine wrapped in double quotes.

So where your `.env` used to look like this with double quotes:

sh
HELLO="encrypted:1234"
API_KEY="encrypted:5678"


It will now begin looking like this with single quotes:

sh
HELLO='encrypted:1234'
API_KEY='encrypted:5678'


It's an aesthetic side effect only. Your values will continue to be decrypted and encrypted correctly.