Open
Conversation
varlock
@varlock/astro-integration
@varlock/cloudflare-integration
@varlock/expo-integration
@varlock/nextjs-integration
@varlock/vite-integration
@varlock/1password-plugin
@varlock/aws-secrets-plugin
@varlock/azure-key-vault-plugin
@varlock/bitwarden-plugin
@varlock/dashlane-plugin
@varlock/google-secret-manager-plugin
@varlock/hashicorp-vault-plugin
@varlock/infisical-plugin
@varlock/keepass-plugin
@varlock/pass-plugin
@varlock/passbolt-plugin
@varlock/proton-pass-plugin
commit: |
commit: |
8fd8e38 to
d867d51
Compare
d867d51 to
d742d59
Compare
d742d59 to
889d8e3
Compare
889d8e3 to
28c7585
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.8.0
Minor Changes
#560
0ea6641- Addvarlock explain ITEM_KEYcommand and override indicators invarlock loadoutput.Override indicators: When a config item's value comes from a
process.envoverride rather than its file-based definitions,varlock loadnow shows a yellow indicator on that item. This helps users understand why their resolver functions (e.g.op()) are not being called.varlock explaincommand: Shows detailed information about how a single config item is resolved, including all definitions and sources in priority order, which source is active, whether a process.env override is in effect (and what would be used without it), decorators, type info, and documentation links.Patch Changes
#534
74752a3- Add version mismatch detection between standalone binary and local node_modules installWhen running the standalone binary (installed via homebrew/curl), varlock now checks if a different version is installed in the project's node_modules. If a version mismatch is detected, a warning is displayed suggesting users update the binary or use the locally installed version instead. This helps prevent confusing errors caused by running mismatched versions.
#553
6ab2d31- Fix diamond dependency handling when the same schema is imported via multiple paths. Previously, duplicate imports caused plugin init decorators to run twice ("Instance already initialized" error). Now, duplicate imports create lightweightImportAliasSourcenodes that appear at the correct precedence position without re-initializing the source. This correctly handles different importKeys subsets across import sites and preserves override semantics matching non-deduplicated behavior. Also addstypefield to serialized source entries for easier filtering.#558
01c9a6a- Fix plugin resolution failure in monorepo workspaces where.gitand the lockfile coexist in the same directory.detectWorkspaceInfo()was checking for a.gitdirectory after moving to the parent, so in the standard monorepo layout (monorepo-root/.git+monorepo-root/bun.lock) the root was never scanned and the lockfile was never found. Moving the.gitboundary check to before moving up ensures the git-root directory is always scanned first.#547
1a4b0cf- Fix binary resolution in monorepos whencwddiffers from the package root.When importing
varlock/auto-load(e.g. from aplaywright.config.tsin a monorepo sub-package), VS Code and similar tools may setprocess.cwd()to the workspace root rather than the sub-package directory. This causedexecSyncVarlockto search for thevarlockbinary starting at the workspace root and fail to find it when it was only installed in a sub-package'snode_modules/.bin.Two fixes are applied:
execSyncVarlocknow accepts acallerDiroption. When provided, the binary search walks up fromcallerDirbefore falling back toprocess.cwd().auto-load.tspassesimport.meta.dirnameso the search always starts from inside the varlock package itself, which is already in the correct sub-package'snode_modules.The walk-up logic no longer throws immediately when it finds a
node_modules/.bindirectory that does not contain varlock. It now continues walking up, allowing the search to find varlock installed at a higher or lower level of a monorepo.#542
02e82d0- Fix Vitest workspace projects in monorepos: when running Vitest from the monorepo root using theprojectsconfig, varlock now correctly resolves.env.schemaand.envfiles from each child package's directory instead of only looking in the monorepo root.#550
0c27ed1- Fix@generateTypesnot creating variables when using a custom path withvarlock typegen --path <file>When a schema file with an environment-qualifier-like name (e.g.
.env.infra.schema) was passed as the explicit entry point via--path, its variables were being excluded from type generation. The filename was parsed such thatinfrawas treated as an environment name (applyForEnv='infra'), causing the data source to be marked as environment-specific and all its variables to be filtered out.The fix ensures that a file loaded as the root entry point (no parent data source) is never treated as environment-specific, even if its filename contains an environment qualifier.
@varlock/astro-integration@0.2.8
Patch Changes
74752a3,0ea6641,6ab2d31,01c9a6a,1a4b0cf,02e82d0,0c27ed1]:@varlock/cloudflare-integration@0.0.2
Patch Changes
74752a3,0ea6641,6ab2d31,01c9a6a,1a4b0cf,02e82d0,0c27ed1]:@varlock/expo-integration@0.0.2
Patch Changes
74752a3,0ea6641,6ab2d31,01c9a6a,1a4b0cf,02e82d0,0c27ed1]:@varlock/nextjs-integration@0.3.3
Patch Changes
#553
6ab2d31- Fix diamond dependency handling when the same schema is imported via multiple paths. Previously, duplicate imports caused plugin init decorators to run twice ("Instance already initialized" error). Now, duplicate imports create lightweightImportAliasSourcenodes that appear at the correct precedence position without re-initializing the source. This correctly handles different importKeys subsets across import sites and preserves override semantics matching non-deduplicated behavior. Also addstypefield to serialized source entries for easier filtering.Updated dependencies [
74752a3,0ea6641,6ab2d31,01c9a6a,1a4b0cf,02e82d0,0c27ed1]:@varlock/vite-integration@0.2.10
Patch Changes
#542
02e82d0- Fix Vitest workspace projects in monorepos: when running Vitest from the monorepo root using theprojectsconfig, varlock now correctly resolves.env.schemaand.envfiles from each child package's directory instead of only looking in the monorepo root.Updated dependencies [
74752a3,0ea6641,6ab2d31,01c9a6a,1a4b0cf,02e82d0,0c27ed1]:@varlock/1password-plugin@0.3.3
Patch Changes
#533
0b6b2c0- Add support for 1Password Connect server (self-hosted)connectHost+connectTokenparameters in@initOp()for connecting to self-hosted 1Password Connect serversopCLI or 1Password SDK required for Connect server usageopConnectTokendata type for Connect server API tokensop://vault/item/[section/]fieldreferences and resolves them via the Connect APIopLoadEnvironment()is used with Connect (not supported by the Connect API)Updated dependencies [
74752a3,0ea6641,6ab2d31,01c9a6a,1a4b0cf,02e82d0,0c27ed1]:@varlock/aws-secrets-plugin@0.0.7
Patch Changes
74752a3,0ea6641,6ab2d31,01c9a6a,1a4b0cf,02e82d0,0c27ed1]:@varlock/azure-key-vault-plugin@0.0.7
Patch Changes
74752a3,0ea6641,6ab2d31,01c9a6a,1a4b0cf,02e82d0,0c27ed1]:@varlock/bitwarden-plugin@0.0.7
Patch Changes
74752a3,0ea6641,6ab2d31,01c9a6a,1a4b0cf,02e82d0,0c27ed1]:@varlock/dashlane-plugin@0.0.2
Patch Changes
74752a3,0ea6641,6ab2d31,01c9a6a,1a4b0cf,02e82d0,0c27ed1]:@varlock/google-secret-manager-plugin@0.2.2
Patch Changes
74752a3,0ea6641,6ab2d31,01c9a6a,1a4b0cf,02e82d0,0c27ed1]:@varlock/hashicorp-vault-plugin@0.0.5
Patch Changes
74752a3,0ea6641,6ab2d31,01c9a6a,1a4b0cf,02e82d0,0c27ed1]:@varlock/infisical-plugin@0.0.7
Patch Changes
74752a3,0ea6641,6ab2d31,01c9a6a,1a4b0cf,02e82d0,0c27ed1]:@varlock/keepass-plugin@0.0.3
Patch Changes
74752a3,0ea6641,6ab2d31,01c9a6a,1a4b0cf,02e82d0,0c27ed1]:@varlock/pass-plugin@0.0.7
Patch Changes
74752a3,0ea6641,6ab2d31,01c9a6a,1a4b0cf,02e82d0,0c27ed1]:@varlock/passbolt-plugin@0.0.2
Patch Changes
74752a3,0ea6641,6ab2d31,01c9a6a,1a4b0cf,02e82d0,0c27ed1]:@varlock/proton-pass-plugin@0.0.4
Patch Changes
74752a3,0ea6641,6ab2d31,01c9a6a,1a4b0cf,02e82d0,0c27ed1]: