Skip to content

Version Packages (alpha) - #1635

Open
arkenv-bot[bot] wants to merge 2 commits into
v1from
changeset-release/v1
Open

Version Packages (alpha)#1635
arkenv-bot[bot] wants to merge 2 commits into
v1from
changeset-release/v1

Conversation

@arkenv-bot

@arkenv-bot arkenv-bot Bot commented Aug 27, 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.15

Major Changes

  • Replace --json payloads with settlement envelopes #1633 02a5a32 @yamcodes

    --json / --agent now write an ok-discriminated settlement document to stdout instead of { status, code, message, retryWith }. Human-readable output is unchanged. JSON stays on stdout; logs stay on stderr. Secret values are redacted in meta, summary, and why.

    Completed runs use ok: true (including arkenv check findings, which still set exitCode: 4). Aborts use ok: false with a dotted CLI.* or ENV.* code. nextActions is always present ([] when there is nothing to do). Commands in nextActions resolve to the invoked runner (pnpm arkenv, npx arkenv, bunx arkenv, and so on).

    Example refusal:

    {
      "ok": false,
      "commandId": "init",
      "error": {
        "code": "CLI.GIT_TREE_DIRTY",
        "severity": "error",
        "summary": "Git working tree is not clean.",
        "nextActions": [
          {
            "kind": "run-command",
            "label": "Re-run with --force to bypass this check",
            "command": "npx arkenv init --force"
          }
        ]
      },
      "diagnostics": [],
      "nextActions": [
        {
          "kind": "run-command",
          "label": "Re-run with --force to bypass this check",
          "command": "npx arkenv init --force"
        }
      ]
    }

    BREAKING CHANGE: Agents must switch from status / retryWith to ok / error.code / nextActions. Flat codes such as GIT_TREE_DIRTY are now dotted (CLI.GIT_TREE_DIRTY).

    - { "status": "error", "code": "GIT_TREE_DIRTY", "retryWith": ["--force"] }
    + { "ok": false, "error": { "code": "CLI.GIT_TREE_DIRTY", "nextActions": [{ "kind": "run-command", "command": "npx arkenv init --force" }] } }

Minor Changes

  • Add arkenv check command and cross-module validation detection #1632 01a028d @yamcodes

    • Add arkenv check CLI command to validate the active environment against the project's env schema, supporting --schema (-s), repeatable --env-file, --json, --quiet, and --agent with CI-friendly exit codes.
    • Add structural ArkErrors verification in @arkenv/core so cross-module-instance schema evaluation reliably surfaces validation issues.

Patch Changes

  • Drop default z.coerce from Zod product samples and scaffold templates #1631 ba9f903 @yamcodes

    Scaffolded Zod templates, @arkenv/standard JSDoc examples, and official example projects now declare numeric and boolean fields with z.number() and z.boolean() instead of z.coerce.number() or z.coerce.boolean(), reflecting ArkEnv's built-in pre-coercion for Standard Schema validators.

    import arkenv from "@arkenv/standard";
    import { z } from "zod";
    
    export const env = arkenv({
      PORT: z.number().default(3000),
      DATABASE_URL: z.string().url(),
      DEBUG: z.boolean().default(false),
    });
  • Align Next.js onboarding with @/.arkenv #1639 cc87d51 @yamcodes

    arkenv init now scaffolds Next.js schemas that import the codegen factory from @/.arkenv, writes that factory to .arkenv/env.gen.ts, gitignores .arkenv/, and maps the specifier in tsconfig.json. Docs, READMEs, and examples match that path instead of ./generated/env.gen.

    import arkenv from "@/.arkenv";
    
    export const env = arkenv({
      DATABASE_URL: "string",
      NEXT_PUBLIC_API_URL: "string",
    });

    Existing outputPath overrides still work. Keep importing @/.arkenv. withArkEnv aliases the specifier for bundlers, and codegen keeps .arkenv/index.ts re-exporting the file so tsc --noEmit resolves it too.

@arkenv/core@1.0.0-alpha.7

Patch Changes

  • Add arkenv check command and cross-module validation detection #1632 01a028d @yamcodes

    • Add arkenv check CLI command to validate the active environment against the project's env schema, supporting --schema (-s), repeatable --env-file, --json, --quiet, and --agent with CI-friendly exit codes.
    • Add structural ArkErrors verification in @arkenv/core so cross-module-instance schema evaluation reliably surfaces validation issues.

@arkenv/nextjs@1.0.0-alpha.13

Patch Changes

  • Align Next.js onboarding with @/.arkenv #1639 cc87d51 @yamcodes

    arkenv init now scaffolds Next.js schemas that import the codegen factory from @/.arkenv, writes that factory to .arkenv/env.gen.ts, gitignores .arkenv/, and maps the specifier in tsconfig.json. Docs, READMEs, and examples match that path instead of ./generated/env.gen.

    import arkenv from "@/.arkenv";
    
    export const env = arkenv({
      DATABASE_URL: "string",
      NEXT_PUBLIC_API_URL: "string",
    });

    Existing outputPath overrides still work. Keep importing @/.arkenv. withArkEnv aliases the specifier for bundlers, and codegen keeps .arkenv/index.ts re-exporting the file so tsc --noEmit resolves it too.

Updated 2 dependencies

01a028d ba9f903

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

Patch Changes

  • Drop default z.coerce from Zod product samples and scaffold templates #1631 ba9f903 @yamcodes

    Scaffolded Zod templates, @arkenv/standard JSDoc examples, and official example projects now declare numeric and boolean fields with z.number() and z.boolean() instead of z.coerce.number() or z.coerce.boolean(), reflecting ArkEnv's built-in pre-coercion for Standard Schema validators.

    import arkenv from "@arkenv/standard";
    import { z } from "zod";
    
    export const env = arkenv({
      PORT: z.number().default(3000),
      DATABASE_URL: z.string().url(),
      DEBUG: z.boolean().default(false),
    });

@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 27, 2026
@pkg-pr-new

pkg-pr-new Bot commented Aug 27, 2026

Copy link
Copy Markdown

Open in StackBlitz

@arkenv/agent-plugin

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

arkenv

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

@arkenv/build

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

@arkenv/bun-plugin

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

@arkenv/core

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

@arkenv/fumadocs-ui

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

@arkenv/nextjs

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

@arkenv/nuxt

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

@arkenv/standard

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

@arkenv/vite-plugin

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

commit: 075d670

@arkenv-bot
arkenv-bot Bot force-pushed the changeset-release/v1 branch 4 times, most recently from 13a98e9 to 117da1a Compare August 27, 2026 19:28
yamcodes added a commit that referenced this pull request Aug 27, 2026
The hero Valibot pane height calc exceeded Biome's CSS lineWidth, and
useLayoutEffect listed validator without reading it. Autofix then exited
1, which blocked Version Packages PR #1635.

Co-authored-by: Cursor <cursoragent@cursor.com>
@arkenv-bot
arkenv-bot Bot force-pushed the changeset-release/v1 branch 2 times, most recently from 79772dc to f7d9364 Compare August 27, 2026 20:07
@arkenv-bot
arkenv-bot Bot force-pushed the changeset-release/v1 branch from 204377c to b939902 Compare August 27, 2026 20:38
@github-actions github-actions Bot added the @arkenv/nextjs Issues or Pull Requests involving the Next.js integration for ArkEnv label Aug 27, 2026
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.

0 participants