Skip to content

CHANGELOG.md

Latest commit

 

History

History
122 lines (66 loc) · 7.29 KB

CHANGELOG.md

File metadata and controls

122 lines (66 loc) · 7.29 KB
Raw

env-spec-language

0.3.2

2026-07-31

  • #960 (patch) - Add generateOtp() to autocomplete

0.3.1

2026-07-28

  • #944 (patch) - Fix false "can only be used once" diagnostic for multiline plugin init decorators (e.g. @initInfisical()

0.3.0

2026-07-21

  • #917 (minor) Add array and object value types: @type=array(...) and @type=record(...) with per-element validation, native [a, b] / {k=v} literal values, JSON and separator string input, configurable serialization back to process.env, per-element redaction, and typed code generation across languages

0.2.7

2026-07-20

  • #892 (patch) - Add @generateJavaEnv and @generateCsharpEnv loadable env modules (typed Env, loader, sensitive keys)

0.2.6

2026-07-15

  • #873 (patch) Add editor autocomplete and hover docs for the new @tag() decorator, the filter= arg on @generate* decorators, and @internal

0.2.5

2026-07-06

  • #849 (patch) Generate code for Python, Rust, Go, and PHP with new per-language decorators (@generatePythonEnv, @generateRustEnv, @generateGoEnv, @generatePhpEnv). Each emits a self-contained, idiomatic module — typed coerced values, a loader that parses the injected env, and a SENSITIVE_KEYS constant — so it's usable out of the box. The TypeScript generator moves to @generateTsTypes and gains options to control process.env/import.meta.env augmentation and a monorepo-friendly exposeEnv=local mode. @generateTypes(lang=ts) still works as a deprecated alias. The varlock typegen command is renamed to varlock codegen (with typegen kept as a deprecated alias). Note: @disableProcessEnvInjection now requires a static true/false value — env-dependent values like forEnv(prod) are a schema error, since generated code must not differ per environment.

0.2.4

2026-06-23

  • #816 (patch) - Improve syntax highlighting for array/object literals: highlight bare item-value literals (e.g. KEY=[a, b], KEY={ k=v }) and fix unindented (column-0) comments inside multi-line fn(...) literals

0.2.3

2026-06-17

  • #792 (patch) - Maintenance release — no functional changes (switches Marketplace publishing to OIDC)
  • #794 (patch) - Object and array literals can now span multiple lines. Inside decorators each continuation line is prefixed with # (like multi-line function calls), e.g. a long @import(./.env.shared, pick=[ ... ]) key list; literals nested in item-value function calls use plain newlines. Single-line literals are unchanged. Multi-line literals and function calls also support # comments — full-line entries can be commented out (# # OLD_KEY,) and individual entries annotated with trailing comments (# KEY, # note). The VSCode extension's syntax highlighting now understands object/array literals (single- and multi-line) and these inline comments.
  • #795 (patch) - Fix syntax highlighting: closing paren in a nested decorator function call (e.g. @dec(fn())) no longer shows as an error

0.2.2

2026-06-16

  • #786 (patch) - @setValuesBulk and @import support pick/omit key filters. Filter which keys are brought in with pick (allowlist) or omit (denylist) array args — e.g. @setValuesBulk(opLoadEnvironment(env-id), pick=[API_KEY, DB_*]) or @import(./.env.shared, omit=[LEGACY_TOKEN]). By default every key is included; pick and omit can't be combined, and both accept simple globs (*, ?). For @import, listing keys as positional args (@import(./.env.shared, KEY1, KEY2)) is now deprecated in favor of pick=[...] — it still works but warns.

0.2.1

2026-06-03

  • #742 (patch) Thanks @Shtian! - Fixed URL fragments in @docs() decorator not being highlighted correctly.

0.2.0

2026-05-11

  • #569 Thanks @danish-fareed! - add code env scanner and audit command with @auditIgnore / @auditIgnorePaths decorators

0.1.3

Patch Changes

  • #620 0f3ca3b - Fix regex literal parsing ambiguity with file paths

    Removed grammar-level regex literal (/pattern/) parsing which caused paths like /folder/foo/bar to be incorrectly parsed as regex patterns. Regex-like strings are now detected at runtime by specific consumers (remap() match values, matches type option) instead of at the grammar level. Unquoted strings that look like /pattern/flags are treated as regex in those contexts; wrap in quotes to force literal string matching.

0.1.2

Patch Changes

  • #599 c498964 - Add noTrailingSlash and matches (regex) options to the url data type. Add regex literal syntax (/pattern/flags) as a new language feature, deprecating the regex() function wrapper.

0.1.1

Patch Changes

  • #467 72f1ef0 Thanks @voiys! - Fix VS Code diagnostics and completions so decorator parsing ignores prose mentions and post-comments while still matching parser behavior for leading @word comment lines.

  • #468 6313f82 Thanks @voiys! - Fix duplicate decorator diagnostics so repeated function-style decorators stay valid and split header root decorators still share one header scope.

0.1.0

Minor Changes

  • #370 5fa49f7 Thanks @voiys! - Add IntelliSense, inline diagnostics, and docs demos for the VS Code extension.

0.0.5

Patch Changes

0.0.4

Patch Changes

0.0.3

Patch Changes

  • #320 0992470 - multi-line function calls, many highlighting fixes