Skip to content

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

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
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

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

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 4, 2023 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
@types/node (source) ^22.14.1 -> ^22.18.1 age confidence
abitype ^1.0.8 -> ^1.1.0 age confidence
bumpp ^10.1.0 -> ^10.2.3 age confidence
pnpm (source) 10.8.0 -> 10.15.1 age confidence
simple-git-hooks ^2.12.1 -> ^2.13.1 age confidence
tsup (source) ^8.4.0 -> ^8.5.0 age confidence
typedoc (source) ^0.28.2 -> ^0.28.12 age confidence
typescript (source) ^5.8.3 -> ^5.9.2 age confidence
viem (source) ^2.26.5 -> ^2.37.5 age confidence
vitest (source) ^3.1.1 -> ^3.2.4 age confidence

Release Notes

wevm/abitype (abitype)

v1.1.0

Compare Source

Minor Changes

v1.0.9

Compare Source

Patch Changes
antfu-collective/bumpp (bumpp)

v10.2.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v10.2.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v10.2.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v10.2.0

Compare Source

   🚀 Features
    View changes on GitHub

v10.1.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub
pnpm/pnpm (pnpm)

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.

v10.14.0

Compare Source

Minor Changes

  • Added support for JavaScript runtime resolution

    Declare Node.js, Deno, or Bun in devEngines.runtime (inside package.json) and let pnpm download and pin it automatically.

    Usage example:

    {
  "devEngines": {
    "runtime": {
      "name": "node",
      "version": "^24.4.0",
      "onFail": "download" (we only support the "download" value for now)
    }
  }
}

    How it works:

    1. pnpm install resolves your specified range to the latest matching runtime version.
    2. The exact version (and checksum) is saved in the lockfile.
    3. Scripts use the local runtime, ensuring consistency across environments.

    Why this is better:

    1. This new setting supports also Deno and Bun (vs. our Node-only settings useNodeVersion and executionEnv.nodeVersion)
    2. Supports version ranges (not just a fixed version).
    3. The resolved version is stored in the pnpm lockfile, along with an integrity checksum for future validation of the Node.js content's validity.
    4. It can be used on any workspace project (like executionEnv.nodeVersion). So, different projects in a workspace can use different runtimes.
    5. For now devEngines.runtime setting will install the runtime locally, which we will improve in future versions of pnpm by using a shared location on the computer.

    Related PR: #​9755.

  • Add --cpu, --libc, and --os to pnpm install, pnpm add, and pnpm dlx to customize supportedArchitectures via the CLI #​7510.

Patch Changes
  • Fix a bug in which pnpm add downloads packages whose libc differ from pnpm.supportedArchitectures.libc.
  • The integrities of the downloaded Node.js artifacts are verified #​9750.
  • Allow dlx to parse CLI flags and options between the dlx command and the command to run or between the dlx command and -- #​9719.
  • pnpm install --prod should removing hoisted dev dependencies #​9782.
  • Fix an edge case bug causing local tarballs to not re-link into the virtual store. This bug would happen when changing the contents of the tarball without renaming the file and running a filtered install.
  • Fix a bug causing pnpm install to incorrectly assume the lockfile is up to date after changing a local tarball that has peers dependencies.

v10.13.1

Compare Source

Patch Changes
  • Run user defined pnpmfiles after pnpmfiles of plugins.

v10.13.0

Compare Source

Minor Changes

  • Added the possibility to load multiple pnpmfiles. The pnpmfile setting can now accept a list of pnpmfile locations #​9702.

  • pnpm will now automatically load the pnpmfile.cjs file from any config dependency named @pnpm/plugin-* or pnpm-plugin-* #​9729.

    The order in which config dependencies are initialized should not matter — they are initialized in alphabetical order. If a specific order is needed, the paths to the pnpmfile.cjs files in the config dependencies can be explicitly listed using the pnpmfile setting in pnpm-workspace.yaml.

Patch Changes
  • When patching dependencies installed via pkg.pr.new, treat them as Git tarball URLs #​9694.
  • Prevent conflicts between local projects' config and the global config in dangerouslyAllowAllBuilds, onlyBuiltDependencies, onlyBuiltDependenciesFile, and neverBuiltDependencies #​9628.
  • Sort keys in pnpm-workspace.yaml with deep #​9701.
  • The pnpm rebuild command should not add pkgs included in ignoredBuiltDependencies to ignoredBuilds in node_modules/.modules.yaml #​9338.
  • Replaced shell-quote with shlex for quoting command arguments #​9381.

v10.12.4

Compare Source

Patch Changes

v10.12.3

Compare Source

Patch Changes
  • Restore hoisting of optional peer dependencies when installing with an outdated lockfile.
    Regression introduced in v10.12.2 by #​9648; resolves #​9685.

v10.12.2

Compare Source

Patch Changes
  • Fixed hoisting with enableGlobalVirtualStore set to true #​9648.
  • Fix the --help and -h flags not working as expected for the pnpm create command.
  • The dependency package path output by the pnpm licenses list --json command is incorrect.
  • Fix a bug in which pnpm deploy fails due to overridden dependencies having peer dependencies causing ERR_PNPM_OUTDATED_LOCKFILE #​9595.

v10.12.1

Minor Changes

  • Experimental. Added support for global virtual stores. When enabled, node_modules contains only symlinks to a central virtual store, rather to node_modules/.pnpm. By default, this central store is located at <store-path>/links (you can find the store path by running pnpm store path).

    In the central virtual store, each package is hard linked into a directory whose name is the hash of its dependency graph. This allows multiple projects on the system to symlink shared dependencies from this central location, significantly improving installation speed when a warm cache is available.

    This is conceptually similar to how NixOS manages packages, using dependency graph hashes to create isolated and reusable package directories.

    To enable the global virtual store, set enableGlobalVirtualStore: true in your root pnpm-workspace.yaml, or globally via:

    pnpm config -g set enable-global-virtual-store true

    NOTE: In CI environments, where caches are typically cold, this setting may slow down installation. pnpm automatically disables the global virtual store when running in CI.

    Related PR: #​8190

  • The pnpm update command now supports updating catalog: protocol dependencies and writes new specifiers to pnpm-workspace.yaml.
  • Added two new CLI options (--save-catalog and --save-catalog-name=<name>) to pnpm add to save new dependencies as catalog entries. catalog: or catalog:<name> will be added to package.json and the package specifier will be added to the catalogs or catalog[<name>] object in pnpm-workspace.yaml #​9425.
  • Semi-breaking. The keys used for side-effects caches have changed. If you have a side-effects cache generated by a previous version of pnpm, the new version will not use it and will create a new cache instead #​9605.
  • Added a new setting called ci for explicitly telling pnpm if the current environment is a CI or not.
Patch Changes
  • Sort versions printed by pnpm patch using semantic versioning rules.
  • Improve the way the error message displays mismatched specifiers. Show differences instead of 2 whole objects #​9598.
  • Revert #​9574 to fix a regression #​9596.

v10.11.1

Compare Source

Patch Changes
  • Fix an issue in which pnpm deploy --legacy creates unexpected directories when the root package.json has a workspace package as a peer dependency #​9550.
  • Dependencies specified via a URL that redirects will only be locked to the target if it is immutable, fixing a regression when installing from GitHub releases. (#​9531)
  • Installation should not exit with an error if strictPeerDependencies is true but all issues are ignored by peerDependencyRules #​9505.
  • Use pnpm_config_ env variables instead of npm_config_ #​9571.
  • Fix a regression (in v10.9.0) causing the --lockfile-only flag on pnpm update to produce a different pnpm-lock.yaml than an update without the flag.
  • Let pnpm deploy work in repos with overrides when inject-workspace-packages=true #​9283.
  • Fixed the problem of path loss caused by parsing URL address. Fixes a regression shipped in pnpm v10.11 via #​9502.
  • pnpm -r --silent run should not print out section #​9563.

v10.11.0

Compare Source

Minor Changes

  • A new setting added for pnpm init to create a package.json with type=module, when init-type is module. Works as a flag for the init command too #​9463.

  • Added support for Nushell to pnpm setup #​6476.

  • Added two new flags to the pnpm audit command, --ignore and --ignore-unfixable #​8474.

    Ignore all vulnerabilities that have no solution:

    > pnpm audit --ignore-unfixable

    Provide a list of CVE's to ignore those specifically, even if they have a resolution.

    > pnpm audit --ignore=CVE-2021-1234 --ignore=CVE-2021-5678

  • Added support for recursively running pack in every project of a workspace #​4351.

    Now you can run pnpm -r pack to pack all packages in the workspace.

Patch Changes
  • pnpm version management should work, when dangerouslyAllowAllBuilds is set to true #​9472.
  • pnpm link should work from inside a workspace #​9506.
  • Set the default workspaceConcurrency to Math.min(os.availableParallelism(), 4) #​9493.
  • Installation should not exit with an error if strictPeerDependencies is true but all issues are ignored by peerDependencyRules #​9505.
  • Read updateConfig from pnpm-workspace.yaml #​9500.
  • Add support for recursive pack
  • Remove url.parse usage to fix warning on Node.js 24 #​9492.
  • pnpm run should be able to run commands from the workspace root, if ignoreScripts is set tot true #​4858.

v10.10.0

Compare Source

Minor Changes
  • Allow loading the preResolution, importPackage, and fetchers hooks from local pnpmfile.
Patch Changes
  • Fix cd command, when shellEmulator is true #​7838.
  • Sort keys in pnpm-workspace.yaml #​9453.
  • Pass the npm_package_json environment variable to the executed scripts #​9452.
  • Fixed a mistake in the description of the --reporter=silent option.

v10.9.0

Compare Source

Minor Changes

  • Added support for installing JSR packages. You can now install JSR packages using the following syntax:

    pnpm add jsr:<pkg_name>

    or with a version range:

    pnpm add jsr:<pkg_name>@&#8203;<range>

    For example, running:

    pnpm add jsr:@&#8203;foo/bar

    will add the following entry to your package.json:

    {
  "dependencies": {
    "@&#8203;foo/bar": "jsr:^0.1.2"
  }
}

    When publishing, this entry will be transformed into a format compatible with npm, older versions of Yarn, and previous pnpm versions:

    {
  "dependencies": {
    "@&#8203;foo/bar": "npm:@&#8203;jsr/foo__bar@^0.1.2"
  }
}

    Related issue: #​8941.

    Note: The @jsr scope defaults to https://npm.jsr.io/ if the @jsr:registry setting is not defined.

  • Added a new setting, dangerouslyAllowAllBuilds, for automatically running any scripts of dependencies without the need to approve any builds. It was already possible to allow all builds by adding this to pnpm-workspace.yaml:

    neverBuiltDependencies: []

    dangerouslyAllowAllBuilds has the same effect but also allows to be set globally via:

    pnpm config set dangerouslyAllowAllBuilds true

    It can also be set when running a command:

    pnpm install --dangerously-allow-all-builds
Patch Changes
  • Fix a false negative in verifyDepsBeforeRun when nodeLinker is hoisted and there is a workspace package without dependencies and node_modules directory #​9424.
  • Explicitly drop verifyDepsBeforeRun support for nodeLinker: pnp. Combining verifyDepsBeforeRun and nodeLinker: pnp will now print a warning.

v10.8.1

Compare Source

Patch Changes
  • Removed bright white highlighting, which didn't look good on some light themes #​9389.
  • If there is no pnpm related configuration in package.json, onlyBuiltDependencies will be written to pnpm-workspace.yaml file #​9404.
toplenboren/simple-git-hooks (simple-git-hooks)

v2.13.1

Compare Source

Patch Changes

v2.13.0

Compare Source

Minor Changes
egoist/tsup (tsup)

v8.5.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
TypeStrong/TypeDoc (typedoc)

v0.28.12

Compare Source

Bug Fixes
  • Variables marked with @enum now work for symbols imported from another module, #​3003.
  • Improved magic introduced with #​2999 to work with imported symbols, #​3003.
  • Fixed relative link resolution to file names containing percent encoded URLs, #​3006.
  • Linking to the project's README file with a relative link will now behave as expected, #​3006.
  • Reduced unnecessary HTML element rendering in default theme.
    API: Reflection.hasComment and Comment.hasVisibleComponent now accepts an optional notRenderedTags parameter.

v0.28.11

Compare Source

Features
  • Object properties declared with shorthand property assignment will now use the variable's comment
    if they do not have their own comment, #​2999.
Bug Fixes
  • Fixed link resolution not working correctly in first comment on the file in some cases, #​2994.
  • Optional methods are now rendered with a trailing ? in the reflection preview and signature, #​2995.
  • The compilerOptions option now functions properly with non-boolean options, #​3000.
  • Configuration errors within the compilerOptions option are now handled gracefully, #​3000.
  • Fixed improper casing of "Type Declaration" header, #​3002.

v0.28.10

Compare Source

Bug Fixes
  • Fixed inconsistent anchors on module pages for re-exports, #​2990.
  • Markdown references which appear to be footnotes will no longer be checked for links, #​2991.

v0.28.9

Compare Source

Features
  • Add support for TypeScript 5.9, #​2989.
Bug Fixes
  • Fixed bug introduced in 0.28.8 where TypeDoc could not render docs when members inherited from a complex type alias, #​2982.
  • Fixed automatic discovery of entry points when not running in packages mode, #​2988.
  • Fixed discovery of package.json file when running with entry points containing a glob, #​2985.

v0.28.8

Compare Source

Features
  • If using JS config files, the plugin function can now be given plugin functions to load.
  • Permit - within tag names to support typescript-json-schema's @TJS-type tag, #​2972.
  • Exposed Context.createSymbolId for use by plugins.
Bug Fixes
  • Relative links in <img srcset> will now be discovered by TypeDoc, #​2975.
  • Relative links in <source src> and <source srcset> elements will now be discovered by TypeDoc, #​2975.
  • Improved inherited from/overwrites link discovery to point to parent properties in more cases, #​2978
Thanks!

v0.28.7

Compare Source

Features
  • Introduced the @sortStrategy tag to override the sort option on a specific reflection, #​2965.
Bug Fixes
  • Classes and functions exported with export { type X } are no longer missing comments, #​2970.
  • Setting locale to an unknown value will now cause TypeDoc to operate in English instead of a debug locale.
  • Array options will now report an error if set to a non-array/non-string value.

v0.28.6

Compare Source

Features
  • TypeDoc now supports resolving relative paths in links to the package directory as belonging to the project, #​2961.
  • Declarations without comments will now check for comments on their export specifier, #​2964.
Bug Fixes
  • Attempting to highlight a supported language which is not enabled is now a warning, not an error, #​2956.
  • Improved compatibility with CommonMark's link parsing, #​2959.
  • Classes, variables, and functions exported with export { type X } are now detected and converted as interfaces/type aliases, #​2962.
  • Improved warning messaging for links to symbols which were resolved, but the symbols were not included in the documentation, #​2967.
  • Fixed an issue preventing nested documents from being deserialized from TypeDoc's JSON output or used in packages mode, #​2969.
Thanks!

v0.28.5

Compare Source

Bug Fixes
  • References to type aliases defined as mapped types will now correctly create a reference to the type alias, #​2954.
  • ignoredHighlightLanguages can now be used to prevent warnings for codeblocks containing languages
    which are supported by Shiki but are not loaded, #​2956.

v0.28.4

Compare Source

Features
  • The navigation in the default theme will now attempt to break long names onto multiple lines, #​2940.
  • Added German (de) localization, #​2941.
Bug Fixes
  • TypeDoc's default theme now uses the same chevron for all collapsible elements, #​2924
    The chevronSmall helper is now deprecated and will be removed with v0.29.0.
  • Classes/interfaces marked with @hidden will no longer appear in the
    "Hierarchy" section of the docs.
  • TypeDoc now handles wildcard JSDoc types, #​2949.
Thanks!

v0.28.3

Compare Source

Bug Fixes
  • @inline now functions when referencing tuple types, #​2932.
  • @link links to the current page are now rendered, #​2934.
  • @includeCode now supports regions in TypeScript files with .mts and .cts file extensions, #​2935.
  • Aliased symbols (re-exports) are now resolved before checking if they are excluded/external, #​2937.
  • Improved error reporting when paths including Windows separators are provided as globs, #​2938.
microsoft/TypeScript (typescript)

v5.9.2

Compare Source

wevm/viem (viem)

v2.37.5

Compare Source

Patch Changes

v2.37.4

Compare Source

Patch Changes

v2.37.3

Compare Source

Patch Changes

v2.37.2

Compare Source

Patch Changes

v2.37.1

Compare Source

Patch Changes

v2.37.0

Compare Source

Minor Changes

v2.36.1

Compare Source

Patch Changes

v2.36.0

Compare Source

Minor Changes
Patch Changes

v2.35.1

Compare Source

Patch Changes

v2.35.0

Compare Source

Minor Changes
Patch Changes

v2.34.0

Compare Source

Minor Changes
Patch Changes

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 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 renovate bot added the dependencies label Sep 4, 2023
@netlify
Copy link

netlify bot commented Sep 4, 2023 •
edited
Loading

❌ Deploy Preview for crossbell-js failed.

Name Link
🔨 Latest commit cec1476
🔍 Latest deploy log https://app.netlify.com/projects/crossbell-js/deploys/68bff2aed675610008fa17f8

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 10 times, most recently from 8c411ef to 0567274 Compare September 11, 2023 01:56
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 0567274 to fd45ca1 Compare September 11, 2023 13:31
@renovate renovate bot changed the title chore(deps): update all non-major dependencies chore(deps): update pnpm to v8.7.5 Sep 12, 2023
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 50cb4bf to cad77b7 Compare September 14, 2023 00:28
@renovate renovate bot changed the title chore(deps): update pnpm to v8.7.5 chore(deps): update all non-major dependencies Sep 14, 2023
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from cad77b7 to 36c4563 Compare September 14, 2023 00:50
@renovate renovate bot changed the title chore(deps): update all non-major dependencies fix(deps): update dependency viem to ^1.10.12 Sep 14, 2023
@renovate renovate bot changed the title fix(deps): update dependency viem to ^1.10.12 fix(deps): update dependency viem to ^1.10.13 Sep 14, 2023
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from c72110d to db5e98a Compare September 15, 2023 01:26
@renovate renovate bot changed the title fix(deps): update dependency viem to ^1.10.13 fix(deps): update dependency viem to ^1.10.14 Sep 15, 2023
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from db5e98a to faf19cf Compare September 15, 2023 09:31
@renovate renovate bot changed the title fix(deps): update dependency viem to ^1.10.14 chore(deps): update all non-major dependencies Sep 15, 2023
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from f23bb74 to 37441f8 Compare September 20, 2023 00:15
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 76bcf99 to 7f13d74 Compare August 1, 2025 18:53
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from c87b229 to 217d863 Compare August 12, 2025 01:55
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 6acbf7f to 562420a Compare August 19, 2025 19:42
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 15057a6 to 2a7c653 Compare August 31, 2025 09:37
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 8 times, most recently from f33af3d to 447caf4 Compare September 7, 2025 10:01
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 447caf4 to cec1476 Compare September 9, 2025 09:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants