chore(deps): update all non-major dependencies

[cu-infra-svc-git]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint-plugin-prettier	^5.1.3 -> ^5.2.1
jsii-diff (source)	^1.100.0 -> ^1.102.0
jsii-pacmak (source)	^1.100.0 -> ^1.102.0
pnpm (source)	9.1.2 -> 9.7.0
prettier (source)	^3.3.2 -> ^3.3.3
semver	^7.6.2 -> ^7.6.3
ts-jest (source)	^29.1.5 -> ^29.2.4
typescript (source)	^5.5.2 -> ^5.5.4

---

Release Notes

prettier/eslint-plugin-prettier (eslint-plugin-prettier)

v5.2.1

Compare Source

Patch Changes

• #​668 ac036cc Thanks @​OrlovAlexei! - build(deps): Bump synckit from 0.8.6 to 0.9.1

aws/jsii (jsii-diff)

v1.102.0

Compare Source

v1.101.0

Compare Source

Bug Fixes

• pacmak: Twine 5.1.0 not found (#​4554) (b4cc08c)

pnpm/pnpm (pnpm)

v9.7.0: pnpm 9.7

Compare Source

Minor Changes

• Added pnpm version management. If the manage-package-manager-versions setting is set to true, pnpm will switch to the version specified in the packageManager field of package.json #​8363. This is the same field used by Corepack. Example:

  {
    "packageManager": "pnpm@9.3.0"
  }

• Added the ability to apply patch to all versions #​8337.

  If the key of pnpm.patchedDependencies is a package name without a version (e.g. pkg), pnpm will attempt to apply the patch to all versions of the package. Failures will be skipped. If there's only one version of pkg installed, pnpm patch pkg and subsequent pnpm patch-commit $edit_dir will create an entry named pkg in pnpm.patchedDependencies. And pnpm will attempt to apply this patch to other versions of pkg in the future.

• Change the default edit dir location when running pnpm patch from a temporary directory to node_modules/.pnpm_patches/pkg[@​version] to allow the code editor to open the edit dir in the same file tree as the main project #​8379.

• Substitute environment variables in config keys #​6679.

Patch Changes

• pnpm install should run node-gyp rebuild if the project has a binding.gyp file even if the project doesn't have an install script #​8293.
• Print warnings to stderr #​8342.
• Peer dependencies of optional peer dependencies should be automatically installed #​8323.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.6.0: pnpm 9.6

Compare Source

Minor Changes

• Support specifying node version (via pnpm.executionEnv.nodeVersion in package.json) for running lifecycle scripts per each package in a workspace #​6720.
• Overrides now support the catalogs: protocol #​8303.

Patch Changes

• The pnpm deploy command now supports the catalog: protocol #​8298.
• The pnpm outdated command now supports the catalog: protocol #​8304.
• Correct the error message when trying to run pnpm patch without node_modules/.modules.yaml #​8257.
• Silent reporting fixed with the pnpm exec command #​7608.
• Add registries information to the calculation of dlx cache hash #​8299.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.5.0: pnpm 9.5

Compare Source

Minor Changes

• Added support for catalogs #​8122.

  Catalogs may be declared in the pnpm-workspace.yaml file. For example:

Default catalogs

catalog:
  chalk: ^4.1.2

Named catalogs

catalogs:
  react16:
    react: ^16.7.0
    react-dom: ^16.7.0
  react17:
    react: ^17.10.0
    react-dom: ^17.10.0
```

Then, in `package.json` files, use the `catalog:` protocol to reference a "default" or "named" catalog:

```json
{
  "dependencies": {
    "chalk": "catalog:",
    "react": "catalog:react16",
    "react-dom": "catalog:react16"
  }
}
```

Shout out to @​gluxon for implementing it!

• Bundled pnpm setup now creates the pnpx script #​8230.

Patch Changes

• Read authentication information from .npmrc in the current directory when running dlx #​7996.
• Updated @pnpm/tabtab to v0.5.4, enabling zsh autocomplete lazy loading #​8236.
• Installation with filtering will now work, when dedupe-peer-dependents is set to true #​6300.
• Fixed dlx not actually using the Node.js version specified by --use-node-version.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.4.0

Compare Source

Minor Changes

• Some registries allow the exact same content to be published under different package names and/or versions. This breaks the validity checks of packages in the store. To avoid errors when verifying the names and versions of such packages in the store, you may now set the strict-store-pkg-content-check setting to false #​4724.

Patch Changes

• Fix package-manager-strict-version missing in config #​8195.
• If install is performed on a subset of workspace projects, always create an up-to-date lockfile first. So, a partial install can be performed only on a fully resolved (non-partial) lockfile #​8165.
• Handle workspace protocol with any semver range specifier, when used in peer dependencies #​7578.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.3.0

Compare Source

Minor Changes

• Semi-breaking. Dependency key names in the lockfile are shortened if they are longer than 1000 characters. We don't expect this change to affect many users. Affected users most probably can't run install successfully at the moment. This change is required to fix some edge cases in which installation fails with an out-of-memory error or "Invalid string length (RangeError: Invalid string length)" error. The max allowed length of the dependency key can be controlled with the peers-suffix-max-length setting #​8177.

Patch Changes

• Set reporter-hide-prefix to true by default for pnpm exec. In order to show prefix, the user now has to explicitly set reporter-hide-prefix=false #​8174.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.2.0

Compare Source

Minor Changes

• If package-manager-strict-version is set to true, pnpm will fail if its version doesn't exactly match the version in the "packageManager" field of package.json.

Patch Changes

• Update @yarnpkg/pnp to the latest version, fixing issue with node: imports #​8161.
• Deduplicate bin names to prevent race condition and corrupted bin scripts #​7833.
• pnpm doesn't fail if its version doesn't match the one specified in the "packageManager" field of package.json #​8087.
• exec now also streams prefixed output when --recursive or --parallel is specified just as run does #​8065.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.1.4

Compare Source

Patch Changes

• Improved the performance of the resolution stage by changing how missing peer dependencies are detected [#​8144](https://togithub.com/pnpm/

---

Configuration

📅 Schedule: Branch creation - "before 2am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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 has been generated by Renovate Bot.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.38%. Comparing base (aba860f) to head (9c341f8).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #286   +/-   ##
=======================================
  Coverage   99.38%   99.38%           
=======================================
  Files          17       17           
  Lines        2272     2272           
  Branches      138      138           
=======================================
  Hits         2258     2258           
  Misses         14       14           

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update aba860f...9c341f8. Read the comment docs.

[cu-infra-svc-git]

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.

[github-actions]

This pull request is now marked as stale because it hasn't seen activity for a while. Add a comment or it will be closed soon. If you wish to exclude this issue from being marked as stale, add the "backlog" label.

[github-actions]

Closing this pull request as it hasn't seen activity for a while. Please add a comment @mentioning a maintainer to reopen. If you wish to exclude this issue from being marked as stale, add the "backlog" label.