Skip to content

Update all non-major dependencies #415

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update all non-major dependencies #415

wants to merge 1 commit into from
+460 −424

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Sep 8, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence Type Update
@vitejs/plugin-vue (source) 6.0.1 -> 6.0.2 age confidence devDependencies patch
@vue/language-server (source) 3.0.6 -> 3.1.5 age confidence devDependencies minor
JamesIves/github-pages-deploy-action v4.7.3 -> v4.7.4 age confidence action patch
nano-staged 0.8.0 -> 0.9.0 age confidence devDependencies minor
pnpm (source) 10.15.0 -> 10.23.0 age confidence packageManager minor
sass 1.90.0 -> 1.94.2 age confidence devDependencies minor
typescript (source) 5.9.2 -> 5.9.3 age confidence devDependencies patch
vite (source) 7.1.4 -> 7.2.7 age confidence devDependencies minor
vue (source) 3.6.0-alpha.2 -> 3.6.0-alpha.4 age confidence dependencies patch
vue-tsc (source) 3.0.6 -> 3.1.5 age confidence devDependencies minor

Release Notes

vitejs/vite-plugin-vue (@​vitejs/plugin-vue)

v6.0.2

Bug Fixes
Miscellaneous Chores
vuejs/language-tools (@​vue/language-server)

v3.1.5

Compare Source

Features
  • feat(language-service): support tsconfig path alias resolution for document links (#​5562) - Thanks to @​KazariEX!
  • feat(language-server): add serverInfo to initialized result (#​5767) - Thanks to @​kada49!
Bug Fixes
Performance

v3.1.4

Compare Source

Bug Fixes
  • fix(language-service): prevent auto-insertion of html snippets in template interpolation (#​5744) - Thanks to @​serkodev!
  • fix(language-service): strip interpolations from document passed to html service - Thanks to @​KazariEX!
  • fix(language-core): report unused @ts-expect-error directive on components with loose props checks (#​5750) - Thanks to @​serkodev and @​KazariEX!
  • fix(language-core): respect directive comments before v-else (#​5753) - Thanks to @​serkodev and @​KazariEX!
Other Changes
  • refactor(language-core): re-implement component references by codegen (#​5736) - Thanks to @​KazariEX!
  • refactor(language-core): simplify calculation of full interpolation content - Thanks to @​KazariEX!

v3.1.3

Compare Source

Features
  • feat(typescript-plugin): allow triggering file references on <template> (#​5734) - Thanks to @​KazariEX!
Bug Fixes
  • fix(vscode): correct syntax highlight in template with lang="html" (#​5728) - Thanks to @​serkodev!
Other Changes
  • refactor(language-core): generate intrinsic elements variable into global types (#​5730) - Thanks to @​KazariEX!
  • refactor(typescript-plugin): remove go to definition trick for auto imported components (#​5733) - Thanks to @​KazariEX!

v3.1.2

Compare Source

Bug Fixes
  • fix(component-meta): import type helpers by relative path
  • fix(language-core): fix syntax error when propTypes has no elements (#​5704) - Thanks to @​so1ve!
  • fix(language-core): omit defined emit props only (#​5705) - Thanks to @​so1ve!
Other Changes
  • docs: fix vue-tsc broken link to example boilerplate in README.md (#​5721) - Thanks to @​heyakyra!

v3.1.1

Compare Source

Features
  • feat(language-server): support --tsdk command line arg (#​5691)
Bug Fixes
  • fix(language-core): tolerate non-literal export default (#​5675) - Thanks to @​KazariEX!
  • fix(language-core): use component instance props as fallthrough attributes (#​5686) - Thanks to @​KazariEX!
  • fix(typescript-plugin): determine if variable is Ref by RefSymbol property (#​5687) - Thanks to @​KazariEX!
  • fix(language-core): exclude effect of comments on root node (#​5689) - Thanks to @​KazariEX!
  • fix(typescript-plugin): place __vue__ in project instead of program (#​5690)
  • fix(component-type-helpers): remove deprecated $scopedSlots support for Vue 2
  • fix(language-core): replace markdown links after sfc blocks processing (#​5695) - Thanks to @​KazariEX!
  • fix(language-core): do not report unused error on __VLS_export (#​5696) - Thanks to @​KazariEX!
Other Changes
  • refactor(language-core): reimplement writeGlobalTypes without side effects

v3.1.0

Compare Source

Performance
Other Changes

v3.0.10

Compare Source

Bug Fixes
  • fix(typescript-plugin): place __vue__ in project instead of program (#​5690)

v3.0.9

Compare Source

Features
  • feat(language-server): support --tsdk command line arg (#​5691)

v3.0.8

Compare Source

Features
  • feat(vscode): introduce vue.server.path setting (#​5647)
Bug Fixes
  • fix(language-core): initialize properties of VueVirtualCode in constructor (#​5635) - Thanks to @​KazariEX!
  • fix(vscode): flatten reactivity visualization decorators (#​5642) - Thanks to @​KazariEX!
  • fix(vscode): normalize reactivity visualization ranges
  • fix(vscode): patch typescriptServerPlugin languages without FS hack
  • fix(language-service): do not provide semantic tokens and document highlights for non-file scheme files (#​5653) - Thanks to @​KazariEX!
Performance
  • perf(typescript-plugin): redo single-file language service for reactivity visualization (#​5652)
Other Changes
  • refactor(typescript-plugin): externalize reactivity analysis logic (#​5645) - Thanks to @​KazariEX!

v3.0.7

Compare Source

Bug Fixes
  • fix(vscode): show welcome page only when opening a Vue file
  • fix(language-core): generate slot parameters in the same way as interpolation (#​5618) - Thanks to @​KazariEX!
  • fix(language-core): do not generate variables for builtin directives - Thanks to @​KazariEX!
Other Changes
  • docs(vscode): add descriptions for premium feature configurations (#​5612) - Thanks to @​KazariEX!
  • refactor(typescript-plugin): explicitly request parameters (#​5623)
  • chore(lint): enable @typescript-eslint/no-unnecessary-condition (#​5630)
  • refactor(language-server): reimplement Reactivity Visualization in typescript plugin (#​5632)
  • refactor(language-server): parsing interpolations in extension client (#​5633)
  • refactor(vscode): reimplement Focus Mode base on folding ranges (#​5634)
  • chore(vscode): disable Focus Mode by default (#​5578)
  • refactor(vscode): set delay of reactivity visualization updates to 250ms - Thanks to @​KazariEX!
JamesIves/github-pages-deploy-action (JamesIves/github-pages-deploy-action)

v4.7.4

Compare Source

What's Changed

Bug Fixes 🐛
Build 🔧
Other Changes
  • Add comprehensive GitHub Copilot instructions for development workflow by @​Copilot in #​1894

Full Changelog: JamesIves/github-pages-deploy-action@v4...v4.7.4

pnpm/pnpm (pnpm)

v10.23.0: pnpm 10.23

Compare Source

Minor Changes

  • Added --lockfile-only option to pnpm list #​10020.

Patch Changes

  • pnpm self-update should download pnpm from the configured npm registry #​10205.
  • pnpm self-update should always install the non-executable pnpm package (pnpm in the registry) and never the @pnpm/exe package, when installing v11 or newer. We currently cannot ship @pnpm/exe as pkg doesn't work with ESM #​10190.
  • Node.js runtime is not added to "dependencies" on pnpm add, if there's a engines.runtime setting declared in package.json #​10209.
  • The installation should fail if an optional dependency cannot be installed due to a trust policy check failure #​10208.
  • pnpm list and pnpm why now display npm: protocol for aliased packages (e.g., foo npm:[email protected]) #​8660.
  • Don't add an extra slash to the Node.js mirror URL #​10204.
  • pnpm store prune should not fail if the store contains Node.js packages #​10131.

Platinum Sponsors

Bit

Gold Sponsors

Discord CodeRabbit Workleap
Stackblitz Vite

v10.22.0: pnpm 10.22

Compare Source

Minor Changes

  • Added support for trustPolicyExclude #​10164.

    You can now list one or more specific packages or versions that pnpm should allow to install, even if those packages don't satisfy the trust policy requirement. For example:

    trustPolicy: no-downgrade
trustPolicyExclude:
  - [email protected]
  - [email protected] || 5.102.1

  • Allow to override the engines field on publish by the publishConfig.engines field.

Patch Changes

  • Don't crash when two processes of pnpm are hardlinking the contents of a directory to the same destination simultaneously #​10179.

Platinum Sponsors

Bit

Gold Sponsors

Discord CodeRabbit Workleap
Stackblitz Vite

v10.21.0

Compare Source

v10.20.0

Compare Source

Minor Changes
  • Support --all option in pnpm --help to list all commands #​8628.
Patch Changes
  • When the latest version doesn't satisfy the maturity requirement configured by minimumReleaseAge, pick the highest version that is mature enough, even if it has a different major version #​10100.
  • create command should not verify patch info.
  • Set managePackageManagerVersions to false, when switching to a different version of pnpm CLI, in order to avoid subsequent switches #​10063.

v10.19.0

Compare Source

Minor Changes

  • You can now allow specific versions of dependencies to run postinstall scripts. onlyBuiltDependencies now accepts package names with lists of trusted versions. For example:

    onlyBuiltDependencies:
  - [email protected] || 21.6.5
  - [email protected]

    Related PR: #​10104.

  • Added support for exact versions in minimumReleaseAgeExclude #​9985.

    You can now list one or more specific versions that pnpm should allow to install, even if those versions don’t satisfy the maturity requirement set by minimumReleaseAge. For example:

    minimumReleaseAge: 1440
minimumReleaseAgeExclude:
  - [email protected]
  - [email protected] || 5.102.1

v10.18.3

Compare Source

Patch Changes
  • Fix a bug where pnpm would infinitely recurse when using verifyDepsBeforeInstall: install and pre/post install scripts that called other pnpm scripts #​10060.
  • Fixed scoped registry keys (e.g., @scope:registry) being parsed as property paths in pnpm config get when --location=project is used #​9362.
  • Remove pnpm-specific CLI options before passing to npm publish to prevent "Unknown cli config" warnings #​9646.
  • Fixed EISDIR error when bin field points to a directory #​9441.
  • Preserve version and hasBin for variations packages #​10022.
  • Fixed pnpm config set --location=project incorrectly handling keys with slashes (auth tokens, registry settings) #​9884.
  • When both pnpm-workspace.yaml and .npmrc exist, pnpm config set --location=project now writes to pnpm-workspace.yaml (matching read priority) #​10072.
  • Prevent a table width error in pnpm outdated --long #​10040.
  • Sync bin links after injected dependencies are updated by build scripts. This ensures that binaries created during build processes are properly linked and accessible to consuming projects #​10057.

v10.18.2

Compare Source

Patch Changes
  • pnpm outdated --long should work #​10040.
  • Replace ndjson with split2. Reduce the bundle size of pnpm CLI #​10054.
  • pnpm dlx should request the full metadata of packages, when minimumReleaseAge is set #​9963.
  • pnpm version switching should work when the pnpm home directory is in a symlinked directory #​9715.
  • Fix EPIPE errors when piping output to other commands #​10027.

v10.18.1

Compare Source

Patch Changes
  • Don't print a warning, when --lockfile-only is used #​8320.
  • pnpm setup creates a command shim to the pnpm executable. This is needed to be able to run pnpm self-update on Windows #​5700.
  • When using pnpm catalogs and running a normal pnpm install, pnpm produced false positive warnings for "skip adding to the default catalog because it already exists". This warning now only prints when using pnpm add --save-catalog as originally intended.

v10.18.0

Compare Source

Minor Changes

  • Added network performance monitoring to pnpm by implementing warnings for slow network requests, including both metadata fetches and tarball downloads.

    Added configuration options for warning thresholds: fetchWarnTimeoutMs and fetchMinSpeedKiBps.
    Warning messages are displayed when requests exceed time thresholds or fall below speed minimums

    Related PR: #​10025.

Patch Changes
  • Retry filesystem operations on EAGAIN errors #​9959.
  • Outdated command respects minimumReleaseAge configuration #​10030.
  • Correctly apply the cleanupUnusedCatalogs configuration when removing dependent packages.
  • Don't fail with a meaningless error when scriptShell is set to false #​8748.
  • pnpm dlx should not fail when minimumReleaseAge is set #​10037.

v10.17.1

Compare Source

Patch Changes
  • When a version specifier cannot be resolved because the versions don't satisfy the minimumReleaseAge setting, print this information out in the error message #​9974.
  • Fix state.json creation path when executing pnpm patch in a workspace project #​9733.
  • When minimumReleaseAge is set and the latest tag is not mature enough, prefer a non-deprecated version as the new latest #​9987.

v10.17.0

Compare Source

Minor Changes

  • The minimumReleaseAgeExclude setting now supports patterns. For instance:

    minimumReleaseAge: 1440
minimumReleaseAgeExclude:
  - "@&#8203;eslint/*"

    Related PR: #​9984.

Patch Changes
  • Don't ignore the minimumReleaseAge check, when the package is requested by exact version and the packument is loaded from cache #​9978.
  • When minimumReleaseAge is set and the active version under a dist-tag is not mature enough, do not downgrade to a prerelease version in case the original version wasn't a prerelease one #​9979.

v10.16.1

Compare Source

Patch Changes
  • The full metadata cache should be stored not at the same location as the abbreviated metadata. This fixes a bug where pnpm was loading the abbreviated metadata from cache and couldn't find the "time" field as a result #​9963.
  • Forcibly disable ANSI color codes when generating patch diff #​9914.

v10.16.0

Compare Source

Minor Changes

  • There have been several incidents recently where popular packages were successfully attacked. To reduce the risk of installing a compromised version, we are introducing a new setting that delays the installation of newly released dependencies. In most cases, such attacks are discovered quickly and the malicious versions are removed from the registry within an hour.

    The new setting is called minimumReleaseAge. It specifies the number of minutes that must pass after a version is published before pnpm will install it. For example, setting minimumReleaseAge: 1440 ensures that only packages released at least one day ago can be installed.

    If you set minimumReleaseAge but need to disable this restriction for certain dependencies, you can list them under the minimumReleaseAgeExclude setting. For instance, with the following configuration pnpm will always install the latest version of webpack, regardless of its release time:

    minimumReleaseAgeExclude:
  - webpack

    Related issue: #​9921.

  • Added support for finders #​9946.

    In the past, pnpm list and pnpm why could only search for dependencies by name (and optionally version). For example:

    pnpm why minimist

    prints the chain of dependencies to any installed instance of minimist:

    verdaccio 5.20.1
├─┬ handlebars 4.7.7
│ └── minimist 1.2.8
└─┬ mv 2.1.1
  └─┬ mkdirp 0.5.6
    └── minimist 1.2.8

    What if we want to search by other properties of a dependency, not just its name? For instance, find all packages that have react@17 in their peer dependencies?

    This is now possible with "finder functions". Finder functions can be declared in .pnpmfile.cjs and invoked with the --find-by=<function name> flag when running pnpm list or pnpm why.

    Let's say we want to find any dependencies that have React 17 in peer dependencies. We can add this finder to our .pnpmfile.cjs:

    module.exports = {
  finders: {
    react17: (ctx) => {
      return ctx.readManifest().peerDependencies?.react === "^17.0.0";
    },
  },
};

    Now we can use this finder function by running:

    pnpm why --find-by=react17

    pnpm will find all dependencies that have this React in peer dependencies and print their exact locations in the dependency graph.

    @&#8203;apollo/client 4.0.4
├── @&#8203;graphql-typed-document-node/core 3.2.0
└── graphql-tag 2.12.6

    It is also possible to print out some additional information in the output by returning a string from the finder. For example, with the following finder:

    module.exports = {
  finders: {
    react17: (ctx) => {
      const manifest = ctx.readManifest();
      if (manifest.peerDependencies?.react === "^17.0.0") {
        return `license: ${manifest.license}`;
      }
      return false;
    },
  },
};

    Every matched package will also print out the license from its package.json:

    @&#8203;apollo/client 4.0.4
├── @&#8203;graphql-typed-document-node/core 3.2.0
│   license: MIT
└── graphql-tag 2.12.6
    license: MIT
Patch Changes
  • Fix deprecation warning printed when executing pnpm with Node.js 24 #​9529.
  • Throw an error if nodeVersion is not set to an exact semver version #​9934.
  • pnpm publish should be able to publish a .tar.gz file #​9927.
  • Canceling a running process with Ctrl-C should make pnpm run return a non-zero exit code #​9626.

v10.15.1

Compare Source

Patch Changes
  • Fix .pnp.cjs crash when importing subpath #​9904.
  • When resolving peer dependencies, pnpm looks whether the peer depend

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).

🚦 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.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Sep 8, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 009ce6c to d4dad7a Compare September 14, 2025 00:04
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from abeaafc to b92c915 Compare September 22, 2025 04:51
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from 036d5b1 to 6abc3c9 Compare September 28, 2025 18:03
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from 5d3ec25 to 4aef535 Compare October 7, 2025 04:57
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 8154018 to 9ed8586 Compare October 14, 2025 18:00
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from ee7a820 to eb844a9 Compare October 25, 2025 05:52
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 5a30d8f to c5b1566 Compare November 3, 2025 03:04
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 8 times, most recently from 73db572 to 08a2dc4 Compare November 11, 2025 12:13
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from d65633b to 54a0194 Compare November 19, 2025 08:28
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from d067ad5 to 7d90a6c Compare November 20, 2025 17:51
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 7d90a6c to eccd239 Compare November 22, 2025 21:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant