fix(deps): update all non-major dependencies by renovate[bot] · Pull Request #138 · zotero-plugin-dev/zotero-plugin-scaffold

renovate · 2025-10-01T02:32:26Z

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	Type	Update
@antfu/eslint-config	`^5.2.1` -> `^5.4.1`	devDependencies	minor
@shikijs/vitepress-twoslash (source)	`^3.12.1` -> `^3.13.0`	devDependencies	minor
@types/node (source)	`^22.18.0` -> `^22.18.8`	devDependencies	patch
c12	`^3.2.0` -> `^3.3.0`	dependencies	minor
commander	`^14.0.0` -> `^14.0.1`	dependencies	patch
esbuild	`^0.25.9` -> `^0.25.10`	dependencies	patch
eslint (source)	`^9.34.0` -> `^9.36.0`	devDependencies	minor
eslint-plugin-format	`^1.0.1` -> `^1.0.2`	devDependencies	patch
fs-extra	`^11.3.1` -> `^11.3.2`	dependencies	patch
lint-staged	`^16.1.6` -> `^16.2.3`	devDependencies	minor
node	`22.19.0` -> `22.20.0`	uses-with	minor
pnpm (source)	`10.15.1` -> `10.17.1`	packageManager	minor
tinyglobby (source)	`^0.2.14` -> `^0.2.15`	dependencies	patch
tsx (source)	`^4.20.5` -> `^4.20.6`	devDependencies	patch
typescript (source)	`^5.9.2` -> `^5.9.3`	devDependencies	patch

Release Notes

antfu/eslint-config (@antfu/eslint-config)

`v5.4.1`

Compare Source

No significant changes

View changes on GitHub

`v5.4.0`

Compare Source

No significant changes

View changes on GitHub

`v5.3.0`

Compare Source

🐞 Bug Fixes

Use ecmaVersion 'latest' per eslint's docs recommendation. fixes support for import attributes - by @romansp in #756 (2031b)

View changes on GitHub

`v5.2.2`

Compare Source

🚀 Features

Add sort support of Bun catalogs - by @letstri in #754 (800d8)

View changes on GitHub

shikijs/shiki (@shikijs/vitepress-twoslash)

`v3.13.0`

Compare Source

🚀 Features

transformers: Render indent guides - by @KazariEX and @antfu in #1060 (aecd1)

View changes on GitHub

`v3.12.3`

Compare Source

🐞 Bug Fixes

@shikijs/twoslash version specifier - by @9romise in #1078 (a1cde)

View changes on GitHub

`v3.12.2`

Compare Source

🐞 Bug Fixes

twoslash: Fix onTwoslashError return value handling - by @Karibash in #1070 (e86b0)

View changes on GitHub

unjs/c12 (c12)

`v3.3.0`

Compare Source

compare changes

🚀 Enhancements

Support loading config with array exports (#272)
Allow extends without extension (#268)

🩹 Fixes

loadDotenv: cwd is optional (#273)

📖 Documentation

Improve dotenv section with multiple files example (#270)

🏡 Chore

Update readme (5f803d6)
Sort a-z (40207d2)
Update lockfile (2cc4f5e)
Update lockfile (38e04db)

✅ Tests

Add missing await (63e5b5e)
Update snapshot (bc671c4)

❤️ Contributors

Pooya Parsa (@pi0)
Devbro1 [email protected]
Carson (@carson2222)
Igal Klebanov [email protected]

tj/commander.js (commander)

`v14.0.1`

Compare Source

Fixed

broken markdown link in README ([#2369])

Changed

improve code readability by using optional chaining ([#2394])
use more idiomatic code with object spread instead of Object.assign() ([#2395])
improve code readability using string.endsWith() instead of string.slice() ([#2396])
refactor .parseOptions() to process args array in-place ([#2409])
change private variadic support routines from ._concatValue() to ._collectValue() (change code from array.concat() to array.push()) ([#2410])
update (dev) dependencies

evanw/esbuild (esbuild)

`v0.25.10`

Compare Source

Fix a panic in a minification edge case (#4287)

This release fixes a panic due to a null pointer that could happen when esbuild inlines a doubly-nested identity function and the final result is empty. It was fixed by emitting the value undefined in this case, which avoids the panic. This case must be rare since it hasn't come up until now. Here is an example of code that previously triggered the panic (which only happened when minifying):
```
function identity(x) { return x }
identity({ y: identity(123) })
```
Fix @supports nested inside pseudo-element (#4265)

When transforming nested CSS to non-nested CSS, esbuild is supposed to filter out pseudo-elements such as ::placeholder for correctness. The CSS nesting specification says the following:

The nesting selector cannot represent pseudo-elements (identical to the behavior of the ':is()' pseudo-class). We’d like to relax this restriction, but need to do so simultaneously for both ':is()' and '&', since they’re intentionally built on the same underlying mechanisms.

However, it seems like this behavior is different for nested at-rules such as @supports, which do work with pseudo-elements. So this release modifies esbuild's behavior to now take that into account:
```
/* Original code */
::placeholder {
  color: red;
  body & { color: green }
  @&#8203;supports (color: blue) { color: blue }
}

/* Old output (with --supported:nesting=false) */
::placeholder {
  color: red;
}
body :is() {
  color: green;
}
@&#8203;supports (color: blue) {
   {
    color: blue;
  }
}

/* New output (with --supported:nesting=false) */
::placeholder {
  color: red;
}
body :is() {
  color: green;
}
@&#8203;supports (color: blue) {
  ::placeholder {
    color: blue;
  }
}
```

eslint/eslint (eslint)

`v9.36.0`

Compare Source

`v9.35.0`

Compare Source

antfu/eslint-plugin-format (eslint-plugin-format)

`v1.0.2`

Compare Source

No significant changes

View changes on GitHub

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)

lint-staged/lint-staged (lint-staged)

`v16.2.3`

Compare Source

Patch Changes

#1669 27cd541 Thanks @iiroj! - When using --fail-on-changes, automatically hidden (partially) unstaged changes are no longer counted to make lint-staged fail.

`v16.2.2`

Compare Source

Patch Changes

#1667 699f95d Thanks @iiroj! - The backup stash will not be dropped when using --fail-on-changes and there are errors. When reverting to original state is disabled (via --no-revert or --fail-on-changes), hidden (partially) unstaged changes are still restored automatically so that it's easier to resolve the situation manually.

Additionally, the example for using the backup stash manually now uses the correct backup hash, if available:

% npx lint-staged --fail-on-changes
✔ Backed up original state in git stash (c18d55a3)
✔ Running tasks for staged files...
✖ Tasks modified files and --fail-on-changes was used!
↓ Cleaning up temporary files...

✖ lint-staged failed because `--fail-on-changes` was used.

Any lost modifications can be restored from a git stash:

  > git stash list --format="%h %s"
  c18d55a3 On main: lint-staged automatic backup
  > git apply --index c18d55a3

`v16.2.1`

Compare Source

Patch Changes

#1664 8277b3b Thanks @iiroj! - The built-in TypeScript types have been updated to more closely match the implementation. Notably, the list of staged files supplied to task functions is readonly string[] and can't be mutated. Thanks @outslept!
```
export default {
---  "*": (files: string[]) => void console.log('staged files', files)
+++  "*": (files: readonly string[]) => void console.log('staged files', files)
}
```
#1654 70b9af3 Thanks @iiroj! - This version has been published from GitHub Actions using Trusted Publishing for npm packages.
#1659 4996817 Thanks @iiroj! - Fix searching configuration files when the working directory is a subdirectory of a git repository, and there are package.json files in the working directory. This situation might happen when running lint-staged for a single package in a monorepo.
#1654 7021f0a Thanks @iiroj! - Return the caret semver range (^) to direct dependencies so that future patch and minor versions are allowed. This enables projects to better maintain and deduplicate their own transitive dependencies while not requiring direct updates to lint-staged. This was changed in 16.2.0 after the vulnerability issues with chalk and debug, which were also removed in the same version.

Given the recent vulnerabilities in the npm ecosystem, it's best to be very careful when updating dependencies.

`v16.2.0`

Compare Source

Minor Changes

#1615 99eb742 Thanks @iiroj! - Added a new option --fail-on-changes to make lint-staged exit with code 1 when tasks modify any files, making the precommit hook fail. This is similar to the git diff --exit-code option. Using this flag also implies the --no-revert flag which means any changes made my tasks will be left in the working tree after failing, so that they can be manually staged and the commit tried again.
#1611 cd05fd3 Thanks @rlorenzo! - Added a new option --continue-on-error so that lint-staged will run all tasks to completion even if some of them fail. By default, lint-staded will exit early on the first failure.
#1637 82fcc07 Thanks @iiroj! - Internal lint-staged errors are now thrown and visible in the console output. Previously they were caught with the process exit code set to 1, but not logged. This happens when, for example, there's a syntax error in the lint-staged configuration file.
#1647 a5ecc06 Thanks @iiroj! - Remove debug as a dependency due to recent malware issue; read more at debug-js/debug#1005. Because of this, the DEBUG environment variable is no longer supported — use the --debug to enable debugging
#1636 8db2717 Thanks @iiroj! - Added a new option --hide-unstaged so that lint-staged will hide all unstaged changes to tracked files before running tasks. The changes will be applied back after running the tasks. Note that the combination of flags --hide-unstaged --no-hide-partially-staged isn't meaningful and behaves the same as just --hide-unstaged.

Thanks to @ItsNickBarry for the idea and initial implementation in #1552.
#1648 7900b3b Thanks @iiroj! - Remove lilconfig to reduce reliance on third-party dependencies. It was used to find possible config files outside of those tracked in Git, including from the parent directories. This behavior has been moved directly into lint-staged and should work about the same.

Patch Changes

#1633 7f9e485 Thanks @dependabot! - Bumps listr2 from 9.0.3 to 9.0.4.
#1626 99d5a9b Thanks @iiroj! - Due to recent phishing attacks, for example [email protected] was released with malware. To avoid lint-staged's users being at risk the direct dependencies are pinned to exact versions, instead of allowing future patch versions with the caret (^) range.
#1588 035bbf2 Thanks @outslept! - Increase performance by listing staged files and searching for configuration concurrently.
#1645 deba3ad Thanks @iiroj! - Remove chalk as a dependency due to recent malware issue; read more at chalk/chalk#656.

If you are having trouble with ANSI color codes when using lint-staged, you can try setting either FORCE_COLOR=true or NO_COLOR=true env variables.

actions/node-versions (node)

`v22.20.0`: 22.20.0

Compare Source

Node.js 22.20.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:
  - "@&#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.

SuperchupuDev/tinyglobby (tinyglobby)

`v0.2.15`

Compare Source

Added

Documentation page at https://superchupu.dev/tinyglobby,
which also contains a library comparison page and migration guide.

It's been a huge effort that took two months to make.

Big thanks to outslept, 43081j
and benmccann for helping out! ❤️
JSDoc to all functions and options based on the online documentation page
Benchmarks with help from
43081j and benmccann
braceExpansion option
extglob option
fs option
globstar option by benmccann
signal option
package.json export as tinyglobby/package.json
Ability to pass readonly types by TomerAberbach
Support for URLs in cwd option

Changed

Rewritten path processing algorithm leading to a huge performance increase in many cases
with help from 43081j and benmccann
Deprecated using patterns inside the options object
Enabled trusted publishing using npm's OIDC support

Fixed

Negated bracket expressions i.e. [!abc]
Some patterns like +++ breaking the partial matcher

privatenumber/tsx (tsx)

`v4.20.6`

Compare Source

Bug Fixes

properly hide relaySignal from process.listeners() (#741) (710a424)

This release is also available on:

npm package (@latest dist-tag)

microsoft/TypeScript (typescript)

`v5.9.3`

Compare Source

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.

pkg-pr-new · 2025-10-01T02:33:25Z

npm i https://pkg.pr.new/zotero-plugin-scaffold@138

commit: 3481e24

fix(deps): update all non-major dependencies

3481e24

renovate Bot added the dependencies label Oct 1, 2025

northword merged commit a6cd63b into main Oct 1, 2025
7 checks passed

northword deleted the renovate/all-minor-patch branch October 1, 2025 02:40

github-actions Bot locked as resolved and limited conversation to collaborators Dec 1, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

fix(deps): update all non-major dependencies#138
northword merged 1 commit intomainfrom
renovate/all-minor-patch

renovate Bot commented Oct 1, 2025

Uh oh!

pkg-pr-new Bot commented Oct 1, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

renovate Bot commented Oct 1, 2025

Release Notes

🐞 Bug Fixes

🚀 Features

🚀 Features

🐞 Bug Fixes

🐞 Bug Fixes

🚀 Enhancements

🩹 Fixes

📖 Documentation

🏡 Chore

✅ Tests

❤️ Contributors

Fixed

Changed

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

v22.20.0: 22.20.0

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Added

Changed

Fixed

Bug Fixes

Configuration

Uh oh!

pkg-pr-new Bot commented Oct 1, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

`v22.20.0`: 22.20.0