chore(deps): update all non-major dependencies - #73
Merged
Conversation
✅ Deploy Preview for vite-plugin-registry ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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:
^1.2.119→^1.2.121^14.3.0→^14.4.0^0.60.0→^0.61.0^1.75.0→^1.76.011.17.0→11.18.0^8.1.5→^8.2.02.0.0-alpha.18→2.0.0-alpha.19^1.7.5→^1.7.6v0.6.1→v0.6.2Release Notes
vueuse/vueuse (@vueuse/core)
v14.4.0Compare Source
🚀 Features
useColorModeauto import if@nuxtjs/color-modeis detected - by @OrbisK in #5476 (60687)onStartTyping- by @LightQuanta and @9romise in #5395 (1f2b7)behavior,blockandinlineto exposed scrollTo method - by @laurens94, @OrbisK, @43081j and @ilyaliao in #4905 (01875)🐞 Bug Fixes
PUREannotation to avoid Rollup warning - by @serkodev and @9romise in #5388 (16933)tryOnScopeDisposeto avoid operating Vue internal API - by @liangmiQwQ in #5548 (2cad7)View changes on GitHub
oxc-project/oxc (oxfmt)
v0.61.0Compare Source
oxc-project/oxc (oxlint)
v1.76.0Compare Source
🚀 Features
8d31dfalinter: Verify eslint/no-restricted-globals config schema (#24598) (vigneshwar)7069621linter: Verify jest/vitest prefer-lowercase-title config schema (#24724) (Bartok)016cf2alinter/oxc: Add bad-match-all-arg rule (#24900) (camc314)cdc941elinter/n: Implementexports-stylerule (#24087) (Mikhail Baev)1ad6f6clinter/eslint: Implementid-denylistrule (#24632) (Mikhail Baev)📚 Documentation
3ff2e0elinter: Clarify config extends types (#24936) (Boshen)pnpm/pnpm (pnpm)
v11.18.0: pnpm 11.18Compare Source
Minor Changes
Fixed an installed optional dependency being left without one of its own required dependencies. When a package reached through
optionalDependenciesis installable on the current system but one of its regulardependenciesis not, a lockfile-based install skipped that dependency and installed the parent anyway, so importing the parent failed withMODULE_NOT_FOUND. The dependency is now installed, and an install-check warning reports the incompatibility. A dependency is still only skipped when every path to it is optional, or when the package that pulls it in was itself skipped #13286.pnpm setupnow appendsPNPM_HOMEand the global bin directory to the GitHub Actions environment files (GITHUB_ENVandGITHUB_PATH), so later steps in the same job can runpnpm add --globaland other global commands #9191.Added support for
publishConfig.name, which publishes a package under a different name than the one its manifest carries in the workspace. It is for a project whose published name is already taken by a sibling project, which otherwise has to be renamed by a build step just before publishing. Only the published artifact is renamed — dependents,pnpm-lock.yaml, and release tooling keep addressing the project by its manifest name — and the new name reaches the packed manifest, the tarball filename, and everything that addresses the package at the registry: the already-published check ofpnpm publish -r, its registry selection, and the release-planning probes ofpnpm change statusandpnpm version -r#13345.pnpm self-updateno longer takes any instruction from the project it is run in:.npmrcorpnpm-workspace.yamlcan no longer redirect the download or attach credentials to it, and the project's default.pnpmfile.(c|m)jsis no longer loaded. Pnpmfiles from trusted sources (thepnpmfilesetting, the global pnpmfile, config dependencies) still apply.minimumReleaseAgesettings inpnpm-workspace.yamlno longer affectself-update. They still govern the project's own dependencies; forself-updatethe cooldown now comes from the built-in default, your global config, aPNPM_CONFIG_*environment variable, or a command-line flag. This fixesself-updatefailing inside a workspace that raises the cutoff while succeeding everywhere else, and stops a repository from either waiving the cooldown or keeping you on an outdated pnpm by raising it.trustPolicysettings and toci: a project can no longer weaken the trust check that guards the pnpm download, nor re-enable the confirmation prompt that a CI run suppresses.When
self-updaterefuses a version that is younger than the cutoff, an interactive run now offers to update anyway; non-interactive runs still fail. CI never prompts, even on a runner that attaches a TTY.Patch Changes
Fixed
pnpm licenses listto report every version when the same package is installed under multiple aliases pnpm/pnpm#13438.Sort
pnpm dedupe --checksnapshot changes for stable output across pnpm implementations.Strip Unicode formatting characters from registry- and manifest-derived terminal output.
Speed up installs after compatible catalog or direct dependency range changes by retaining the locked version without resolving the dependency graph again.
Speed up installs after safe override changes by reusing unambiguous compatible dependency resolutions, pruning obsolete dependencies, applying independent replacements and removals together, and handling parent-scoped
"-"overrides without full lockfile resolution.Installing a local
file:directory dependency with the global virtual store enabled no longer fails withTypeError: Cannot read properties of undefined (reading 'split')#13335.Local directory dependencies —
file:directories and injected workspace packages — now get a global-virtual-store slot of their own per project. They used to share one slot across every project that depended on a directory of the same name, so a project could end up linked to another project's copy of the dependency.The
Workspacecolumn ofpnpm update --interactivenow falls back to the project's path when itsnameis only whitespace, as it already did for a missing or empty one — all three render an equally blank label otherwise.Checking GitHub Actions dependencies for updates is now opt-in for every command. Neither
pnpm outdatednorpnpm updatereads the workflow files unless--include-github-actionsis passed orupdate.githubActionsis set totrueinpnpm-workspace.yaml. Reading them runsgit ls-remoteagainst every referenced repository, which fails in environments where GitHub is not reachable the way pnpm assumes (a GitHub Enterprise Server, a custom certificate authority, or an offline network) #13254.pnpm outdatedaccepts the--include-github-actionsoption too.pnpm update --interactivenow measures its table in terminal columns rather than in characters. A package name, workspace name, or version containing wide characters (CJK, most emoji) no longer knocks its row's columns out of line with the rest of the group, and a wide character in a version no longer aborts the command withSubject parameter value width cannot be greater than the container width#13357.The
Workspacecolumn ofpnpm update --interactiveis more informative in two cases. A dependency outdated at the same version in several workspace projects is offered as one choice, since selecting it updates every project — that choice now names all of them instead of only the first. And a workspace project without anameis now labelled with its path rather than left blank, so several unnamed projects can be told apart.An auto-installed optional peer is no longer hoisted at a version the workspace root's own dependency on that package excludes.
resolvePeersFromWorkspaceRootalready made the workspace root's specifier decide which version a missing required peer is installed at; the optional-peer picker ignored it and always took the highest version present anywhere in the graph. In a workspace whose root pinspostcss: 8.5.10, an importer that depends onwebpackand declares nopostcssof its own gotpostcss@8.5.22hoisted forterser-webpack-plugin's optionalpostcsspeer, leaving twopostcss@8.5.xinstances in the graph #13320.overridesnow also govern peers that pnpm auto-installs. Previously an override only rewrote dependencies declared in a manifest, so a peer nobody declares — installed becauseautoInstallPeersis on — resolved against its declared peer range and could bring in a second copy of the very package the override pinned. For example, withoverrides: { react: npm:react@19.2.0 }and a lonelucide-reactdependency, pnpm installedreact@18.3.1; it now installs the pinnedreact@19.2.0#13320.Under
resolvePeersFromWorkspaceRoot, a workspace root dependency declared withlink:orfile:(or the path form ofworkspace:, such asworkspace:../pkg) now satisfies another project's missing peer dependency at the linked package's own version, instead of being hoisted as a path. Those specifiers are relative to the project that declares them, so the same specifier reached a different directory — or none — from the project the peer was hoisted into, leaving a broken link. The root now has the same authority over the peer as it has when it declares the package with a version range #13373.Installs through a pnpr server now apply the project's whole verification policy.
minimumReleaseAgeExclude,minimumReleaseAgeIgnoreMissingTime,trustPolicy,trustPolicyExclude,trustPolicyIgnoreAfter, andtrustLockfilewere ignored, so excluded packages were still held back and a lockfile containing them could be rejected.trustPolicy: no-downgradeno longer fails withTRUST_POLICY_INCOMPATIBLE_WITH_PNPRwhen a pnpr server is configured.--frozen-lockfileand--no-prefer-frozen-lockfileare now honored on the pnpr path, instead of resolving and rewriting the lockfile anyway. SincefrozenLockfiledefaults totrueon CI, a CI install through a pnpr server now fails on an out-of-date lockfile rather than updating it.Workspace installs through a pnpr server no longer crash with
Cannot read properties of undefined (reading 'filter')after linking, whenminimumReleaseAgeis active #13275.Fixed
pnpm dedupeupdating valid catalog resolutions when another matching version exists in the lockfile.pnpm -r run "/pattern/" --no-bailno longer exits zero when one of a project's matched scripts fails and a later one passes. The run summary carries a single status per project, and the passing script overwrote the recorded failure.Restored the store block a first install prints, naming how packages were materialized and where the stores live #13315:
The root project's
pnpm:devPreinstallscript now runs before resolution and linking, as it does in pnpm 11. It is skipped under--ignore-scripts,--lockfile-onlyand--dry-run, bypnpm fetchandpnpm rebuild, and by a repeat install that is already up to date. Workspaces that use the hook to prepare state the install depends on — such as next.js, which generates a placeholdernextbin with it — were left with dependents linked against files that were never created #13313.Prevented
pnpm dedupe --checkfrom removing an incompatiblenode_modulesdirectory.pnpm update --workspaceno longer links dependencies the user never named:updateConfig.ignoreDependenciesconfigured no longer fails withERR_PNPM_WORKSPACE_PACKAGE_NOT_FOUNDfor a dependency that is only published to the registry. Such dependencies keep their specifiers, as they already did when no dependencies were ignored.Platinum Sponsors
Gold Sponsors
vitejs/vite (vite)
v8.2.0Compare Source
Features
inputtoserver.fs.allow(#23035) (95a3cda)Bug Fixes
Object.prototypeis frozen (#23073) (599c5b0)Documentation
Tests
vuejs/vitepress (vitepress)
v2.0.0-alpha.19Compare Source
Bug Fixes
preConfighook when extending configs (c39a85a), closes #5205cjkFriendlyoption (27762ea)lazyLoadingtolazyLoad(078786a)disableDetailedViewlocal search option (cec4998)lastUpdatedTextoption (18d1b47)outlineTitleoption (95c0420)Features
tabindexattribute (bffe1e1)attrs: falsefor disabling attrs plugin (e235dbe)note,important,cautionmarkdown containers (#5161) (3b560a0), closes #4427 #3928Performance Improvements
Reverts
BREAKING CHANGES
markdown.anchoroptions are now typed by@mdit/plugin-anchor. Common options (level,slugify,permalink,getTokensText,tabIndex, etc.) are unchanged, but the deprecated markdown-it-anchor permalink options (permalinkSymbol,renderPermalink, ...) are no longer accepted. Permalink builders likeheaderLinkare named exports of@mdit/plugin-anchorinstead of properties of the plugin.markdown.attrsoptions are now typed by@mdit/plugin-attrs:leftDelimiter,rightDelimiter, andallowedAttributesare renamed toleft,right, andallowed. Aruleoption is available for toggling individual attribute rules (VitePress disablesfenceby default).markdown.codeCopyButtonTitleis nowmarkdown.codeCopyButton.tooltipText, and its default changed from "Copy Code" to "Copy code". The--vp-code-copy-copied-text-contentCSS variable and its built-in per-language:lang()defaults are removed - setcodeCopyButton.copiedText(per locale) instead.useData().hashhas been removed. Read the hash fromuseRoute()instead.callers of vitepress' build() will now notice the version banner gets printed. To disable that, pass a noop function:
custom
themeConfig.i18nRoutingfunctions now receive the currentRouteas their second argument instead of the hashnormalize-level defaults differ from the old reset - native select and number-input chrome is restored, headings inherit font size and weight, the hidden attribute is enforced with !important, and every element starts with zero margin/padding and border-style: solid. Sites layering custom CSS on the default theme may notice.
relative urls in included markdown files resolve against the included file rather than the including page. Partials written for one specific location may need their links updated, or markdown.include.rebaseRelativeUrls set to false to keep resolving them from the including page. Absolute and external urls are unaffected. Note that the marker comments shift the line numbers reported for dead links following an include, which already pointed into the include-expanded source rather than the original file.
init: scaffold() now returns a
Promise<string>and must be awaited.The
defsproperty ofmarkdown.emojihas been renamed todefinitions.The
markdown.attrs.disableoption has been removed. Setmarkdown.attrstofalseinstead.The
markdown.image.lazyLoadingoption has been renamed tomarkdown.image.lazyLoad.The deprecated
disableDetailedViewoption of local search has been removed. UsedetailedView: falseinstead.The deprecated
markdown.cjkFriendlyoption has been removed. Usemarkdown.cjkFriendlyEmphasisinstead.The deprecated
themeConfig.lastUpdatedTextoption has been removed. UsethemeConfig.lastUpdated.textinstead.The deprecated
themeConfig.outlineTitleoption has been removed. UsethemeConfig.outline.labelinstead.The Inter4CJK font family has been renamed to 'Inter Core'. Custom --vp-font-family-base overrides referencing Inter4CJK must be updated.
yuyinws/vitepress-plugin-group-icons (vitepress-plugin-group-icons)
v1.7.6Compare Source
🚀 Features
🐞 Bug Fixes
View changes on GitHub
zizmorcore/zizmor-action (zizmorcore/zizmor-action)
v0.6.2Compare Source
zizmor 1.29.0 is now the default version.
Configuration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, 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.