[Changesets] Create versioned packages for publishing

Author: github-actions[bot]

.changeset/binary-version-mismatch-check.md

@@ -1,5 +1,22 @@
 # @varlock/1password-plugin
 
+## 0.3.3
+
+### Patch Changes
+
+- [#533](https://github.com/dmno-dev/varlock/pull/533) [`0b6b2c0`](https://github.com/dmno-dev/varlock/commit/0b6b2c03ea5170f2ad1fbfa536b1b94ccf1de500) - Add support for 1Password Connect server (self-hosted)
+
+  - New auth mode: `connectHost` + `connectToken` parameters in `@initOp()` for connecting to self-hosted 1Password Connect servers
+  - Direct REST API integration — no `op` CLI or 1Password SDK required for Connect server usage
+  - New `opConnectToken` data type for Connect server API tokens
+  - Parses standard `op://vault/item/[section/]field` references and resolves them via the Connect API
+  - Caches vault and item ID lookups within a session for efficiency
+  - Clear error when `opLoadEnvironment()` is used with Connect (not supported by the Connect API)
+  - Updated error messages and tips to include Connect server as an auth option
+
+- Updated dependencies [[`74752a3`](https://github.com/dmno-dev/varlock/commit/74752a3db9459538b8ef7d984737f5bb55de17ae), [`01c9a6a`](https://github.com/dmno-dev/varlock/commit/01c9a6a5398d31d3818953dd757d3263e0cf3a36), [`1a4b0cf`](https://github.com/dmno-dev/varlock/commit/1a4b0cf4185c4152be4b39c70755316f1a8be25d), [`0c27ed1`](https://github.com/dmno-dev/varlock/commit/0c27ed10b3b77571848974a3703d77e1eabb8abd)]:
+  - varlock@0.7.2
+
 ## 0.3.2
 
 ### Patch Changes

.changeset/brave-doors-connect.md

@@ -1,7 +1,7 @@
 {
   "name": "@varlock/1password-plugin",
   "description": "Varlock plugin to load data from 1Password vaults",
-  "version": "0.3.2",
+  "version": "0.3.3",
   "type": "module",
   "homepage": "https://varlock.dev/plugins/1password/",
   "bugs": "https://github.com/dmno-dev/varlock/issues",

.changeset/fix-git-boundary-lockfile-detection.md

@@ -1,5 +1,33 @@
 # varlock
 
+## 0.7.2
+
+### Patch Changes
+
+- [#534](https://github.com/dmno-dev/varlock/pull/534) [`74752a3`](https://github.com/dmno-dev/varlock/commit/74752a3db9459538b8ef7d984737f5bb55de17ae) - Add version mismatch detection between standalone binary and local node_modules install
+
+  When 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.
+
+- [#558](https://github.com/dmno-dev/varlock/pull/558) [`01c9a6a`](https://github.com/dmno-dev/varlock/commit/01c9a6a5398d31d3818953dd757d3263e0cf3a36) - Fix plugin resolution failure in monorepo workspaces where `.git` and the lockfile coexist in the same directory.
+
+  `detectWorkspaceInfo()` was checking for a `.git` directory **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 `.git` boundary check to **before** moving up ensures the git-root directory is always scanned first.
+
+- [#547](https://github.com/dmno-dev/varlock/pull/547) [`1a4b0cf`](https://github.com/dmno-dev/varlock/commit/1a4b0cf4185c4152be4b39c70755316f1a8be25d) - Fix binary resolution in monorepos when `cwd` differs from the package root.
+
+  When importing `varlock/auto-load` (e.g. from a `playwright.config.ts` in a monorepo sub-package), VS Code and similar tools may set `process.cwd()` to the workspace root rather than the sub-package directory. This caused `execSyncVarlock` to search for the `varlock` binary starting at the workspace root and fail to find it when it was only installed in a sub-package's `node_modules/.bin`.
+
+  Two fixes are applied:
+
+  1. `execSyncVarlock` now accepts a `callerDir` option. When provided, the binary search walks up from `callerDir` before falling back to `process.cwd()`. `auto-load.ts` passes `import.meta.dirname` so the search always starts from inside the varlock package itself, which is already in the correct sub-package's `node_modules`.
+
+  2. The walk-up logic no longer throws immediately when it finds a `node_modules/.bin` directory 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.
+
+- [#550](https://github.com/dmno-dev/varlock/pull/550) [`0c27ed1`](https://github.com/dmno-dev/varlock/commit/0c27ed10b3b77571848974a3703d77e1eabb8abd) - Fix `@generateTypes` not creating variables when using a custom path with `varlock 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 that `infra` was 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.
+
 ## 0.7.1
 
 ### Patch Changes

.changeset/fix-monorepo-binary-resolution.md

@@ -1,6 +1,6 @@
 {
   "name": "varlock",
-  "version": "0.7.1",
+  "version": "0.7.2",
   "description": "AI-safe .env files: Schemas for agents, Secrets for humans.",
   "main": "index.js",
   "type": "module",