Version Packages (rc) - #1885
Open
arkenv-bot[bot] wants to merge 1 commit into
Open
arkenv-bot[bot] wants to merge 1 commit into
arkenv-bot[bot] wants to merge 1 commit into
Conversation
@arkenv/agent-plugin
arkenv
@arkenv/build
@arkenv/bun-plugin
@arkenv/core
@arkenv/fumadocs-ui
@arkenv/nextjs
@arkenv/nuxt
@arkenv/rsbuild-plugin
@arkenv/standard
@arkenv/tanstack-addon
@arkenv/vite-plugin
commit: |
arkenv-bot
Bot
force-pushed
the
changeset-release/v1
branch
8 times, most recently
from
September 20, 2026 11:23
2166d1d to
5d415f6
Compare
4 tasks
arkenv-bot
Bot
force-pushed
the
changeset-release/v1
branch
9 times, most recently
from
September 20, 2026 17:13
e7e909e to
56bc24d
Compare
4 tasks
arkenv-bot
Bot
force-pushed
the
changeset-release/v1
branch
from
September 20, 2026 19:22
56bc24d to
e397300
Compare
arkenv-bot
Bot
force-pushed
the
changeset-release/v1
branch
3 times, most recently
from
September 21, 2026 05:44
ada16ac to
c47cd9b
Compare
arkenv-bot
Bot
force-pushed
the
changeset-release/v1
branch
from
September 21, 2026 06:17
c1b2baf to
737e7a1
Compare
arkenv-bot
Bot
force-pushed
the
changeset-release/v1
branch
2 times, most recently
from
September 21, 2026 08:38
59cff9d to
d4526cf
Compare
arkenv-bot
Bot
force-pushed
the
changeset-release/v1
branch
from
September 21, 2026 08:44
d4526cf to
2172c2f
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 v1, this PR will be updated.
v1is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonv1.Releases
arkenv@1.0.0-rc.2
Major Changes
Remove package.json
"arkenv"schema pointer from CLI discovery#1909a98f6c0@yamcodesarkenv initno longer writes apackage.json"arkenv"field, and CLIschema discovery no longer reads one. Location is
--schema/-s, thenconvention paths (
env.ts,src/env.ts, …). Leftover"arkenv"keys areignored.
BREAKING CHANGE: If you relied on
package.json"arkenv"(string or{ "schema": "…" }) forarkenv check, put the path on--schemain yourscripts instead:
{ "scripts": { "check": "arkenv check --schema config/env.ts" } }Patch Changes
Fetch the example registry from the
v1branch#1903e6c8f78@yamcodesThe CLI example registry URL pointed at the archived
main(v0) line. It now loadsexamples/registry.jsonfromv1.@arkenv/core@1.0.0-rc.2
Patch Changes
Point StackBlitz README link at the v1 example
#1905f71bee1@yamcodesThe core package README StackBlitz badge now opens
tree/v1/examples/stackblitz, matching the v1@arkenv/coreplayground instead of the stalemainpath.@arkenv/nextjs@1.0.0-rc.2
Patch Changes
Widen the React peer dependency range
#1877c18c102@yamcodesAllow
@arkenv/nextjsto work with React 18.2.0 and later in the React 18 line,as well as every React 19 release, instead of requiring React 19.2.5. Install it
alongside a supported React version, such as
pnpm add @arkenv/nextjs react@^18.2.0.Updated 2 dependencies
f71bee1@arkenv/core@1.0.0-rc.2@arkenv/standard@1.0.0-rc.2