You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Inconsistent Variable Expansion When Using {{.VAR}} in .env Files with Nested Variables #1847
When using a .env file to define environment variables that rely on other variables using {{.VAR}} template syntax, the variables sometimes expand inconsistently across task runs. The issue becomes more apparent as the variables become more deeply nested.
godotenv.Read(dotEnvPath) reads from a .dotenv file to a map, important, not an ordered map. So your .dotenv file will not be deterministically evaluated.
godotenv.Read() is fairly small, it would be a trivial PR to copy the necessary code into the Task repo, replacing the map with the same ordered map that Task uses.
Activity
trulede commentedon Dec 9, 2025
godotenv.Read(dotEnvPath) reads from a .dotenv file to a map, important, not an ordered map. So your .dotenv file will not be deterministically evaluated.
godotenv.Read() is fairly small, it would be a trivial PR to copy the necessary code into the Task repo, replacing the map with the same ordered map that Task uses.