Repository navigation
Version Packages (rc) - #2077
Closed
arkenv-bot[bot] wants to merge 1 commit into
Closed
arkenv-bot[bot] wants to merge 1 commit into
arkenv-bot[bot] wants to merge 1 commit into
Conversation
Owner
|
Closing, release is already in action |
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/[email protected]
Patch Changes
Include 1.0.0 prereleases in framework plugin core peers
#2069222d8e9@yamcodesOptional
@arkenv/coreand@arkenv/standardpeers on the Next.js, Nuxt,Vite, Bun, and Rsbuild plugins now use
^1.0.0-0. Installing a plugintogether with
@arkenv/[email protected]and@arkenv/[email protected]resolves on npm 11. The peers stay optional. The range matches
1.0.0prereleases and stable 1.x below
2.0.0.{ "peerDependencies": { "@arkenv/core": "^1.0.0-0", "@arkenv/standard": "^1.0.0-0" }, "peerDependenciesMeta": { "@arkenv/core": { "optional": true }, "@arkenv/standard": { "optional": true } } }@arkenv/[email protected]
Patch Changes
Include 1.0.0 prereleases in framework plugin core peers
#2069222d8e9@yamcodesOptional
@arkenv/coreand@arkenv/standardpeers on the Next.js, Nuxt,Vite, Bun, and Rsbuild plugins now use
^1.0.0-0. Installing a plugintogether with
@arkenv/[email protected]and@arkenv/[email protected]resolves on npm 11. The peers stay optional. The range matches
1.0.0prereleases and stable 1.x below
2.0.0.{ "peerDependencies": { "@arkenv/core": "^1.0.0-0", "@arkenv/standard": "^1.0.0-0" }, "peerDependenciesMeta": { "@arkenv/core": { "optional": true }, "@arkenv/standard": { "optional": true } } }@arkenv/[email protected]
Patch Changes
Include 1.0.0 prereleases in framework plugin core peers
#2069222d8e9@yamcodesOptional
@arkenv/coreand@arkenv/standardpeers on the Next.js, Nuxt,Vite, Bun, and Rsbuild plugins now use
^1.0.0-0. Installing a plugintogether with
@arkenv/[email protected]and@arkenv/[email protected]resolves on npm 11. The peers stay optional. The range matches
1.0.0prereleases and stable 1.x below
2.0.0.{ "peerDependencies": { "@arkenv/core": "^1.0.0-0", "@arkenv/standard": "^1.0.0-0" }, "peerDependenciesMeta": { "@arkenv/core": { "optional": true }, "@arkenv/standard": { "optional": true } } }Compile the Nuxt schema into the Nitro server bundle
#2073f882c42@yamcodesProduction startup and prerender now validate the schema compiled into the server bundle. A copied
.outputdirectory no longer reads the build-machineenv.tsand no longer needsjiti. LiveNUXT_*andNUXT_PUBLIC_*overrides, including empty strings, still win over values baked at build time.Fix Nuxt 4.6
nitro:confighook types#204017ff351@renovate@arkenv/nuxttypechecks again with Nuxt 4.6. The module no longer redeclares thenitro:confighook, which now uses Nuxt'sNitroConfigtype, and still registers the server boot alias on that hook.@arkenv/[email protected]
Patch Changes
Include 1.0.0 prereleases in framework plugin core peers
#2069222d8e9@yamcodesOptional
@arkenv/coreand@arkenv/standardpeers on the Next.js, Nuxt,Vite, Bun, and Rsbuild plugins now use
^1.0.0-0. Installing a plugintogether with
@arkenv/[email protected]and@arkenv/[email protected]resolves on npm 11. The peers stay optional. The range matches
1.0.0prereleases and stable 1.x below
2.0.0.{ "peerDependencies": { "@arkenv/core": "^1.0.0-0", "@arkenv/standard": "^1.0.0-0" }, "peerDependenciesMeta": { "@arkenv/core": { "optional": true }, "@arkenv/standard": { "optional": true } } }@arkenv/[email protected]
Patch Changes
Include 1.0.0 prereleases in framework plugin core peers
#2069222d8e9@yamcodesOptional
@arkenv/coreand@arkenv/standardpeers on the Next.js, Nuxt,Vite, Bun, and Rsbuild plugins now use
^1.0.0-0. Installing a plugintogether with
@arkenv/[email protected]and@arkenv/[email protected]resolves on npm 11. The peers stay optional. The range matches
1.0.0prereleases and stable 1.x below
2.0.0.{ "peerDependencies": { "@arkenv/core": "^1.0.0-0", "@arkenv/standard": "^1.0.0-0" }, "peerDependenciesMeta": { "@arkenv/core": { "optional": true }, "@arkenv/standard": { "optional": true } } }