Skip to content

🐸 Versioned release#791

Merged
theoephraim merged 1 commit into
mainfrom
bumpy/version-packages
Jun 17, 2026
Merged

🐸 Versioned release#791
theoephraim merged 1 commit into
mainfrom
bumpy/version-packages

Conversation

@bumpy-bot

@bumpy-bot bumpy-bot commented Jun 16, 2026

Copy link
Copy Markdown
Collaborator

bumpy-frog

This PR was created and will be kept in sync by bumpy based on your bump files (in .bumpy/). Merge it when you are ready to release the packages listed below:

patch Patch releases

@env-spec/parser 0.4.0 → 0.4.1 CHANGELOG.md

  • 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. (bump file)
    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.

env-spec-language 0.2.2 → 0.2.3 CHANGELOG.md

  • Maintenance release — no functional changes (switches Marketplace publishing to OIDC) (bump file)
  • 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. (bump file)
    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.
  • Fix syntax highlighting: closing paren in a nested decorator function call (e.g. @dec(fn())) no longer shows as an error (bump file)

varlock 1.7.0 → 1.7.1 CHANGELOG.md

  • Fix typed builtin vars (e.g. boolean VARLOCK_IS_CI) being stringified when referenced from root decorators like @import/@initOp, which broke not()/if() logic (bump file)
  • 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. (bump file)
    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.

@github-actions github-actions Bot added release releases - managed by changesets core:varlock labels Jun 16, 2026
@bumpy-bot bumpy-bot force-pushed the bumpy/version-packages branch from f07595b to aae59ab Compare June 16, 2026 22:50
@bumpy-bot bumpy-bot force-pushed the bumpy/version-packages branch 3 times, most recently from f58dce3 to 8832680 Compare June 17, 2026 05:51
@env-spec/parser@0.4.1
env-spec-language@0.2.3
varlock@1.7.1
@bumpy-bot bumpy-bot force-pushed the bumpy/version-packages branch from 8832680 to fdb3430 Compare June 17, 2026 06:38
@theoephraim theoephraim merged commit a4ba859 into main Jun 17, 2026
30 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants