chore: Update all non-major dependencies - #274
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
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.2.0→^7.3.1^7.1.0→^7.2.1^8.1.34→^8.1.37^5.21.3→^5.22.0^1.2.123→^1.2.1261.2.127^3.15.2→^3.16.0^2.5.0→^2.5.1^4.1.0→^4.2.0^4.10.0→^4.11.0^4.1.10→^4.1.11v0.5.5→v0.6.9^10.8.1→^10.9.1^20.11.2→^20.11.1220.12.0(+3)^6.32.2→^6.32.36.33.024.19.0→24.20.011.22.0→11.24.0^2.10.3→^2.10.4^8.2.1→^8.2.2^4.1.10→^4.1.11^3.5.41→^3.5.42^3.3.10→^3.3.11Release Notes
dotansimha/graphql-code-generator (@graphql-codegen/cli)
v7.3.1Compare Source
Patch Changes
#10924
0c8f5baThanks @eddeee888! - Fix profiler output not being written to the
filesystem in watch mode (
--profile --watch)The profiler trace was only written on the non-watch code path, after the watch-mode early return,
so a profiled watch session never produced a
codegen-*.jsonfile.The profiler now writes a fresh trace file after the initial run and after every rebuild, with
each file containing only that run's events. A failed rebuild does not produce a trace and its
events are discarded so they don't leak into the next successful run.
The
Profilernow owns its own trace lifecycle:clear()method starts a new traceoutputNameproperty provides the filename for the current trace (nullfor the noopprofiler)
CodegenContextUpdated dependencies
[
0c8f5ba]:v7.3.0Compare Source
Minor Changes
#10921
58cdb31Thanks @eddeee888! - Extend
overwritewithoverwrite.removeStaleFilesandoverwrite.updateExistingFilesoverwritewas being used to both remove stale files in watch mode and update existing files.Some plugins such as Server Preset may dynamically return files to write between watch runs (for
performance purposes).
The
overwritecan now take an object withoverwrite.removeStaleFilesandoverwrite.updateExistingFilesfields to allow granular control over actions.This is not a breaking change because
overwrite=true|falsestill works.Patch Changes
[
58cdb31]:dotansimha/graphql-code-generator (@graphql-codegen/plugin-helpers)
v7.2.1Compare Source
Patch Changes
#10924
0c8f5baThanks @eddeee888! - Fix profiler output not being written to the
filesystem in watch mode (
--profile --watch)The profiler trace was only written on the non-watch code path, after the watch-mode early return,
so a profiled watch session never produced a
codegen-*.jsonfile.The profiler now writes a fresh trace file after the initial run and after every rebuild, with
each file containing only that run's events. A failed rebuild does not produce a trace and its
events are discarded so they don't leak into the next successful run.
The
Profilernow owns its own trace lifecycle:clear()method starts a new traceoutputNameproperty provides the filename for the current trace (nullfor the noopprofiler)
CodegenContextv7.2.0Compare Source
Minor Changes
#10921
58cdb31Thanks @eddeee888! - Extend
overwritewithoverwrite.removeStaleFilesandoverwrite.updateExistingFilesoverwritewas being used to both remove stale files in watch mode and update existing files.Some plugins such as Server Preset may dynamically return files to write between watch runs (for
performance purposes).
The
overwritecan now take an object withoverwrite.removeStaleFilesandoverwrite.updateExistingFilesfields to allow granular control over actions.This is not a breaking change because
overwrite=true|falsestill works.ardatan/graphql-tools (@graphql-tools/code-file-loader)
v8.1.37Compare Source
Patch Changes
[
2273c21]:v8.1.36Compare Source
Patch Changes
[
e90719b]:v8.1.35Compare Source
Patch Changes
[
615c1a2]:graphql-hive/graphql-yoga (@graphql-yoga/render-graphiql)
v5.22.0Compare Source
Patch Changes
[
94ebe5b]:nuxt/content (@nuxt/content)
v3.16.0Compare Source
Bug Fixes
hub.db(#3822) (8841abc)#content/adapterto prevent prerender failure (#3830) (400390a)nuxt/test-utils (@nuxt/test-utils)
v4.2.0Compare Source
👉 Changelog
compare changes
🚀 Enhancements
🩹 Fixes
mockNuxtImportsourcemap mapped position (#1787)setupTimeoutin playwright + surface server logs (#1785)includeSourcein both projects indefineVitestConfig(#1763)taskkillto kill processes on windows (#1760)🏡 Chore
latestranges with caret ranges (#1773)✅ Tests
🤖 CI
🎉 New Contributors
❤️ Contributors
nuxt/ui (@nuxt/ui)
v4.11.0Compare Source
Features
iconin items (#6726) (07f3fe8)experimental.componentDetection(#6731) (3a568b5)Bug Fixes
scrollable(#6786) (5afbd5c)baseinapplyUnstyled(#6825) (3e89ea7)classfrompropswith the component class (#6842) (731ff26)prefers-reduced-motion(#6742) (735b264)Performance Improvements
vitest-dev/vitest (@vitest/coverage-v8)
v4.1.11Compare Source
🐞 Bug Fixes
View changes on GitHub
danielroe/uppt (danielroe/uppt)
v0.6.9Compare Source
compare changes
🩹 Fixes
❤️ Contributors
v0.6.8Compare Source
compare changes
🚀 Enhancements
🩹 Fixes
❤️ Contributors
v0.6.7Compare Source
compare changes
🩹 Fixes
❤️ Contributors
v0.6.6Compare Source
compare changes
🩹 Fixes
❤️ Contributors
v0.6.5Compare Source
compare changes
🚀 Enhancements
🩹 Fixes
💅 Refactors
📖 Documentation
🏡 Chore
✅ Tests
❤️ Contributors
v0.6.4Compare Source
compare changes
🩹 Fixes
🏡 Chore
❤️ Contributors
v0.6.3Compare Source
compare changes
🩹 Fixes
🏡 Chore
❤️ Contributors
v0.6.2Compare Source
compare changes
🩹 Fixes
💅 Refactors
🏡 Chore
❤️ Contributors
v0.6.1Compare Source
v0.6.1)
🩹 Fixes
🏡 Chore
❤️ Contributors
v0.6.0Compare Source
compare changes
🚀 Enhancements
🩹 Fixes
🏡 Chore
🤖 CI
❤️ Contributors
eslint/eslint (eslint)
v10.9.1Compare Source
v10.9.0Compare Source
capricorn86/happy-dom (happy-dom)
v20.11.12Compare Source
👷♂️ Patch fixes
v20.11.11Compare Source
v20.11.10Compare Source
v20.11.9Compare Source
v20.11.8Compare Source
👷♂️ Patch fixes
v20.11.7Compare Source
👷♂️ Patch fixes
v20.11.6Compare Source
👷♂️ Patch fixes
v20.11.5Compare Source
v20.11.4Compare Source
v20.11.3Compare Source
👷♂️ Patch fixes
webpro-nl/knip (knip)
v6.32.3: Release 6.32.3Compare Source
9f18cba)de51629)f6964dd)68d6f52) - thanks @codeAnqiang-ma!4015ae0) - thanks @codeAnqiang-ma!deedbf6) - thanks @marcalexiei!0201641) - thanks @DSeaStar!dc7aca5) - thanks @solomonaustin!ee555d2) - thanks @kirthi-b!ff0d791) - thanks @DreamLongYT!a0c0b08) - thanks @taracutie!d1d5d42) - thanks @NimmLor!e655b0b)f4ff31a)actions/node-versions (node)
v24.20.0: 24.20.0Compare Source
Node.js 24.20.0
pnpm/pnpm (pnpm)
v11.24.0: pnpm 11.24Compare Source
Minor Changes
Patch Changes
Fixed pnpm v11 incorrectly reporting
confirmModulesPurgeas unrecognized when set inpnpm-workspace.yaml. The Rust CLI now identifies the unsupported option as a pnpm v11 setting instead of suggesting an unrelated setting.pnpm install --frozen-lockfileno longer fails withERR_PNPM_FROZEN_LOCKFILE_WITH_OUTDATED_LOCKFILEwhen the pinned pnpm version recorded inpnpm-lock.yamlhas to be re-resolved before it can be installed. It runs the pnpm version the lockfile pins and leaves the lockfile unchanged #14124.Under
nodeLinker: hoisted, peer-resolution variants of an injected directory dependency (afile:snapshot) are materialized as separate copies again instead of collapsing onto the first-seen variant. Each copy keeps its own peer-resolved dependency set, so a project pinning one peer version no longer resolves another project's variant — Bit root components with conflicting peers across injected copies rely on this.Fixed
pnpm install --merge-git-branch-lockfiles --frozen-lockfilefailing withERR_PNPM_OUTDATED_LOCKFILEwhen a branch lockfile predates the removal of a dependency, or its move to another dependency group #13966. A dependency that no project declares anymore is no longer reinstated by the merge, and the packages it was the only path to are dropped with it.Batch workspace publishing accepts a shared scope-specific credential, rejects mismatched credentials for a registry before publishing, and runs the
publishandpostpublishscripts after each completed registry group pnpm/pnpm#14101.The Rust CLI now honors five settings it recognized but ignored:
updateNotifier,legacyDirFiltering,initAuthorName/initAuthorEmail/initAuthorUrl,initLicense, andinitVersion.pnpm installandpnpm addcheck once a day for a newer pnpm and print how to get it (turn it off withupdateNotifier: false); a{<dir>}filter selector can go back to matching the subtree below the directory withlegacyDirFiltering: true; andpnpm initwrites the configured author, license, and version into thepackage.jsonit scaffolds.PNPM_CONFIG_INIT_VERSIONis now read as well.maxsockets, npm's spelling ofmaxSockets, is no longer ignored: both spellings are read frompnpm-workspace.yaml, the global config file, the environment, and the command line, in that increasing order of precedence — a value passed on the command line now wins even when the two sides spelled the setting differently.A
lastUpdateChecktimestamp dated in the future — after a clock change, a restored snapshot, or a hand-edited state file — no longer silences the update check until that time comes around.legacyDirFilteringno longer reaches the workspace-root selectors pnpm generates for itself: the!{<workspace-root>}exclusion a recursiverun/exec/add/testappends, and the{<workspace-root>}inclusion--workspace-rootappends. Read as subtree matches they named every project below the root, so a recursive command under the setting selected nothing at all, and--workspace-rootpulled in every project below the root instead of the root alone #14101.pnpm install --frozen-lockfileno longer fails whenpnpm-lock.yamlrecords the pinned pnpm version alongside an engine package the running pnpm does not install it from. An entry pinning another version is still refused, and a plain install rewrites the block #14124.v11.23.0: pnpm 11.23Compare Source
Minor Changes
pnpm config getandpnpm config listnow show the settings pnpm acts on under their documented names:registriesshows the registries pnpm resolves from, merged across every source (.npmrc,pnpm-workspace.yaml, the global config, CLI flags), in the shape the setting is written in: keyed by registry URL, with the default registry declared as the bare@scope. BuiConfiguration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 Automerge: Enabled.
♻ 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.