Update all non-major dependencies

[renovate]

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
3d-tiles-renderer	~0.4.14 -> ~0.4.17
@needle-tools/gltf-progressive (source)	~3.2.0 -> ~3.3.4
@needle-tools/three-animation-pointer	~1.0.1 -> ~1.0.3
dprint	^0.50.1 -> ^0.50.2
pnpm (source)	10.14.0 -> 10.17.1
pnpm (source)	10.14.0 -> 10.17.1

---

Release Notes

NASA-AMMOS/3DTilesRendererJS (3d-tiles-renderer)

v0.4.17

Compare Source

Added

• LoadRegionPlugin: Added support for "mask" regions that allow for only loading tiles within the shape.
• Added WMSTilesOverlay & WMSTilesPlugin for displaying and overlaying WMS image tiles.
• I3DMLoader: Add support for quantized position data.
• Added in-progress "GeoJSONOverlay" for overlaying GeoJSON data.

Fixed

• Fixed types not being defined correctly in the package.json.
• ImageOverlays: Fixed case where overlay textures were generated even when no content was present.
• TilesRenderer.manager checking for a non existent "preprocessURL" function when transforming a URL.

v0.4.16

Compare Source

Fixed

• GlobeControls: Fix case where camera position could become "NaN" when zooming into the sky.
• Fixed built files possibly not being correctly bundled.

v0.4.15

Compare Source

Changed

• Adjusted the package to export a bundled version of the library.
• Some execution timing of react components may have changed.
• LoadRegionPlugin: "Region" constructors have changed to take options as an object rather than individual arguments.
• TilesRenderer Plugins: Return value for "calculateTileViewError" has been added.

Fixed

• Fixed bug introduced when loading GoogleMapsOverlay with ImageOverlayPlugin.
• ImageFormatPlugin types.
• DebugTilesRenderer: fix case where disabling and reenabling the plugin could cause errors.
• QuantizedMeshPlugin: fix case where quantized mesh could not expand to the lowest levels of detail.
• Fixed behavior of TilesRenderer and TilesPlugin components in "strict mode" with React 19.
• Improved performance of extracting url file extensions.
• Fixed case where a loaders "working path" was not generated correctly.
• BatchTable, FeatureTable: Filter the reserved "extensions" field from the batch data "getKeys" function.

needle-tools/gltf-progressive (@​needle-tools/gltf-progressive)

v3.3.4

Compare Source

• Fix: import with missing .js extension

v3.3.3

Compare Source

• Update documentation and add an initial extension definition

v3.3.2

Compare Source

• Update KTX2 transcoder

v3.3.1

Compare Source

• Add: waitForFirstCapture option to LodsManager (e.g. lodsManager.awaitLoading({waitForFirstCapture: true})) to be able to not resolve the promise until at any promise has been capture (e.g. any LOD has started and finished loading). If necessary a signal can be provided to timeout.

v3.3.0

Compare Source

• Add LODsManager overrideLodLevel property. When set to a number >= 0 texture and mesh LODs will be loaded for that level

needle-tools/three-animation-pointer (@​needle-tools/three-animation-pointer)

v1.0.3

Compare Source

• Fix: Handle undefined path if AnimationClip tracks have invalid/unexpected names. Fallback to default three implementation

v1.0.2

Compare Source

dprint/dprint (dprint)

v0.50.2

Compare Source

Changes

• fix: upgrade wasmer to 6.1.0-rc.3 to fix build failure with Rust ≥ 1.89.0 (#​1021)
• fix: ignore empty proxy env (#​1014)

Install

Run dprint upgrade or see https://dprint.dev/install/

Checksums

Artifact	SHA-256 Checksum
dprint-x86_64-apple-darwin.zip	61becbf8d1b16540e364a4f00be704266ae322ee0ff3ba66a4a21033f66a8d55
dprint-aarch64-apple-darwin.zip	f534bcc054947ab2a42c069b5f6027914d252729bd15c1109812313b35a662a5
dprint-x86_64-pc-windows-msvc.zip	2dbdb57106818acd930a00bc0c2c33370bd4c7265f78a6cda000e3621f2d3c1c
dprint-x86_64-pc-windows-msvc-installer.exe	0b2dab815dd68501b7418831157a907a4db89b84b623a71c1deb486a08244b83
dprint-x86_64-unknown-linux-gnu.zip	95c7e633a67531ffc4990c152d59ed0802e1c0caf7e27e424e9cea9ef3d499d4
dprint-x86_64-unknown-linux-musl.zip	4b0e7911262049ccb8e1ac5968bf7a66dc490968fe1552a123bb2d6dadf2ad95
dprint-aarch64-unknown-linux-gnu.zip	039d4dca4360cb6622a2b56c3fc29ea71c356cd954e0b9566bff1a70e75beda8
dprint-aarch64-unknown-linux-musl.zip	a4982964a68aefc2720b4c79c51a57e49b32f8944c1641fd9e714503fcf01847
dprint-riscv64gc-unknown-linux-gnu.zip	6918c45b0070da1da137fa328c7ca82133c6ab0b49a651fa53513305611fe3a8

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.

  @​apollo/client 4.0.4
  ├── @​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:

  @​apollo/client 4.0.4
  ├── @​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["@​babel/parser"].peerDependencies["@​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.

---

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.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.