Skip to content

chore(deps): update all non-major dependencies #520

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

chore(deps): update all non-major dependencies #520

merged 1 commit into from
Oct 13, 2025

Conversation

renovate[bot]
Copy link
Contributor

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

This PR contains the following updates:

Package Change Age Confidence
automd ^0.4.0 -> ^0.4.2 age confidence
esbuild ^0.25.9 -> ^0.25.10 age confidence
eslint (source) ^9.34.0 -> ^9.37.0 age confidence
jiti ^2.5.1 -> ^2.6.1 age confidence
magic-string ^0.30.18 -> ^0.30.19 age confidence
pnpm (source) 10.15.1 -> 10.18.2 age confidence
typescript (source) ^5.9.2 -> ^5.9.3 age confidence
workerd ^1.20250904.0 -> ^1.20251011.0 age confidence
wrangler (source) ^4.33.2 -> ^4.42.2 age confidence

Release Notes

unjs/automd (automd)

v0.4.2

Compare Source

compare changes

v0.4.1

Compare Source

compare changes

🩹 Fixes
  • pm-install: Use pnpm add instead of pnpm install (#​122)
  • pm, pm-install: Add npm: prefix for deno (#​115)
  • jsimport: Bun doesn't support url imports (#​112)
  • Create missing output dir (#​106)
📖 Documentation
🏡 Chore
❤️ Contributors
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 }
  @​supports (color: blue) { color: blue }
}

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

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

v9.37.0

Compare Source

v9.36.0

Compare Source

v9.35.0

Compare Source

unjs/jiti (jiti)

v2.6.1

Compare Source

compare changes

🩹 Fixes
  • interop: Only passthrough default if it is not a promise (#​408)
📦 Build
  • Revert to terser-webpack-plugin (#​407)
🏡 Chore
❤️ Contributors

v2.6.0

Compare Source

compare changes

🔥 Performance
  • Lazy load babel transform (#​405)
🩹 Fixes
  • cjs-interop: Handle function default exports (#​396)
  • Always use native for node: specifiers (#​392)
📦 Build
🏡 Chore
✅ Tests
  • Update deno and bun native test ignores (df844f8)
  • New bench script (6404427)
❤️ Contributors
  • Pooya Parsa (@​pi0)
  • Volodymyr Kolesnykov (@​sjinks)
  • Jungwoo LEE <jungwoo3490@​naver.com>
rich-harris/magic-string (magic-string)

v0.30.19

Compare Source

Bug Fixes
Features
  • replace(All) support replacement for functions when the first parameter is a string (#​304) (fd1d887)
pnpm/pnpm (pnpm)

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.
microsoft/TypeScript (typescript)

v5.9.3

Compare Source

cloudflare/workerd (workerd)

v1.20251011.0

Compare Source

What's Changed

Full Changelog: cloudflare/workerd@v1.20251010.0...v1.20251011.0

v1.20251008.0

Compare Source

What's Changed

Full Changelog: cloudflare/workerd@v1.20251007.0...v1.20251008.0

v1.20251004.0

Compare Source

What's Changed

Full Changelog: cloudflare/workerd@v1.20251003.0...v1.20251004.0

v1.20251003.0

Compare Source

What's Changed

Full Changelog: cloudflare/workerd@v1.20251002.0...v1.20251003.0

v1.20251001.0

Compare Source

What's Changed

Full Changelog: cloudflare/workerd@v1.20250930.0...v1.20251001.0

v1.20250927.0

Compare Source

What's Changed

Full Changelog: cloudflare/workerd@v1.20250926.0...v1.20250927.0

v1.20250926.0

Compare Source

What's Changed

Full Changelog: cloudflare/workerd@v1.20250925.0...v1.20250926.0

v1.20250924.0

Compare Source

What's Changed

Full Changelog: cloudflare/workerd@v1.20250923.0...v1.20250924.0

v1.20250923.0

Compare Source

What's Changed

Full Changelog: cloudflare/workerd@v1.20250922.0...v1.20250923.0

v1.20250922.0

Compare Source

What's Changed

New Contributors

Full Changelog: cloudflare/workerd@v1.20250921.0...v1.20250922.0

v1.20250921.0

Compare Source

What's Changed

Full Changelog: cloudflare/workerd@v1.20250920.0...v1.20250921.0

v1.20250920.0

Compare Source

What's Changed

Full Changelog: cloudflare/workerd@v1.20250919.0...v1.20250920.0

v1.20250919.0

Compare Source

What's Changed

Full Changelog: cloudflare/workerd@v1.20250918.0...v1.20250919.0

v1.20250918.0

Compare Source

What's Changed

Full Changelog: cloudflare/workerd@v1.20250917.0...v1.20250918.0

v1.20250917.0

Compare Source

What's Changed

Full Changelog: cloudflare/workerd@v1.20250916.0...v1.20250917.0

v1.20250913.0

Compare Source

What's Changed

New Contributors

Full Changelog: cloudflare/workerd@v1.20250912.0...v1.20250913.0

v1.20250912.0

Compare Source

What's Changed

Full Changelog: cloudflare/workerd@v1.20250911.0...v1.20250912.0

v1.20250911.0

Compare Source

What's Changed

Full Changelog: cloudflare/workerd@v1.20250910.0...v1.20250911.0

v1.20250910.0

Compare Source

What's Changed

New Contributors

Full Changelog: cloudflare/workerd@v1.20250909.0...v1.20250910.0

v1.20250909.0

Compare Source

What's Changed

Full Changelog: cloudflare/workerd@v1.20250906.0...v1.20250909.0

v1.20250906.0

Compare Source

What's Changed

Configuration

📅 Schedule: Branch creation - "after 2am and before 3am" (UTC), Automerge - "after 1am and before 2am" (UTC).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 requested a review from pi0 as a code owner September 6, 2025 02:59
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 8 times, most recently from 58e0413 to 9bb7a19 Compare September 14, 2025 22:43
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 13 times, most recently from 9834da9 to 43a4073 Compare September 22, 2025 15:29
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 8 times, most recently from 57ce758 to 4f01262 Compare September 27, 2025 02:36
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 9 times, most recently from 54e5c5c to 8003960 Compare October 6, 2025 15:28
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from b60f67e to 0cdb670 Compare October 10, 2025 03:01
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 0cdb670 to fb2bcfe Compare October 11, 2025 02:33
@pi0 pi0 merged commit 140aa99 into main Oct 13, 2025
2 checks passed
@pi0 pi0 deleted the renovate/all-minor-patch branch October 13, 2025 09:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@pi0 pi0 Awaiting requested review from pi0 pi0 is a code owner

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

@pi0