Skip to content

Version Packages (alpha) - #1629

Merged
yamcodes merged 1 commit into
v1from
changeset-release/v1
Aug 27, 2026
Merged

Version Packages (alpha)#1629
yamcodes merged 1 commit into
v1from
changeset-release/v1

Conversation

@arkenv-bot

@arkenv-bot arkenv-bot Bot commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

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 v1, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

v1 is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on v1.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

arkenv@1.0.0-alpha.14

Minor Changes

  • Add @arkenv/standard/valibot and @arkenv/standard/zod-mini subpaths #1623 6d2e3c7 @yamcodes

    Valibot and Zod Mini now have first-class imports that bind JSON Schema converters, so v.number() / Mini z.boolean() coerce without a manual toJsonSchema callback. Root @arkenv/standard stays dependency-free. arkenv init scaffolds @arkenv/standard/valibot for Valibot.

    import { arkenv } from "@arkenv/standard/valibot";
    import * as v from "valibot";
    
    export const env = arkenv({
      PORT: v.optional(v.number(), 3000),
      DEBUG: v.optional(v.boolean(), false),
    });
    import { arkenv } from "@arkenv/standard/zod-mini";
    import * as z from "zod/mini";
    
    export const env = arkenv({
      PORT: z.number(),
      DEBUG: z.boolean(),
    });

    Install @valibot/to-json-schema when using the Valibot subpath, and zod when using the Zod Mini subpath (both optional peers). TypeScript must use moduleResolution: "bundler" | "node16" | "nodenext".

Patch Changes

  • Load env.ts without a populated environment #1622 a735e9a @yamcodes

    The CLI can now import a project's flat env.ts and read declared keys even when the environment is empty.

@arkenv/nextjs@1.0.0-alpha.12

Minor Changes

  • Support function-form next.config in withArkEnv #1621 f079663 @yamcodes

    withArkEnv now accepts Next.js function-form configs (sync or async). The wrapper awaits the user's factory with the phase and context Next.js provides, then applies strict-layout and .arkenv/ aliases to the resolved object.

    import { withArkEnv } from "@arkenv/nextjs/config";
    
    export default withArkEnv(async (phase, { defaultConfig }) => ({
      ...defaultConfig,
      reactStrictMode: phase !== "phase-test",
    }));

Patch Changes

Updated 2 dependencies

a735e9a 6d2e3c7

  • @arkenv/core@1.0.0-alpha.6
  • @arkenv/standard@1.0.0-alpha.6
## @arkenv/standard@1.0.0-alpha.6

Minor Changes

  • Add @arkenv/standard/valibot and @arkenv/standard/zod-mini subpaths #1623 6d2e3c7 @yamcodes

    Valibot and Zod Mini now have first-class imports that bind JSON Schema converters, so v.number() / Mini z.boolean() coerce without a manual toJsonSchema callback. Root @arkenv/standard stays dependency-free. arkenv init scaffolds @arkenv/standard/valibot for Valibot.

    import { arkenv } from "@arkenv/standard/valibot";
    import * as v from "valibot";
    
    export const env = arkenv({
      PORT: v.optional(v.number(), 3000),
      DEBUG: v.optional(v.boolean(), false),
    });
    import { arkenv } from "@arkenv/standard/zod-mini";
    import * as z from "zod/mini";
    
    export const env = arkenv({
      PORT: z.number(),
      DEBUG: z.boolean(),
    });

    Install @valibot/to-json-schema when using the Valibot subpath, and zod when using the Zod Mini subpath (both optional peers). TypeScript must use moduleResolution: "bundler" | "node16" | "nodenext".

Patch Changes

  • Record the schema without reading the environment when a tool is inspecting it #1622 a735e9a @yamcodes

    arkenv() now records the definition object instead of validating process.env when the ArkEnv CLI (or another in-process tool) is inspecting the schema. App validation is unchanged.

@arkenv/agent-plugin@0.0.1-alpha.0

Patch Changes

  • Add a coding-agent plugin with MCP init and audit tools #1624 da7419e @yamcodes

    @arkenv/agent-plugin is now available for coding agents. Install it with
    npx plugins add yamcodes/arkenv. Compatible runtimes expose /arkenv:init
    (delegates to arkenv init --agent) and /arkenv:audit (TypeScript AST scan
    for raw process.env / import.meta.env access, client secret leaks, public
    prefix mistakes, and leftover v0 ambient .d.ts augmentations).

    The stdio MCP server is available after publish:

    npx -y @arkenv/agent-plugin@alpha

    Audit a tree programmatically:

    import { auditProject } from "@arkenv/agent-plugin";
    
    const { diagnostics } = await auditProject(".");

@arkenv/core@1.0.0-alpha.6

Patch Changes

  • Record the schema without reading the environment when a tool is inspecting it #1622 a735e9a @yamcodes

    arkenv() now records the definition object instead of validating process.env when the ArkEnv CLI (or another in-process tool) is inspecting the schema. App validation is unchanged.

@github-actions github-actions Bot added docs Adds or changes documentation, or acts as documentation in and of itself arkenv Changes to the `arkenv` npm package. labels Aug 26, 2026
@pkg-pr-new

pkg-pr-new Bot commented Aug 26, 2026

Copy link
Copy Markdown

Open in StackBlitz

@arkenv/agent-plugin

npm i https://pkg.pr.new/yamcodes/arkenv/@arkenv/agent-plugin@1629

arkenv

npm i https://pkg.pr.new/yamcodes/arkenv@1629

@arkenv/build

npm i https://pkg.pr.new/yamcodes/arkenv/@arkenv/build@1629

@arkenv/bun-plugin

npm i https://pkg.pr.new/yamcodes/arkenv/@arkenv/bun-plugin@1629

@arkenv/core

npm i https://pkg.pr.new/yamcodes/arkenv/@arkenv/core@1629

@arkenv/fumadocs-ui

npm i https://pkg.pr.new/yamcodes/arkenv/@arkenv/fumadocs-ui@1629

@arkenv/nextjs

npm i https://pkg.pr.new/yamcodes/arkenv/@arkenv/nextjs@1629

@arkenv/nuxt

npm i https://pkg.pr.new/yamcodes/arkenv/@arkenv/nuxt@1629

@arkenv/standard

npm i https://pkg.pr.new/yamcodes/arkenv/@arkenv/standard@1629

@arkenv/vite-plugin

npm i https://pkg.pr.new/yamcodes/arkenv/@arkenv/vite-plugin@1629

commit: f269723

@arkenv-bot
arkenv-bot Bot force-pushed the changeset-release/v1 branch from 367e187 to 6104ba3 Compare August 26, 2026 21:04
@github-actions github-actions Bot added the @arkenv/nextjs Issues or Pull Requests involving the Next.js integration for ArkEnv label Aug 26, 2026
@arkenv-bot
arkenv-bot Bot force-pushed the changeset-release/v1 branch 3 times, most recently from 3e75a9d to 4e5bdc7 Compare August 26, 2026 23:11
@arkenv-bot
arkenv-bot Bot force-pushed the changeset-release/v1 branch from f269723 to 5227162 Compare August 27, 2026 00:06
@yamcodes
yamcodes merged commit 27e5d9a into v1 Aug 27, 2026
16 of 17 checks passed
@yamcodes
yamcodes deleted the changeset-release/v1 branch August 27, 2026 00:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

@arkenv/nextjs Issues or Pull Requests involving the Next.js integration for ArkEnv arkenv Changes to the `arkenv` npm package. docs Adds or changes documentation, or acts as documentation in and of itself

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant