Skip to content

[Changesets] Versioned release#2

Open
github-actions[bot] wants to merge 1 commit intomainfrom
changeset-release/main
Open

[Changesets] Versioned release#2
github-actions[bot] wants to merge 1 commit intomainfrom
changeset-release/main

Conversation

@github-actions
Copy link
Copy Markdown

@github-actions github-actions bot commented Mar 31, 2026

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

varlock@0.7.0

Minor Changes

  • #483 ba61adb - Add support for single-file ESM and TypeScript plugins, and improve the plugin authoring API.

    New: ESM and TypeScript single-file plugins

    Single-file plugins can now be written as .mjs or .ts files in addition to .js/.cjs. TypeScript plugins require Bun.

    Improved: explicit plugin import instead of injected global

    Plugin authors should now import plugin explicitly from varlock/plugin-lib rather than relying on the injected global:

    // CJS plugin (.js / .cjs)
    const { plugin } = require("varlock/plugin-lib");
    
    // ESM plugin (.mjs / .ts)
    import { plugin } from "varlock/plugin-lib";

    This works in both regular installs and SEA binary builds. Error classes (ValidationError, CoercionError, etc.) are also now directly importable from varlock/plugin-lib.

    Breaking change: the implicit plugin global is no longer injected into CJS plugin modules. Existing plugins must add const { plugin } = require('varlock/plugin-lib').

Patch Changes

  • #503 6fe325d - Fix Docker image failing to run due to missing libstdc++ and libgcc_s shared libraries on Alpine Linux. The bun-compiled binary dynamically links against these C++ runtime libraries, which are now installed in the Docker image via apk add libstdc++.

  • #507 76c17f8 - Fix @import(enabled=...) and @disable conditions not seeing values from .env, .env.local, and env-specific files

    Previously, import conditions and imported file @disable decorators were evaluated during .env.schema's initialization, before other files (.env, .env.local, .env.ENV, .env.ENV.local) were loaded. This meant that variables set in those files were not available when resolving conditions like enabled=eq($AUTH_MODE, "azure") or @disable=not(eq($AUTH_MODE, "azure")).

    Now, DirectoryDataSource loads all auto-loaded files first (registering their config items), then processes imports in a separate pass. This ensures all file values are available when import/disable conditions are evaluated.

@varlock/astro-integration@0.2.6

Patch Changes

@varlock/cloudflare-integration@0.0.1

Patch Changes

  • #480 39d88a9 - New @varlock/cloudflare-integration package for Cloudflare Workers

    • varlockCloudflareVitePlugin() — Vite plugin that reads secrets from Cloudflare bindings at runtime instead of bundling them into worker code
    • varlock-wrangler CLI — drop-in wrangler replacement that uploads non-sensitive values as vars and sensitive values as secrets on deploy; injects env into miniflare via Unix named pipe in dev; watches .env files for changes; generates correct Env types
    • @varlock/cloudflare-integration/init — standalone init module for non-Vite workers
      Refactors @varlock/vite-integration to remove Cloudflare-specific logic and add generic extension points (ssrEntryCode, ssrEdgeRuntime, ssrEntryModuleIds) for platform integrations.
  • Updated dependencies [ba61adb, 6fe325d, 76c17f8]:

    • varlock@0.7.0

@varlock/expo-integration@0.0.1

Patch Changes

@varlock/nextjs-integration@0.3.2

Patch Changes

@varlock/vite-integration@0.2.8

Patch Changes

  • #480 39d88a9 - New @varlock/cloudflare-integration package for Cloudflare Workers

    • varlockCloudflareVitePlugin() — Vite plugin that reads secrets from Cloudflare bindings at runtime instead of bundling them into worker code
    • varlock-wrangler CLI — drop-in wrangler replacement that uploads non-sensitive values as vars and sensitive values as secrets on deploy; injects env into miniflare via Unix named pipe in dev; watches .env files for changes; generates correct Env types
    • @varlock/cloudflare-integration/init — standalone init module for non-Vite workers
      Refactors @varlock/vite-integration to remove Cloudflare-specific logic and add generic extension points (ssrEntryCode, ssrEdgeRuntime, ssrEntryModuleIds) for platform integrations.
  • Updated dependencies [ba61adb, 6fe325d, 76c17f8]:

    • varlock@0.7.0

@varlock/1password-plugin@0.3.1

Patch Changes

  • #483 ba61adb - Add support for single-file ESM and TypeScript plugins, and improve the plugin authoring API.

    New: ESM and TypeScript single-file plugins

    Single-file plugins can now be written as .mjs or .ts files in addition to .js/.cjs. TypeScript plugins require Bun.

    Improved: explicit plugin import instead of injected global

    Plugin authors should now import plugin explicitly from varlock/plugin-lib rather than relying on the injected global:

    // CJS plugin (.js / .cjs)
    const { plugin } = require("varlock/plugin-lib");
    
    // ESM plugin (.mjs / .ts)
    import { plugin } from "varlock/plugin-lib";

    This works in both regular installs and SEA binary builds. Error classes (ValidationError, CoercionError, etc.) are also now directly importable from varlock/plugin-lib.

    Breaking change: the implicit plugin global is no longer injected into CJS plugin modules. Existing plugins must add const { plugin } = require('varlock/plugin-lib').

  • #513 3a480b2 - - fix: checkOpCliAuth() now always returns a completion callback (a no-op after the mutex is already settled) so follow-up op CLI paths still signal success/failure correctly; previously only the first call returned the deferred resolve function.

  • Updated dependencies [ba61adb, 6fe325d, 76c17f8]:

    • varlock@0.7.0

@varlock/aws-secrets-plugin@0.0.6

Patch Changes

  • #483 ba61adb - Add support for single-file ESM and TypeScript plugins, and improve the plugin authoring API.

    New: ESM and TypeScript single-file plugins

    Single-file plugins can now be written as .mjs or .ts files in addition to .js/.cjs. TypeScript plugins require Bun.

    Improved: explicit plugin import instead of injected global

    Plugin authors should now import plugin explicitly from varlock/plugin-lib rather than relying on the injected global:

    // CJS plugin (.js / .cjs)
    const { plugin } = require("varlock/plugin-lib");
    
    // ESM plugin (.mjs / .ts)
    import { plugin } from "varlock/plugin-lib";

    This works in both regular installs and SEA binary builds. Error classes (ValidationError, CoercionError, etc.) are also now directly importable from varlock/plugin-lib.

    Breaking change: the implicit plugin global is no longer injected into CJS plugin modules. Existing plugins must add const { plugin } = require('varlock/plugin-lib').

  • Updated dependencies [ba61adb, 6fe325d, 76c17f8]:

    • varlock@0.7.0

@varlock/azure-key-vault-plugin@0.0.6

Patch Changes

  • #483 ba61adb - Add support for single-file ESM and TypeScript plugins, and improve the plugin authoring API.

    New: ESM and TypeScript single-file plugins

    Single-file plugins can now be written as .mjs or .ts files in addition to .js/.cjs. TypeScript plugins require Bun.

    Improved: explicit plugin import instead of injected global

    Plugin authors should now import plugin explicitly from varlock/plugin-lib rather than relying on the injected global:

    // CJS plugin (.js / .cjs)
    const { plugin } = require("varlock/plugin-lib");
    
    // ESM plugin (.mjs / .ts)
    import { plugin } from "varlock/plugin-lib";

    This works in both regular installs and SEA binary builds. Error classes (ValidationError, CoercionError, etc.) are also now directly importable from varlock/plugin-lib.

    Breaking change: the implicit plugin global is no longer injected into CJS plugin modules. Existing plugins must add const { plugin } = require('varlock/plugin-lib').

  • Updated dependencies [ba61adb, 6fe325d, 76c17f8]:

    • varlock@0.7.0

@varlock/bitwarden-plugin@0.0.6

Patch Changes

  • #483 ba61adb - Add support for single-file ESM and TypeScript plugins, and improve the plugin authoring API.

    New: ESM and TypeScript single-file plugins

    Single-file plugins can now be written as .mjs or .ts files in addition to .js/.cjs. TypeScript plugins require Bun.

    Improved: explicit plugin import instead of injected global

    Plugin authors should now import plugin explicitly from varlock/plugin-lib rather than relying on the injected global:

    // CJS plugin (.js / .cjs)
    const { plugin } = require("varlock/plugin-lib");
    
    // ESM plugin (.mjs / .ts)
    import { plugin } from "varlock/plugin-lib";

    This works in both regular installs and SEA binary builds. Error classes (ValidationError, CoercionError, etc.) are also now directly importable from varlock/plugin-lib.

    Breaking change: the implicit plugin global is no longer injected into CJS plugin modules. Existing plugins must add const { plugin } = require('varlock/plugin-lib').

  • Updated dependencies [ba61adb, 6fe325d, 76c17f8]:

    • varlock@0.7.0

@varlock/google-secret-manager-plugin@0.2.1

Patch Changes

  • #483 ba61adb - Add support for single-file ESM and TypeScript plugins, and improve the plugin authoring API.

    New: ESM and TypeScript single-file plugins

    Single-file plugins can now be written as .mjs or .ts files in addition to .js/.cjs. TypeScript plugins require Bun.

    Improved: explicit plugin import instead of injected global

    Plugin authors should now import plugin explicitly from varlock/plugin-lib rather than relying on the injected global:

    // CJS plugin (.js / .cjs)
    const { plugin } = require("varlock/plugin-lib");
    
    // ESM plugin (.mjs / .ts)
    import { plugin } from "varlock/plugin-lib";

    This works in both regular installs and SEA binary builds. Error classes (ValidationError, CoercionError, etc.) are also now directly importable from varlock/plugin-lib.

    Breaking change: the implicit plugin global is no longer injected into CJS plugin modules. Existing plugins must add const { plugin } = require('varlock/plugin-lib').

  • Updated dependencies [ba61adb, 6fe325d, 76c17f8]:

    • varlock@0.7.0

@varlock/hashicorp-vault-plugin@0.0.4

Patch Changes

  • #483 ba61adb - Add support for single-file ESM and TypeScript plugins, and improve the plugin authoring API.

    New: ESM and TypeScript single-file plugins

    Single-file plugins can now be written as .mjs or .ts files in addition to .js/.cjs. TypeScript plugins require Bun.

    Improved: explicit plugin import instead of injected global

    Plugin authors should now import plugin explicitly from varlock/plugin-lib rather than relying on the injected global:

    // CJS plugin (.js / .cjs)
    const { plugin } = require("varlock/plugin-lib");
    
    // ESM plugin (.mjs / .ts)
    import { plugin } from "varlock/plugin-lib";

    This works in both regular installs and SEA binary builds. Error classes (ValidationError, CoercionError, etc.) are also now directly importable from varlock/plugin-lib.

    Breaking change: the implicit plugin global is no longer injected into CJS plugin modules. Existing plugins must add const { plugin } = require('varlock/plugin-lib').

  • Updated dependencies [ba61adb, 6fe325d, 76c17f8]:

    • varlock@0.7.0

@varlock/infisical-plugin@0.0.6

Patch Changes

  • #483 ba61adb - Add support for single-file ESM and TypeScript plugins, and improve the plugin authoring API.

    New: ESM and TypeScript single-file plugins

    Single-file plugins can now be written as .mjs or .ts files in addition to .js/.cjs. TypeScript plugins require Bun.

    Improved: explicit plugin import instead of injected global

    Plugin authors should now import plugin explicitly from varlock/plugin-lib rather than relying on the injected global:

    // CJS plugin (.js / .cjs)
    const { plugin } = require("varlock/plugin-lib");
    
    // ESM plugin (.mjs / .ts)
    import { plugin } from "varlock/plugin-lib";

    This works in both regular installs and SEA binary builds. Error classes (ValidationError, CoercionError, etc.) are also now directly importable from varlock/plugin-lib.

    Breaking change: the implicit plugin global is no longer injected into CJS plugin modules. Existing plugins must add const { plugin } = require('varlock/plugin-lib').

  • Updated dependencies [ba61adb, 6fe325d, 76c17f8]:

    • varlock@0.7.0

@varlock/keepass-plugin@0.0.2

Patch Changes

  • 6ab4fc9 - Add KeePass plugin for loading secrets from KDBX 4.0 databases.

    • kp() resolver with #attribute syntax, entry name inference from key, and customAttributesObj for bulk custom field loading
    • kpBulk() resolver for loading all passwords from a group via @setValuesBulk
    • kdbxPassword data type for master password validation
    • File mode using kdbxweb with pure WASM argon2 (no native addons, works in SEA builds)
    • CLI mode via keepassxc-cli with dynamic useCli option (e.g., useCli=forEnv(dev))
    • Multiple database instances via id param
    • Key file authentication support
    • Add input option to spawnAsync for streaming stdin to child processes
  • Updated dependencies [ba61adb, 6fe325d, 76c17f8]:

    • varlock@0.7.0

@varlock/pass-plugin@0.0.6

Patch Changes

  • #483 ba61adb - Add support for single-file ESM and TypeScript plugins, and improve the plugin authoring API.

    New: ESM and TypeScript single-file plugins

    Single-file plugins can now be written as .mjs or .ts files in addition to .js/.cjs. TypeScript plugins require Bun.

    Improved: explicit plugin import instead of injected global

    Plugin authors should now import plugin explicitly from varlock/plugin-lib rather than relying on the injected global:

    // CJS plugin (.js / .cjs)
    const { plugin } = require("varlock/plugin-lib");
    
    // ESM plugin (.mjs / .ts)
    import { plugin } from "varlock/plugin-lib";

    This works in both regular installs and SEA binary builds. Error classes (ValidationError, CoercionError, etc.) are also now directly importable from varlock/plugin-lib.

    Breaking change: the implicit plugin global is no longer injected into CJS plugin modules. Existing plugins must add const { plugin } = require('varlock/plugin-lib').

  • Updated dependencies [ba61adb, 6fe325d, 76c17f8]:

    • varlock@0.7.0

@varlock/proton-pass-plugin@0.0.3

Patch Changes

  • #483 ba61adb - Add support for single-file ESM and TypeScript plugins, and improve the plugin authoring API.

    New: ESM and TypeScript single-file plugins

    Single-file plugins can now be written as .mjs or .ts files in addition to .js/.cjs. TypeScript plugins require Bun.

    Improved: explicit plugin import instead of injected global

    Plugin authors should now import plugin explicitly from varlock/plugin-lib rather than relying on the injected global:

    // CJS plugin (.js / .cjs)
    const { plugin } = require("varlock/plugin-lib");
    
    // ESM plugin (.mjs / .ts)
    import { plugin } from "varlock/plugin-lib";

    This works in both regular installs and SEA binary builds. Error classes (ValidationError, CoercionError, etc.) are also now directly importable from varlock/plugin-lib.

    Breaking change: the implicit plugin global is no longer injected into CJS plugin modules. Existing plugins must add const { plugin } = require('varlock/plugin-lib').

  • Updated dependencies [ba61adb, 6fe325d, 76c17f8]:

    • varlock@0.7.0

@github-actions github-actions bot force-pushed the changeset-release/main branch from c5c4fba to da434c5 Compare March 31, 2026 07:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants