Skip to content
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

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

Merged
merged 1 commit into from Sep 23, 2022
Merged

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

merged 1 commit into from Sep 23, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 19, 2022 •
edited

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@sanity/client (source) ^3.3.7 -> ^3.4.1 age adoption passing confidence
@vercel/nft 0.18.2 -> 0.22.1 age adoption passing confidence
@vitest/coverage-c8 ^0.22.1 -> ^0.23.4 age adoption passing confidence
pnpm (source) 7.5.2 -> 7.12.2 age adoption passing confidence
release-it ^15.3.0 -> ^15.4.2 age adoption passing confidence
typescript (source) ^4.7.4 -> ^4.8.3 age adoption passing confidence
vitest ^0.22.1 -> ^0.23.4 age adoption passing confidence

Release Notes

sanity-io/client

v3.4.1

Compare Source

  • fix(typings): fetch() does not need to return record

v3.4.0

Compare Source

  • feat: allow setting allowReconfigure to false to prevent reconfiguration of existing client instance
vercel/nft

v0.22.1

Compare Source

Patches
  • Chore: Bump moment-timezone from 0.5.33 to 0.5.37: #​308
  • Revert "major: assets should not be parsed": #​309

v0.22.0

Compare Source

Changes
  • Major: assets should not be parsed: #​304

v0.21.0

Compare Source

Minor Changes
  • Feat: Support fs-extra and graceful-fs: #​296
  • Fix: add concurrency limit to fs calls: #​301
Credits

Huge thanks to @​kachkaev and @​Brooooooklyn for helping!

v0.20.1

Compare Source

Changes
  • Fix: remove node-pre-gyp dependency: #​299
  • Chore: Bump shell-quote from 1.7.2 to 1.7.3: #​298

v0.20.0

Compare Source

Changes
  • Feat: Allow all file extension inputs (including .jsx): #​294
  • Chore: Bump sharp from 0.30.0 to 0.30.5: #​291
  • Chore: Bump protobufjs from 6.10.2 to 6.11.3: #​292
  • Chore: Windows tests should preserve yarn.lock: #​295

v0.19.1

Compare Source

Patches
  • Fix: handle static eval for sequence expression (fix TS 4.4+): #​289

v0.19.0

Compare Source

Minor Changes
  • Fix: handle node: prefix: #​285
  • Fix: node-gyp-build binary locating in different versions: #​286
  • Chore: Update node prefix tests: #​287
Credits

Huge thanks to @​Rich-Harris for helping!

vitest-dev/vitest

v0.23.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.23.2

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.23.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.23.0

Compare Source

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
pnpm/pnpm

v7.12.2

Compare Source

Patch Changes

  • Don't crash when auto-install-peers is true and the project has many complex circular dependencies #​5394.
  • pnpm link --global should work with the --dir=<path> option #​5371.

Our Gold Sponsors

Our Silver Sponsors

What's Changed

New Contributors

Full Changelog: pnpm/pnpm@v7.12.1...v7.12.2

v7.12.1

Compare Source

Patch Changes

  • Deduplicate peer dependencies when automatically installing them #​5373.

Our Gold Sponsors

Our Silver Sponsors

What's Changed

Full Changelog: pnpm/pnpm@v7.12.0...v7.12.1

v7.12.0

Compare Source

Minor Changes

  • A new setting supported in the pnpm section of the package.json file: allowNonAppliedPatches. When it is set to true, non-applied patches will not cause an error, just a warning will be printed. For example:

    {
  "name": "foo",
  "version": "1.0.0",
  "pnpm": {
    "patchedDependencies": {
      "express@4.18.1": "patches/express@4.18.1.patch"
    },
    "allowNonAppliedPatches": true
  }
}

  • Now it is possible to exclude packages from hoisting by prepending a ! to the pattern. This works with both the hoist-pattern and public-hoist-pattern settings. For instance:

    public-hoist-pattern[]='*types*'
public-hoist-pattern[]='!@&#8203;types/react'

hoist-pattern[]='*eslint*'
hoist-pattern[]='!*eslint-plugin*'

    Ref #​5272

Patch Changes

  • When the same dependency with missing peers is used in multiple workspace projects, install the missing peers in each workspace project #​4820.
  • pnpm patch should work on files that don't have an end of line #​5320.
  • Fix pnpm patch using a custom --edit-dir.

Our Gold Sponsors

Our Silver Sponsors

What's Changed

New Contributors

Full Changelog: pnpm/pnpm@v7.11.0...v7.12.0

v7.11.0

Compare Source

Minor Changes

  • pnpm patch: edit the patched package in a directory specified by the --edit-dir option. E.g., pnpm patch express@3.1.0 --edit-dir=/home/xxx/src/patched-express #​5304

Patch Changes

  • Auto installing a peer dependency in a workspace that also has it as a dev dependency in another project #​5144.
  • When an error happens during installation of a subdependency, print some context information in order to be able to locate that subdependency. Print the exact chain of packages that led to the problematic dependency.

Our Gold Sponsors

Our Silver Sponsors

What's Changed

New Contributors

Full Changelog: pnpm/pnpm@v7.10.0...v7.11.0

v7.10.0

Compare Source

Minor Changes

  • New time-based resolution strategy supported.

    When resolution-mode is set to time-based, pnpm will resolve dependencies the following way:

    1. Direct dependencies will be resolved to their lowest versions. So if there is foo@^1.1.0 in the dependencies, then 1.1.0 will be installed.
    2. Subdependencies will be resolved from versions that were published before the last direct dependency was published.

    With this resolution mode installations with hot cache are faster. It also reduces the chance of subdependency hijacking as subdependencies will be updated only if direct dependencies are updated.

    This resolution mode works only with npm's full metadata. So it is slower in some scenarios. However, if you use Verdaccio v5.15.1 or newer, you may set the registry-supports-time-field setting to true, and it will be really fast.

    Related RFC.

  • Enhance pnpm env with the remove command. To remove a Node.js version installed by pnpm, run:

    pnpm env remove --global <node.js version>

Patch Changes

  • pnpm store prune should remove all cached metadata.
  • Don't modify the manifest of the injected workspace project, when it has the same dependency in prod and peer dependencies.

Our Gold Sponsors

Our Silver Sponsors

What's Changed

New Contributors

Full Changelog: pnpm/pnpm@v7.9.5...v7.10.0

v7.9.5

Compare Source

Patch Changes
  • Set NODE_PATH when prefer-symlinked-executables is enabled #​5251.
  • Fail with a meaningful error when the audit endpoint doesn't exist #​5200.
  • Symlink a local dependency to node_modules, even if the target directory doesn't exist #​5219.
Our Gold Sponsors
Our Silver Sponsors
What's Changed
New Contributors

Full Changelog: pnpm/pnpm@v7.9.4...v7.9.5

v7.9.4

Compare Source

Patch Changes

  • Auto install peer dependencies when auto-install-peers is set to true and the lockfile is up to date #​5213.
  • pnpm env: for Node.js<16 install the x64 build on Darwin ARM as ARM build is not available #​5239.
  • pnpm env: log a message when the node.js tarball starts the download #​5241.
  • Fix pnpm install --merge-git-branch-lockfile when the lockfile is up to date #​5212.

Our Gold Sponsors

Our Silver Sponsors

What's Changed

New Contributors

Full Changelog: pnpm/pnpm@v7.9.3...v7.9.4

v7.9.3

Compare Source

Patch Changes

  • Remove legacy signal handlers #​5224

Our Gold Sponsors

Our Silver Sponsors

What's Changed

Full Changelog: pnpm/pnpm@v7.9.2...v7.9.3

v7.9.2

Compare Source

Patch Changes

  • When the same package is both in "peerDependencies" and in "dependencies", treat this dependency as a peer dependency if it may be resolved from the dependencies of parent packages #​5210.
  • Update node-gyp to v9.
  • Update the compatibility database.

Our Gold Sponsors

Our Silver Sponsors

v7.9.1

Compare Source

Patch Changes

  • pnpm setup: don't use setx to set env variables on Windows.

Our Gold Sponsors

Our Silver Sponsors

v7.9.0

Compare Source

Minor Changes

  • When ignore-dep-scripts is true, ignore scripts of dependencies but run the scripts of the project.
  • When ignore-compatibility-db is set to true, the compatibility database will not be used to patch dependencies #​5132.
  • Print the versions of packages in peer dependency warnings and errors.
  • Support a new hook for passing a custom package importer to the store controller.

Patch Changes

  • Don't print the same deprecation warning multiple times.
  • On POSIX pnpm setup should suggest users to source the config instead of restarting the terminal.
  • Installing a package with bin that points to an .exe file on Windows #​5159.
  • Fix bug where the package manifest was not resolved if verify-store-integrity is set to false.
  • Fix sorting of keys in lockfile to make it more deterministic and prevent unnecessary churn in the lockfile #​5151.
  • Don't create a separate bundle for pnpx.

Our Gold Sponsors

Our Silver Sponsors

v7.8.0

Compare Source

Minor Changes

  • When publishConfig.directory is set, only symlink it to other workspace projects if publishConfig.linkDirectory is set to true. Otherwise, only use it for publishing #​5115.

Patch Changes

  • Don't incorrectly identify a lockfile out-of-date when the package has a publishConfig.directory field #​5124.
  • Don't crash when a config file contains a setting with an env variable that doesn't exist #​5093.

Our Gold Sponsors

Our Silver Sponsors

config help if that's undesired.

  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

@netlify
Copy link

netlify bot commented Sep 11, 2022 •
edited

✅ Deploy Preview for nuxt-sanity-module canceled.

Name Link
🔨 Latest commit d0fb790
🔍 Latest deploy log https://app.netlify.com/sites/nuxt-sanity-module/deploys/632cf5128e1a700009a6a693

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 11 times, most recently from bbf7557 to 8dc596f Compare September 18, 2022 21:37
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 3f2a355 to d2fffce Compare September 22, 2022 20:58
@danielroe danielroe merged commit 9ff5870 into main Sep 23, 2022
@danielroe danielroe deleted the renovate/all-minor-patch branch September 23, 2022 10:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@danielroe danielroe

Labels
dependencies devops
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
1 participant
@danielroe