changelog 🪵

Author: motdotla

CHANGELOG.md

@@ -12,9 +12,17 @@ All notable changes to this project will be documented in this file. See [standa
 
 ### Changed
 
-* 🎉 Expansion logic rewritten to match [dotenvx's](https://github.com/dotenvx/dotenvx). (*NOTE: I recommend dotenvx over dotenv-expand when you are ready. I'm putting all my effort there for a unified standard .env implementation that works everywhere and matches bash, docker-compose, and more. In some cases it slightly improves on them - leading to more reliability for your secrets and config.*) ([#131](https://github.com/motdotla/dotenv-expand/pull/131))
-* ⚠️ BREAKING: do NOT expand in reverse order. Instead, order your .env file keys from first to last as they depend on each other for expansion - principle of least surprise. ([#131](https://github.com/motdotla/dotenv-expand/pull/131))
-* ⚠️ BREAKING: do NOT attempt expansion of process.env. This has always been dangerous (unexpected side effects) and is now removed. process.env should not hold values you want to expand. Put expansion logic in your .env file. If you need this ability, use [dotenvx](https://github.com/dotenvx/dotenvx) by shipping an encrypted .env file with your code - allowing safe expansion at runtime. ([#131](https://github.com/motdotla/dotenv-expand/pull/131))
+* 🎉 Expansion logic rewritten to match [dotenvx](https://github.com/dotenvx/dotenvx) ([#131](https://github.com/motdotla/dotenv-expand/pull/131))
+
+> NOTE: I recommend dotenvx over dotenv-expand when you are ready. I'm putting all my effort there for a unified standard .env implementation that works everywhere and matches bash, docker-compose, and more. In some cases it slightly improves on them - leading to more reliability for your secrets and config.
+
+* ⚠️ BREAKING: do NOT attempt expansion of process.env ([#131](https://github.com/motdotla/dotenv-expand/pull/131))
+
+> This has always been dangerous (unexpected side effects) and is now removed. `process.env` should not hold values you want to expand. If for some reason you need equivalent abilities, use [dotenvx](https://github.com/dotenvx/dotenvx). You can ship an encrypted .env file with your code - allowing safe expansion at runtime - rather than relying on trying to expand pre-existing `process.env` values that could for good reason have a dollar sign in them (example a password). 
+
+* ⚠️ BREAKING: do NOT expand in reverse order ([#131](https://github.com/motdotla/dotenv-expand/pull/131))
+
+> Instead, order your KEYS from first to last as they depend on each other for expansion - principle of least surprise. 
 
 ## [11.0.7](https://github.com/motdotla/dotenv-expand/compare/v11.0.6...v11.0.7) (2024-11-13)