Skip to content

fix(deps): update all non-major dependencies #39

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
Merged
chenjiahan merged 1 commit into from
Oct 1, 2025
Merged

fix(deps): update all non-major dependencies #39

chenjiahan merged 1 commit into from
Oct 1, 2025

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 1, 2025

Note

Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to mend[bot].

This notice will be removed on 2025-10-07.

This PR contains the following updates:

Package Change Age Confidence Type Update
@rslib/core (source) 0.11.0 -> 0.15.0 age confidence devDependencies minor
@types/node (source) 22.17.0 -> 22.18.8 age confidence devDependencies minor
@vercel/ncc 0.38.3 -> 0.38.4 age confidence dependencies patch
fs-extra ^11.3.0 -> ^11.3.2 age confidence devDependencies patch
node 22 -> 22.20.0 age confidence uses-with minor
pnpm (source) 10.14.0 -> 10.17.1 age confidence packageManager minor
rollup (source) ^4.46.2 -> ^4.52.3 age confidence dependencies minor
rollup-plugin-dts ^6.2.1 -> ^6.2.3 age confidence dependencies patch
rslog ^1.2.9 -> ^1.2.11 age confidence devDependencies patch
terser (source) ^5.43.1 -> ^5.44.0 age confidence dependencies minor
typescript (source) ^5.9.2 -> ^5.9.3 age confidence devDependencies patch

Release Notes

web-infra-dev/rslib (@​rslib/core)

v0.15.0

Compare Source

Highlights 💡

Preserve JSX

Rslib supports setting the JSX runtime to 'preserve' to leave JSX syntax unchanged without transforming it, which is useful when you expect JSX to be left as is in library development.

Preserve JSX

See JSX transform - React for more details.

What's Changed

New Features 🎉
Bug Fixes 🐞
Document 📖
Other Changes

Full Changelog: web-infra-dev/rslib@v0.14.0...v0.15.0

v0.14.0

Compare Source

Breaking changes 🚨
Config loading

Currently, configuration files are loaded with jiti, which relies on Babel. This approach is relatively slow (at least ~70ms slower compared to native).

In Rslib v0.13.3, we introduced a new CLI option --config-loader native, which uses Node.js's native loader. This approach offers better performance and stricter behavior, but comes with certain requirements:

  • Requires Node v22.18+ with built-in TypeScript support
  • Import specifiers must include file extensions
  • When using TypeScript, package.json must set "type": "module"
  • Importing JSON requires with { type: "json" }

In Rslib v0.14.0, we adjust the default configuration loading behavior. The new default is now --config-loader auto, which:

  • First attempts to use the faster native loader
  • If that fails, it gracefully falls back to jiti for broader compatibility

This change to 'auto' as the default is part of our long-term plan to transition config loading from jiti to Node.js native.

What's Changed
New Features 🎉
Bug Fixes 🐞
Other Changes

Full Changelog: web-infra-dev/rslib@v0.13.3...v0.14.0

v0.13.3

Compare Source

What's Changed

New Features 🎉
Performance 🚀
Bug Fixes 🐞
Other Changes

Full Changelog: web-infra-dev/rslib@v0.13.2...v0.13.3

v0.13.2

Compare Source

What's Changed

Bug Fixes 🐞
Other Changes

Full Changelog: web-infra-dev/rslib@v0.13.1...v0.13.2

v0.13.1

Compare Source

What's Changed

Bug Fixes 🐞
Document 📖
Other Changes

Full Changelog: web-infra-dev/rslib@v0.13.0...v0.13.1

v0.13.0

Compare Source

Highlights 💡

Faster declaration generation with tsgo

Rslib now can generate declaration files with tsgo, which can provide faster generation of declaration files, especially for large projects.

[!TIP]
This feature is currently an experimental feature. Since tsgo is still in the experimental stage, there may be some bugs and unresolved issues or limitations. So, make sure to fully test it in your project before enabling this option.

export default {
  lib: [
    {
      dts: {
        tsgo: true,
      },
    },
  ],
};

What's Changed

New Features 🎉
Document 📖
Other Changes

Full Changelog: web-infra-dev/rslib@v0.12.4...v0.13.0

v0.12.4

Compare Source

What's Changed

New Features 🎉
Bug Fixes 🐞
Other Changes

New Contributors

Full Changelog: web-infra-dev/rslib@v0.12.3...v0.12.4

v0.12.3

Compare Source

What's Changed

New Features 🎉
Bug Fixes 🐞
Other Changes

Full Changelog: web-infra-dev/rslib@v0.12.2...v0.12.3

v0.12.2

Compare Source

What's Changed

New Features 🎉
Document 📖
Other Changes

New Contributors

Full Changelog: web-infra-dev/rslib@v0.12.1...v0.12.2

v0.12.1

Compare Source

What's Changed

New Features 🎉
Other Changes

Full Changelog: web-infra-dev/rslib@v0.12.0...v0.12.1

v0.12.0

Compare Source

Highlights 💡

Drop support for Node 16

Node.js 16 reached its end-of-life on September 11, 2023. Many other npm packages in the ecosystem have also dropped support for Node 16, including webpack-dev-server, css-loader, sass-loader, and so on, which makes maintaining compatibility increasingly challenging. Therefore, we have decided to drop Node 16 support starting from Rslib v0.12 to ensure better compatibility with the modern ecosystem.

Package v0.11 v0.12
@​rslib/core >=16.7.0 >=18.12.0

Rslib v0.11 based on Rsbuild/Rspack v1.4 and Rslib v0.12 based on Rsbuild/Rspack v1.5:

Package v1.4 v1.5
@​rspack/core >=16.0.0 >=18.12.0
@​rsbuild/core >=16.10.0 >=18.12.0

⚠️ This is a breaking change for users still running Node.js 16. Users will need to upgrade to Node.js 18.12.0 or later to use Rslib v0.12.

For users currently using Node.js 16:

  1. Upgrade to Node.js 18.12.0 or later (Node.js 22 LTS is recommended)
  2. Update your CI/CD pipelines to use the new Node.js version

What's Changed

New Features 🎉
Bug Fixes 🐞
Document 📖
Other Changes

Full Changelog: web-infra-dev/rslib@v0.11.2...v0.12.0

v0.11.2

Compare Source

What's Changed

Trusted Publishing

All Rslib npm packages are now published based on npm's trusted publishing, making Rslib's npm packages more secure and transparent.

See:

Document 📖
Other Changes

Full Changelog: web-infra-dev/rslib@v0.11.1...v0.11.2

v0.11.1

Compare Source

What's Changed

New Features 🎉
Bug Fixes 🐞
Other Changes

Full Changelog: web-infra-dev/rslib@v0.11.0...v0.11.1

vercel/ncc (@​vercel/ncc)

v0.38.4

Compare Source

Bug Fixes
jprichardson/node-fs-extra (fs-extra)

v11.3.2

Compare Source

  • Fix spurrious UnhandledPromiseRejectionWarning that could occur when calling .copy() in some cases (#​1056, #​1058)

v11.3.1

Compare Source

  • Fix case where move/moveSync could incorrectly think files are identical on Windows (#​1050)
actions/node-versions (node)

v22.20.0: 22.20.0

Compare Source

Node.js 22.20.0

v22.19.0: 22.19.0

Compare Source

Node.js 22.19.0

v22.18.0: 22.18.0

Compare Source

Node.js 22.18.0

v22.17.1: 22.17.1

Compare Source

Node.js 22.17.1

v22.17.0: 22.17.0

Compare Source

Node.js 22.17.0

v22.16.0: 22.16.0

Compare Source

Node.js 22.16.0

v22.15.1: 22.15.1

Compare Source

Node.js 22.15.1

v22.15.0: 22.15.0

Compare Source

Node.js 22.15.0

v22.14.0: 22.14.0

Compare Source

Node.js 22.14.0

v22.13.1: 22.13.1

Compare Source

Node.js 22.13.1

v22.13.0: 22.13.0

Compare Source

Node.js 22.13.0

v22.12.0: 22.12.0

Compare Source

Node.js 22.12.0

v22.11.0: 22.11.0

Compare Source

Node.js 22.11.0

v22.10.0: 22.10.0

Compare Source

Node.js 22.10.0

v22.9.0: 22.9.0

Compare Source

Node.js 22.9.0

v22.8.0: 22.8.0

Compare Source

Node.js 22.8.0

v22.7.0: 22.7.0

Compare Source

Node.js 22.7.0

v22.6.0: 22.6.0

Compare Source

Node.js 22.6.0

v22.5.1: 22.5.1

Compare Source

Node.js 22.5.1

v22.5.0: 22.5.0

Compare Source

Node.js 22.5.0

v22.4.1: 22.4.1

Compare Source

Node.js 22.4.1

v22.4.0: 22.4.0

Compare Source

Node.js 22.4.0

v22.3.0: 22.3.0

Compare Source

Node.js 22.3.0

v22.2.0: 22.2.0

Compare Source

Node.js 22.2.0

v22.1.0: 22.1.0

Compare Source

Node.js 22.1.0

pnpm/pnpm (pnpm)

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:
  - "@​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 dependency is present in the root workspace project's dependencies. This change makes it so that the peer dependency is correctly resolved even from aliased npm-hosted dependencies or other types of dependencies #​9913.

v10.15.0

Compare Source

Minor Changes
  • Added the cleanupUnusedCatalogs configuration. When set to true, pnpm will remove unused catalog entries during installation #​9793.
  • Automatically load pnpmfiles from config dependencies that are named @*/pnpm-plugin-* #​9780.
  • pnpm config get now prints an INI string for an object value #​9797.
  • pnpm config get now accepts property paths (e.g. pnpm config get catalog.react, pnpm config get .catalog.react, pnpm config get 'packageExtensions["@&#8203;babel/parser"].peerDependencies["@&#8203;babel/types"]'), and pnpm config set now accepts dot-leading or subscripted keys (e.g. pnpm config set .ignoreScripts true).
  • pnpm config get --json now prints a JSON serialization of config value, and pnpm config set --json now parses the input value as JSON.
Patch Changes
  • Semi-breaking. When automatically installing missing peer dependencies, prefer versions that are already present in the direct dependencies of the root workspace package #​9835.
  • When executing the pnpm create command, must verify whether the node version is supported even if a cache already exists #​9775.
  • When making requests for the non-abbreviated packument, add */* to the Accept header to avoid getting a 406 error on AWS CodeArtifact #​9862.
  • The standalone exe version of pnpm works with glibc 2.26 again #​9734.
  • Fix a regression in which pnpm dlx pkg --help doesn't pass --help to pkg #​9823.
rollup/rollup (rollup)

v4.52.3

Compare Source

2025-09-27

Bug Fixes
  • Fix check in native loader for environments that do not support reports (#​6123)
Pull Requests

v4.52.2

Compare Source

2025-09-23

Bug Fixes
  • Fix Android build crashing due to failed dlopen (#​6109)
Pull Requests

v4.52.1

Compare Source

2025-09-23

Bug Fixes
  • Opt-out of dynamic import optimization when using top-level await to effectively prevent deadlocks (#​6121)
Pull Requests

v4.52.0

Compare Source

2025-09-19

Features
  • Add option output.onlyExplicitManualChunks to turn off merging additional dependencies into manual chunks (#​6087)
  • Add support for x86_64-pc-windows-gnu platform (#​6110)
Pull Requests

v4.51.0

Compare Source

2025-09-19

Features
  • Support ROLLUP_FILE_URL_OBJ placeholder to inject file URLs into the generated code

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, on day 1 of the month ( * 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.

@chenjiahan chenjiahan merged commit 71c940e into main Oct 1, 2025
3 checks passed
@chenjiahan chenjiahan deleted the renovate/all-minor-patch branch October 1, 2025 03:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@chenjiahan chenjiahan chenjiahan approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@chenjiahan