From 7d5b69423ea45b9f27bece06efcf9a3c29b1be01 Mon Sep 17 00:00:00 2001
From: "vland-bot[bot]" <282456776+vland-bot[bot]@users.noreply.github.com>
Date: Sat, 16 May 2026 06:37:35 +0000
Subject: [PATCH] RELEASING: Releasing 1 package(s)

Releases:
  @vlandoss/env@0.2.0

[skip ci]
---
 .changeset/defu-merge-isolate-safe.md    |  9 -------
 .changeset/docs-feedback-polish.md       |  5 ----
 .changeset/envscript-rename.md           | 13 ----------
 .changeset/fs-entrypoint-rename.md       |  7 ------
 .changeset/readenv-defensive-fallback.md |  5 ----
 package/CHANGELOG.md                     | 30 ++++++++++++++++++++++++
 package/package.json                     |  2 +-
 7 files changed, 31 insertions(+), 40 deletions(-)
 delete mode 100644 .changeset/defu-merge-isolate-safe.md
 delete mode 100644 .changeset/docs-feedback-polish.md
 delete mode 100644 .changeset/envscript-rename.md
 delete mode 100644 .changeset/fs-entrypoint-rename.md
 delete mode 100644 .changeset/readenv-defensive-fallback.md

diff --git a/.changeset/defu-merge-isolate-safe.md b/.changeset/defu-merge-isolate-safe.md
deleted file mode 100644
index cb3b03b..0000000
--- a/.changeset/defu-merge-isolate-safe.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-"@vlandoss/env": patch
----
-
-Replace `lodash.merge` with [`defu`](https://github.com/unjs/defu) for the internal merge that combines `defaults + config + envOverride`. The precedence (env > config > defaults) is unchanged.
-
-This fixes a silent shallow-merge regression on V8 isolate runtimes (Cloudflare Workers, Vercel Edge, Next.js Edge): `lodash.merge` relies on `isPlainObject`, which returns `false` when the object originates from a different realm than the merger. The fallback path then assigns by reference instead of deep-merging, which caused leaf values present in `config` (e.g. `db.LOGGING: true`) to be dropped whenever `envOverride` touched the same parent branch.
-
-defu is realm-agnostic and reliably deep-merges in all the runtimes supported by the core.
diff --git a/.changeset/docs-feedback-polish.md b/.changeset/docs-feedback-polish.md
deleted file mode 100644
index a10a0e2..0000000
--- a/.changeset/docs-feedback-polish.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-"@vlandoss/env": patch
----
-
-Polish the package README to match the new docs site language — soften technical references to `process.env`, separate the optional `zod` install, and align the tagline with the rest of the documentation.
diff --git a/.changeset/envscript-rename.md b/.changeset/envscript-rename.md
deleted file mode 100644
index f2eeb44..0000000
--- a/.changeset/envscript-rename.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-"@vlandoss/env": minor
----
-
-**BREAKING** Rename `<ClientEnv />` (in `@vlandoss/env/react`) to `<EnvScript />`. The new name stops suggesting client-side use and reflects what the component actually does: emit a `<script>` tag with the server-resolved env so the browser can read it during SSR or SSG hydration. The entrypoint path (`@vlandoss/env/react`) is unchanged. The wire format is also unchanged: the DOM `id="env"` and `window.__env` global stay identical, so HTML served by an older build continues to hydrate correctly.
-
-Renames included:
-
-- Component: `ClientEnv` → `EnvScript`
-- Props: `ClientEnvProps` → `EnvScriptProps`
-- Constants: `CLIENT_ENV_SCRIPT_ID` → `ENV_SCRIPT_ID`, `CLIENT_ENV_GLOBAL_ID` → `ENV_GLOBAL_ID`
-
-Migration: replace `<ClientEnv …>` with `<EnvScript …>`. If you imported the constants from the core entrypoint, update those imports too.
diff --git a/.changeset/fs-entrypoint-rename.md b/.changeset/fs-entrypoint-rename.md
deleted file mode 100644
index 6e24051..0000000
--- a/.changeset/fs-entrypoint-rename.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-"@vlandoss/env": minor
----
-
-**BREAKING** Rename `@vlandoss/env/node` to `@vlandoss/env/fs`. The entrypoint has always been about file-system access on a Node-compatible runtime — the new name reflects that it works on Node, Bun, and Deno (not just Node), and that it does not work on Workers/Edge. The dynamic-import path resolution now uses `pathToFileURL` so Deno can load absolute paths correctly.
-
-Migration: replace `from "@vlandoss/env/node"` with `from "@vlandoss/env/fs"`.
diff --git a/.changeset/readenv-defensive-fallback.md b/.changeset/readenv-defensive-fallback.md
deleted file mode 100644
index d551a12..0000000
--- a/.changeset/readenv-defensive-fallback.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-"@vlandoss/env": patch
----
-
-`readEnv()` no longer throws `ReferenceError` on runtimes where `process` is not defined (e.g. Cloudflare Workers without `nodejs_compat`). It now returns `{}` so callers can supply the environment explicitly via `defineEnv({ runtimeEnv })` — the idiomatic pattern in Worker `fetch(req, env, ctx)` handlers. Behavior on Node, Bun, Deno, browsers, and Edge runtimes that polyfill `process.env` is unchanged.
diff --git a/package/CHANGELOG.md b/package/CHANGELOG.md
index 9a201b1..c0840d7 100644
--- a/package/CHANGELOG.md
+++ b/package/CHANGELOG.md
@@ -1,5 +1,35 @@
 # @vlandoss/env
 
+## 0.2.0
+
+### Minor Changes
+
+- [#6](https://github.com/variableland/env/pull/6) [`d150a70`](https://github.com/variableland/env/commit/d150a7006c10a240db0dd464ae4e6e8947924028) Thanks [@rqbazan](https://github.com/rqbazan)! - **BREAKING** Rename `<ClientEnv />` (in `@vlandoss/env/react`) to `<EnvScript />`. The new name stops suggesting client-side use and reflects what the component actually does: emit a `<script>` tag with the server-resolved env so the browser can read it during SSR or SSG hydration. The entrypoint path (`@vlandoss/env/react`) is unchanged. The wire format is also unchanged: the DOM `id="env"` and `window.__env` global stay identical, so HTML served by an older build continues to hydrate correctly.
+
+  Renames included:
+
+  - Component: `ClientEnv` → `EnvScript`
+  - Props: `ClientEnvProps` → `EnvScriptProps`
+  - Constants: `CLIENT_ENV_SCRIPT_ID` → `ENV_SCRIPT_ID`, `CLIENT_ENV_GLOBAL_ID` → `ENV_GLOBAL_ID`
+
+  Migration: replace `<ClientEnv …>` with `<EnvScript …>`. If you imported the constants from the core entrypoint, update those imports too.
+
+- [#6](https://github.com/variableland/env/pull/6) [`d150a70`](https://github.com/variableland/env/commit/d150a7006c10a240db0dd464ae4e6e8947924028) Thanks [@rqbazan](https://github.com/rqbazan)! - **BREAKING** Rename `@vlandoss/env/node` to `@vlandoss/env/fs`. The entrypoint has always been about file-system access on a Node-compatible runtime — the new name reflects that it works on Node, Bun, and Deno (not just Node), and that it does not work on Workers/Edge. The dynamic-import path resolution now uses `pathToFileURL` so Deno can load absolute paths correctly.
+
+  Migration: replace `from "@vlandoss/env/node"` with `from "@vlandoss/env/fs"`.
+
+### Patch Changes
+
+- [#6](https://github.com/variableland/env/pull/6) [`d150a70`](https://github.com/variableland/env/commit/d150a7006c10a240db0dd464ae4e6e8947924028) Thanks [@rqbazan](https://github.com/rqbazan)! - Replace `lodash.merge` with [`defu`](https://github.com/unjs/defu) for the internal merge that combines `defaults + config + envOverride`. The precedence (env > config > defaults) is unchanged.
+
+  This fixes a silent shallow-merge regression on V8 isolate runtimes (Cloudflare Workers, Vercel Edge, Next.js Edge): `lodash.merge` relies on `isPlainObject`, which returns `false` when the object originates from a different realm than the merger. The fallback path then assigns by reference instead of deep-merging, which caused leaf values present in `config` (e.g. `db.LOGGING: true`) to be dropped whenever `envOverride` touched the same parent branch.
+
+  defu is realm-agnostic and reliably deep-merges in all the runtimes supported by the core.
+
+- [#6](https://github.com/variableland/env/pull/6) [`d150a70`](https://github.com/variableland/env/commit/d150a7006c10a240db0dd464ae4e6e8947924028) Thanks [@rqbazan](https://github.com/rqbazan)! - Polish the package README to match the new docs site language — soften technical references to `process.env`, separate the optional `zod` install, and align the tagline with the rest of the documentation.
+
+- [#6](https://github.com/variableland/env/pull/6) [`d150a70`](https://github.com/variableland/env/commit/d150a7006c10a240db0dd464ae4e6e8947924028) Thanks [@rqbazan](https://github.com/rqbazan)! - `readEnv()` no longer throws `ReferenceError` on runtimes where `process` is not defined (e.g. Cloudflare Workers without `nodejs_compat`). It now returns `{}` so callers can supply the environment explicitly via `defineEnv({ runtimeEnv })` — the idiomatic pattern in Worker `fetch(req, env, ctx)` handlers. Behavior on Node, Bun, Deno, browsers, and Edge runtimes that polyfill `process.env` is unchanged.
+
 ## 0.1.2
 
 ### Patch Changes
diff --git a/package/package.json b/package/package.json
index ffbbfb8..7abd860 100644
--- a/package/package.json
+++ b/package/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@vlandoss/env",
-  "version": "0.1.2",
+  "version": "0.2.0",
   "description": "A simple helper to define environment-based configuration",
   "homepage": "https://github.com/variableland/env/tree/main/package#readme",
   "bugs": {