Repository navigation
fix(deps): pin dependencies - #2040
Merged
Merged
Conversation
🦋 Changeset detectedLatest commit: c9e1ca5 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
renovate
Bot
force-pushed
the
renovate/pin-dependencies
branch
3 times, most recently
from
October 9, 2026 14:46
12ace8b to
17565be
Compare
yamcodes
added a commit
that referenced
this pull request
Oct 9, 2026
<!-- CURSOR_AGENT_PR_BODY_BEGIN --> Hosted Renovate updates `package.json` and leaves `nub.lock` unchanged. CI's frozen `nub install` then exits 16 with `ERR_NUB_OUTDATED_LOCKFILE`, so every job on those PRs fails before the tests run. Autofix now runs `nub install --lockfile-only` first. That command is allowed to rewrite `nub.lock` in CI, and autofix.ci commits it when it changes. The following CI run installs from that file. `TODO(2057)` on that step tracks removing it once [renovatebot/renovate#44422](renovatebot/renovate#44422) is on the hosted Mend app. Tracking issue: #2057. After this merges, re-run the autofix workflow on the open Renovate PRs so each one picks up its lockfile: - #2050 ejs - #2049 concurrently - #2047 `@testing-library/jest-dom` - #2044 `@ark/util` - #2040 pin dependencies - #2039 pin `@types/react` - #2033 vite - #2032 nuxt - #2031 postcss #1862 is already green. <!-- CURSOR_AGENT_PR_BODY_END --> <div><a href="https://cursor.com/agents/bc-e611d05f-b29d-45ff-bb31-b4388577036b?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a href="https://cursor.com/background-agent?bcId=bc-e611d05f-b29d-45ff-bb31-b4388577036b&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> </div> --------- Co-authored-by: Cursor Agent <[email protected]>
yamcodes
added a commit
that referenced
this pull request
Oct 9, 2026
<!-- CURSOR_AGENT_PR_BODY_BEGIN --> Autofix rewrites `nub.lock` with `nub install --lockfile-only`, then the other jobs can install. That rewrite aborts when the resolve wants a version younger than 24 hours (`ERR_NUB_NO_MATURE_MATCHING_VERSION`). On #2040 that version is `[email protected]`. Autofix never commits the lockfile, so `pkg-pr-new`, `check-sync`, and the test jobs stay on `ERR_NUB_OUTDATED_LOCKFILE`. This passes `--minimum-release-age=0` on that refresh only, which is the off switch Nub documents for the age gate. The following `nub install` in the same job, and every other workflow, still use the normal gate. `TODO(2057)` covers removing the step, including this flag, once [renovatebot/renovate#44422](renovatebot/renovate#44422) is on the hosted Mend app. After this merges, re-run autofix on #2040. The follow-up run is the one that can install. <!-- CURSOR_AGENT_PR_BODY_END --> <div><a href="https://cursor.com/agents/bc-e611d05f-b29d-45ff-bb31-b4388577036b?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a href="https://cursor.com/background-agent?bcId=bc-e611d05f-b29d-45ff-bb31-b4388577036b&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> </div> Co-authored-by: Cursor Agent <[email protected]>
renovate
Bot
force-pushed
the
renovate/pin-dependencies
branch
from
October 9, 2026 18:16
b7e697a to
ce877b6
Compare
@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: |
Contributor
📦 Bundle Size Report✅ All size limits passed! |
renovate
Bot
force-pushed
the
renovate/pin-dependencies
branch
from
October 9, 2026 19:12
0b39e4e to
b69c1dc
Compare
renovate
Bot
force-pushed
the
renovate/pin-dependencies
branch
from
October 10, 2026 03:19
36d90f8 to
46da678
Compare
Contributor
Author
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
Nuxt 4.6 types nitro:config as NitroConfig, which falls back to NitroConfigFallback and no longer allows a second hook declaration. Keep registering the server boot alias without redeclaring the hook. Co-authored-by: Yam Borodetsky <[email protected]>
Pin fumadocs-typescript to 5.4.1 so it stays compatible with fumadocs-core 16.15.14, and sync the Nuxt and SolidStart example manifests with the pinned playgrounds. Co-authored-by: Yam Borodetsky <[email protected]>
Keep the Nuxt 4.6 hook fix and the fumadocs-typescript 5.4.1 pin on top of the chokidar and fumadocs-mdx updates. Co-authored-by: Yam Borodetsky <[email protected]>
Merged
yamcodes
pushed a commit
that referenced
this pull request
Oct 10, 2026
This PR was opened by the [Changesets release](https://github.com/changesets/action) 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/[email protected] ### Patch Changes - #### Include 1.0.0 prereleases in framework plugin core peers _[`#2069`](#2069) [`222d8e9`](222d8e9) [@yamcodes](https://github.com/yamcodes)_ Optional `@arkenv/core` and `@arkenv/standard` peers on the Next.js, Nuxt, Vite, Bun, and Rsbuild plugins now use `^1.0.0-0`. Installing a plugin together with `@arkenv/[email protected]` and `@arkenv/[email protected]` resolves on npm 11. The peers stay optional. The range matches `1.0.0` prereleases and stable 1.x below `2.0.0`. ```bash npm install @arkenv/nuxt @arkenv/[email protected] @arkenv/[email protected] ``` ```json { "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 _[`#2069`](#2069) [`222d8e9`](222d8e9) [@yamcodes](https://github.com/yamcodes)_ Optional `@arkenv/core` and `@arkenv/standard` peers on the Next.js, Nuxt, Vite, Bun, and Rsbuild plugins now use `^1.0.0-0`. Installing a plugin together with `@arkenv/[email protected]` and `@arkenv/[email protected]` resolves on npm 11. The peers stay optional. The range matches `1.0.0` prereleases and stable 1.x below `2.0.0`. ```bash npm install @arkenv/nuxt @arkenv/[email protected] @arkenv/[email protected] ``` ```json { "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 _[`#2069`](#2069) [`222d8e9`](222d8e9) [@yamcodes](https://github.com/yamcodes)_ Optional `@arkenv/core` and `@arkenv/standard` peers on the Next.js, Nuxt, Vite, Bun, and Rsbuild plugins now use `^1.0.0-0`. Installing a plugin together with `@arkenv/[email protected]` and `@arkenv/[email protected]` resolves on npm 11. The peers stay optional. The range matches `1.0.0` prereleases and stable 1.x below `2.0.0`. ```bash npm install @arkenv/nuxt @arkenv/[email protected] @arkenv/[email protected] ``` ```json { "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 _[`#2073`](#2073) [`f882c42`](f882c42) [@yamcodes](https://github.com/yamcodes)_ Production startup and prerender now validate the schema compiled into the server bundle. A copied `.output` directory no longer reads the build-machine `env.ts` and no longer needs `jiti`. Live `NUXT_*` and `NUXT_PUBLIC_*` overrides, including empty strings, still win over values baked at build time. - #### Fix Nuxt 4.6 `nitro:config` hook types _[`#2040`](#2040) [`17ff351`](17ff351) [@renovate](https://github.com/apps/renovate)_ `@arkenv/nuxt` typechecks again with Nuxt 4.6. The module no longer redeclares the `nitro:config` hook, which now uses Nuxt's `NitroConfig` type, 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 _[`#2069`](#2069) [`222d8e9`](222d8e9) [@yamcodes](https://github.com/yamcodes)_ Optional `@arkenv/core` and `@arkenv/standard` peers on the Next.js, Nuxt, Vite, Bun, and Rsbuild plugins now use `^1.0.0-0`. Installing a plugin together with `@arkenv/[email protected]` and `@arkenv/[email protected]` resolves on npm 11. The peers stay optional. The range matches `1.0.0` prereleases and stable 1.x below `2.0.0`. ```bash npm install @arkenv/nuxt @arkenv/[email protected] @arkenv/[email protected] ``` ```json { "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 _[`#2069`](#2069) [`222d8e9`](222d8e9) [@yamcodes](https://github.com/yamcodes)_ Optional `@arkenv/core` and `@arkenv/standard` peers on the Next.js, Nuxt, Vite, Bun, and Rsbuild plugins now use `^1.0.0-0`. Installing a plugin together with `@arkenv/[email protected]` and `@arkenv/[email protected]` resolves on npm 11. The peers stay optional. The range matches `1.0.0` prereleases and stable 1.x below `2.0.0`. ```bash npm install @arkenv/nuxt @arkenv/[email protected] @arkenv/[email protected] ``` ```json { "peerDependencies": { "@arkenv/core": "^1.0.0-0", "@arkenv/standard": "^1.0.0-0" }, "peerDependenciesMeta": { "@arkenv/core": { "optional": true }, "@arkenv/standard": { "optional": true } } } ``` Co-authored-by: arkenv-bot[bot] <237618717+arkenv-bot[bot]@users.noreply.github.com>
Closed
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 contains the following updates:
^7.29.7→7.29.7^10.0.1→10.0.1^0.2.1→0.2.1^0.2.2→0.2.2^0.2.0→0.2.0^0.3.1→0.3.1^4.4.8→4.6.1^4.4.8→4.6.1^0.2.3→0.2.4^2.0.4→2.0.6^0.70.0→0.70.1^7.20.5→7.20.5^3.1.5→3.1.5^0.0.32→0.0.32^6.0.1→6.1.2^1.0.0→1.0.0^10.0.0→10.0.6^6.0.0→6.0.1^10.2.1→10.12.0^7.1.1→7.1.1^0.5.2→0.5.7^5.2.6→5.5.1^1.7.2→1.7.2^17.5.0→17.13.0^2.13.1→2.13.4^4.5.1→4.6.1^4.5.1→4.6.1^5.0.5→5.0.5^1.2.2→1.2.2^8.58.2→8.71.1Add the preset
:preserveSemverRangesto your config if you don't want to pin your dependencies.Configuration
📅 Schedule: (in timezone Asia/Almaty)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.