Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Apr 1, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@eslint/js (source) ^9.21.0 -> ^9.23.0 age adoption passing confidence
@microsoft/api-extractor (source) ^7.51.0 -> ^7.52.2 age adoption passing confidence
@rslib/core (source) 0.5.2 -> 0.6.1 age adoption passing confidence
@types/node (source) 22.13.7 -> 22.13.14 age adoption passing confidence
eslint (source) ^9.21.0 -> ^9.23.0 age adoption passing confidence
eslint-plugin-svelte (source) ^3.0.2 -> ^3.4.1 age adoption passing confidence
eslint-plugin-vue (source) ^9.32.0 -> ^9.33.0 age adoption passing confidence
pnpm (source) 10.5.2 -> 10.7.0 age adoption passing confidence
prettier (source) ^3.5.2 -> ^3.5.3 age adoption passing confidence
simple-git-hooks ^2.11.1 -> ^2.12.1 age adoption passing confidence
typescript-eslint (source) ^8.25.0 -> ^8.29.0 age adoption passing confidence

Release Notes

eslint/eslint (@​eslint/js)

v9.23.0

Compare Source

v9.22.0

Compare Source

microsoft/rushstack (@​microsoft/api-extractor)

v7.52.2

Compare Source

Tue, 25 Mar 2025 15:11:15 GMT

Version update only

v7.52.1

Compare Source

Tue, 11 Mar 2025 02:12:34 GMT

Version update only

v7.52.0

Compare Source

Tue, 11 Mar 2025 00:11:25 GMT

Minor changes
  • Upgrade the bundled compiler engine to TypeScript 5.8.2

v7.51.1

Compare Source

Sat, 01 Mar 2025 05:00:09 GMT

Patches
  • Include triple-slash references marked with preserve="true" from files that only contain re-exports. There was a behavior change in TypeScript 5.5, where only triple-slash references that are explicitly marked with preserve="true" are emitted into declaration files. This change adds support for placing these references in files that only contain re-exports, like the API entrypoint file.
web-infra-dev/rslib (@​rslib/core)

v0.6.1

Compare Source

What's Changed

New Features 🎉
Other Changes

Full Changelog: web-infra-dev/rslib@v0.6.0...v0.6.1

v0.6.0

Compare Source

Highlights ✨

This release brings exciting new features and improvements to Rslib:

  • New default library type for CJS: Rslib changes the default value of output.library.type for CJS from commonjs to commonjs-static. Now, individual exports will be set as properties on module.exports and the output can be statically analyzable, thus named exports are importable into ESM via Node.js. This is useful when source code is written in ESM and the output should be compatible with both CJS and ESM. (#​819)

    Named exports are importable into ESM via Node.js

    • Input:
    export function doSomething() {}
    • Output:
    function doSomething() {}
    // …
    exports.doSomething = __webpack_exports__.doSomething;
    • Consumption (CJS):
    const { doSomething } = require('./output.cjs'); // doSomething => [Function: doSomething]
    • Consumption (ESM):
    import { doSomething } from './output.cjs'; // doSomething => [Function: doSomething]
  • Show code frame for type errors: Rslib now shows full context and code frame of tsc diagnostics in the terminal when generating declaration files. This makes it easier to understand and fix issues in the source code. (#​847)

    image

What's Changed

New Features 🎉
Bug Fixes 🐞
Document 📖
Other Changes

New Contributors

Full Changelog: web-infra-dev/rslib@v0.5.5...v0.6.0

v0.5.5

Compare Source

What's Changed

Bug Fixes 🐞
Document 📖
Other Changes

New Contributors

Full Changelog: web-infra-dev/rslib@v0.5.4...v0.5.5

v0.5.4

Compare Source

What's Changed

Bug Fixes 🐞
Other Changes

Full Changelog: web-infra-dev/rslib@v0.5.3...v0.5.4

v0.5.3

Compare Source

What's Changed

Bug Fixes 🐞
Document 📖
Other Changes

Full Changelog: web-infra-dev/rslib@v0.5.2...v0.5.3

eslint/eslint (eslint)

v9.23.0

Compare Source

v9.22.0

Compare Source

sveltejs/eslint-plugin-svelte (eslint-plugin-svelte)

v3.4.1

Compare Source

Patch Changes

v3.4.0

Compare Source

Minor Changes
  • #​1165 2b7e164 Thanks @​43081j! - Adds a suggestion to the require-store-callbacks-use-set-param rule to automatically rename or add function parameters.

  • #​1163 d9b8604 Thanks @​43081j! - Adds a suggestion to the derived-has-same-inputs-outputs rule which renames the outputs.

  • #​1164 29b1315 Thanks @​43081j! - Added a suggestion for no-at-debug-tags rule which removes the tags

Patch Changes

v3.3.3

Compare Source

Patch Changes

v3.3.2

Compare Source

Patch Changes

v3.3.1

Compare Source

Patch Changes

v3.3.0

Compare Source

Minor Changes
  • #​1132 30c1e5f Thanks @​baseballyama! - feat: add ignorePropertyPatterns property and rename ignorePatterns to ignoreTypePatterns in no-unused-props rule. The ignorePatterns option existed only for a few hours and is removed by this PR. Technically, this is a breaking change, but we’ll handle it as a minor release since very few users are likely affected.

v3.2.2

Compare Source

Patch Changes

v3.2.1

Compare Source

Patch Changes

v3.2.0

Compare Source

Minor Changes

v3.1.0

Compare Source

Minor Changes
Patch Changes

v3.0.3

Compare Source

Patch Changes
vuejs/eslint-plugin-vue (eslint-plugin-vue)

v9.33.0

Compare Source

✨ Enhancements

🐛 Bug Fixes

Full Changelog: vuejs/eslint-plugin-vue@v9.32.0...v9.33.0

pnpm/pnpm (pnpm)

v10.7.0

Compare Source

Minor Changes
  • pnpm config get and list also show settings set in pnpm-workspace.yaml files #​9316.

  • It should be possible to use env variables in pnpm-workspace.yaml setting names and value.

  • Add an ability to patch dependencies by version ranges. Exact versions override version ranges, which in turn override name-only patches. Version range * is the same as name-only, except that patch application failure will not be ignored.

    For example:

    patchedDependencies:
      foo: patches/foo-1.patch
      foo@^2.0.0: patches/foo-2.patch
      foo@2.1.0: patches/foo-3.patch

    The above configuration would apply patches/foo-3.patch to foo@2.1.0, patches/foo-2.patch to all foo versions which satisfy ^2.0.0 except 2.1.0, and patches/foo-1.patch to the remaining foo versions.

    [!WARNING]
    The version ranges should not overlap. If you want to specialize a sub range, make sure to exclude it from the other keys. For example:

    # pnpm-workspace.yaml
    patchedDependencies:
      # the specialized sub range
      'foo@2.2.0-2.8.0': patches/foo.2.2.0-2.8.0.patch
      # the more general patch, excluding the sub range above
      'foo@>=2.0.0 <2.2.0 || >2.8.0': 'patches/foo.gte2.patch

    In most cases, however, it's sufficient to just define an exact version to override the range.

  • pnpm config set --location=project saves the setting to a pnpm-workspace.yaml file if no .npmrc file is present in the directory #​9316.

  • Rename pnpm.allowNonAppliedPatches to pnpm.allowUnusedPatches. The old name is still supported but it would print a deprecation warning message.

  • Add pnpm.ignorePatchFailures to manage whether pnpm would ignore patch application failures.

    If ignorePatchFailures is not set, pnpm would throw an error when patches with exact versions or version ranges fail to apply, and it would ignore failures from name-only patches.

    If ignorePatchFailures is explicitly set to false, pnpm would throw an error when any type of patch fails to apply.

    If ignorePatchFailures is explicitly set to true, pnpm would print a warning when any type of patch fails to apply.

Patch Changes
  • Remove dependency paths from audit output to prevent out-of-memory errors #​9280.

v10.6.5

Compare Source

v10.6.4: pnpm 10.6.4

Compare Source

Patch Changes

  • Fix pnpm dlx with --allow-build flag #​9263.
  • Invalid Node.js version in use-node-version should not cause pnpm itself to break #​9276.
  • The max amount of workers running for linking packages from the store has been reduced to 4 to achieve optimal results #​9286. The workers are performing many file system operations, so increasing the number of CPUs doesn't help performance after some point.

Platinum Sponsors

Bit Bit Syntax

Gold Sponsors

Discord u|screen
JetBrains Nx
CodeRabbit Route4Me
Workleap Stackblitz

v10.6.3

Compare Source

Patch Changes
  • pnpm install --prod=false should not crash, when executed in a project with a pnpm-workspace.yaml file #​9233. This fixes regression introduced via #​9211.

  • Add the missing node-options config to recursive run #​9180.

  • Removed a branching code path that only executed when dedupe-peer-dependents=false. We believe this internal refactor will not result in behavior changes, but we expect it to make future pnpm versions behave more consistently for projects that override dedupe-peer-dependents to false. There should be less unique bugs from turning off dedupe-peer-dependents.

    See details in #​9259.

v10.6.2

Compare Source

Patch Changes
  • pnpm self-update should always update the version in the packageManager field of package.json.
  • Fix running pnpm CLI from pnpm CLI on Windows when the CLI is bundled to an executable #​8971.
  • pnpm patch-commit will now use the same filesystem as the store directory to compare and create patch files.
  • Don't show info output when --loglevel=error is used.
  • peerDependencyRules should be set in pnpm-workspace.yaml to take effect.

v10.6.1

Compare Source

Patch Changes
  • The pnpm CLI process should not stay hanging, when --silent reporting is used.
  • When --loglevel is set to error, don't show installation summary, execution time, and big tarball download progress.
  • Don't ignore pnpm.patchedDependencies from package.json #​9226.
  • When executing the approve-builds command, if package.json contains onlyBuiltDependencies or ignoredBuiltDependencies, the selected dependency package will continue to be written into package.json.
  • When a package version cannot be found in the package metadata, print the registry from which the package was fetched.

v10.6.0

Compare Source

Minor Changes
  • pnpm-workspace.yaml can now hold all the settings that .npmrc accepts. The settings should use camelCase #​9211.

    pnpm-workspace.yaml example:

    verifyDepsBeforeRun: install
    optimisticRepeatInstall: true
    publicHoistPattern:
      - "*types*"
      - "!@&#8203;types/react"
  • Projects using a file: dependency on a local tarball file (i.e. .tgz, .tar.gz, .tar) will see a performance improvement during installation. Previously, using a file: dependency on a tarball caused the lockfile resolution step to always run. The lockfile will now be considered up-to-date if the tarball is unchanged.

Patch Changes
  • pnpm self-update should not leave a directory with a broken pnpm installation if the installation fails.
  • fast-glob replace with tinyglobby to reduce the size of the pnpm CLI dependencies #​9169.
  • pnpm deploy should not remove fields from the deployed package's package.json file #​9215.
  • pnpm self-update should not read the pnpm settings from the package.json file in the current working directory.
  • Fix pnpm deploy creating a package.json without the imports and license field #​9193.
  • pnpm update -i should list only packages that have newer versions #​9206.
  • Fix a bug causing entries in the catalogs section of the pnpm-lock.yaml file to be removed when dedupe-peer-dependents=false on a filtered install. #​9112
prettier/prettier (prettier)

v3.5.3

Compare Source

toplenboren/

Configuration

📅 Schedule: Branch creation - "* 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 ba6b801 into main Apr 1, 2025
4 checks passed
@chenjiahan chenjiahan deleted the renovate/all-minor-patch branch April 1, 2025 03:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants