- #1281 (minor) Thanks @jsskeen-utah! - Generated C# modules now decrypt @encryptInjectedEnv blobs using _VARLOCK_ENV_KEY, instead of rejecting them.
- #1300 (minor)
Add built-intimeZonedata type that validates IANA time zone names. Rename thesimple-objectdata type tosimpleObjectso all built-in type names are camelCase (simple-objectstill works but logs a deprecation warning). - #1269 (patch) -
varlock auditnow detectsENV.KEY(from@generatePythonEnv) andos.environ.get()reads in Python files - #1288 (patch) Thanks @voiys! - An item reached by several resolvers at the same time is resolved and validated once instead of once per caller
- #1286 (patch) Thanks @voiys!
A dependency cycle is now reported even when another item has a schema error, instead of the load stopping with "varlock stopped before the command finished" - #1285 (patch) Thanks @voiys!
An error from a decorator's value (for example@required=forEnv(prod)when the current environment is not set) is reported once instead of twice - #1270 (patch)
Reusing an injected env blob (auto-load undervarlock run) now also re-resolves when an env file it would load, like.env.local, was created after the blob was made - #1284 (patch) Thanks @voiys!
Resolving a large schema no longer slows down quadratically with the number of items (3,000 items: about 245 ms to 50 ms) - #1299 (patch) - Fix
varlock runcorrupting multi-byte UTF-8 characters split across chunks of piped output - #1283 (patch) Thanks @voiys! - Key globs with many
*(inpick/omit,--filterand@auditIgnoreKeys) no longer take seconds or minutes to match - #1253 (patch)
Native helper packages (@varlock/native-helper-*) are now versioned independently and only re-released when their binaries change. varlock still pins exact helper versions. - #1265 (patch)
Proxy: response scrubbing and body substitution no longer corrupt non-UTF-8 bodies (e.g. Go checksum database tiles served as text/plain), HEAD responses keep theircontent-length, and 206 partial responses are no longer rewritten - #1296 (patch)
Fixvarlock runandvarlock proxy rundropping piped output: output still unread when the command exits, output from background processes it started, and output that a slow reader had not consumed within 1 second - #1271 (patch)
Fix CLI calls occasionally losing stdout/stderr when the command exits quickly under load, which could surface as a vague "unknown" error instead of the real one - #1295 (patch)
AcceptVARLOCK_ENV_KEY(and the other_VARLOCK_*config vars without the leading underscore) for platforms like AWS Lambda that reject env var names starting with_
Published to
- ✅ npm