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 #36

Merged
merged 1 commit into from
Mar 16, 2023
Merged

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

merged 1 commit into from
Mar 16, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 27, 2023 •
edited

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@sxzz/eslint-config-prettier ^2.4.4 -> ^2.4.5 age adoption passing confidence
@sxzz/eslint-config-ts ^2.4.4 -> ^2.4.5 age adoption passing confidence
@types/node (source) ^18.13.0 -> ^18.15.3 age adoption passing confidence
eslint (source) ^8.34.0 -> ^8.36.0 age adoption passing confidence
eslint-define-config ^1.15.0 -> ^1.16.0 age adoption passing confidence
pnpm (source) 7.27.0 -> 7.29.3 age adoption passing confidence
tsup (source) ^6.6.2 -> ^6.6.3 age adoption passing confidence
tsx ^3.12.3 -> ^3.12.5 age adoption passing confidence
vitest ^0.28.5 -> ^0.29.2 age adoption passing confidence

Release Notes

eslint/eslint

v8.36.0

Compare Source

Features

Bug Fixes

  • 92c1943 fix: correctly iterate files matched by glob patterns (#​16831) (Nitin Kumar)

Documentation

  • b98fdd4 docs: Update README (GitHub Actions Bot)
  • caf08ce docs: fix estree link in custom formatters docs (#​16967) (Milos Djermanovic)
  • 3398431 docs: Custom Parsers cleanup/expansion (#​16887) (Ben Perlmutter)
  • 19d3531 docs: Update README (GitHub Actions Bot)
  • b09a512 docs: detect and fix broken links (#​16837) (Nitin Kumar)

Chores

v8.35.0

Compare Source

Features

  • 8e34a04 feat: add afterHashbangComment option to lines-around-comment rule (#​16920) (SUZUKI Sosuke)
  • c8c0c71 feat: Move all and recommended configs into package. (#​16844) (Nicholas C. Zakas)
  • 71f6f0d feat: report more cases with ?? in no-constant-binary-expression (#​16826) (Daiki Nishikawa)

Bug Fixes

Documentation

Chores

Shinigami92/eslint-define-config

v1.16.0

Compare Source

diff

  • Fix and sync config.rule type to eslint Linter.Rule (#​172)
  • Update rules for: [eslint, typescript-eslint, graphql, jsdoc, unicorn, vue-pug]
pnpm/pnpm

v7.29.3

Compare Source

Patch Changes

  • Command shim should not set higher priority to the node_modules/.pnpm/node_modules directory through the NODE_PATH env variable, then the command's own node_modules directory #​5176.
  • extend-node-path is set back to true by default. It was set to false in v7.29.2 in order to fix issues with multiple versions of Jest in one workspace. It has caused other issues, so now we keep extending NODE_PATH. We have fixed the Jest issue with a different solution #​6213.

Our Gold Sponsors

Our Silver Sponsors

v7.29.2

Compare Source

Patch Changes

  • Clean up child processes when process exited #​6162.
  • When patch package does not specify a version, use locally installed version by default #​6192.
  • patchedDependencies are now sorted consistently in the lockfile #​6208.
  • Don't extend NODE_PATH in command shims #​5176.
  • Retry copying file on EBUSY error #​6201.

Our Gold Sponsors

Our Silver Sponsors

v7.29.1

Compare Source

Patch Changes

  • Settings related to authorization should be set/deleted by npm CLI #​6181.

Our Gold Sponsors

Our Silver Sponsors

v7.29.0

Compare Source

Minor Changes

  • A new setting is now supported: dedupe-peer-dependents.

    When this setting is set to true, packages with peer dependencies will be deduplicated after peers resolution.

    For instance, let's say we have a workspace with two projects and both of them have webpack in their dependencies. webpack has esbuild in its optional peer dependencies, and one of the projects has esbuild in its dependencies. In this case, pnpm will link two instances of webpack to the node_modules/.pnpm directory: one with esbuild and another one without it:

    node_modules
  .pnpm
    webpack@1.0.0_esbuild@1.0.0
    webpack@1.0.0
project1
  node_modules
    webpack -> ../../node_modules/.pnpm/webpack@1.0.0/node_modules/webpack
project2
  node_modules
    webpack -> ../../node_modules/.pnpm/webpack@1.0.0_esbuild@1.0.0/node_modules/webpack
    esbuild

    This makes sense because webpack is used in two projects, and one of the projects doesn't have esbuild, so the two projects cannot share the same instance of webpack. However, this is not what most developers expect, especially since in a hoisted node_modules, there would only be one instance of webpack. Therefore, you may now use the dedupe-peer-dependents setting to deduplicate webpack when it has no conflicting peer dependencies (explanation at the end). In this case, if we set dedupe-peer-dependents to true, both projects will use the same webpack instance, which is the one that has esbuild resolved:

    node_modules
  .pnpm
    webpack@1.0.0_esbuild@1.0.0
project1
  node_modules
    webpack -> ../../node_modules/.pnpm/webpack@1.0.0_esbuild@1.0.0/node_modules/webpack
project2
  node_modules
    webpack -> ../../node_modules/.pnpm/webpack@1.0.0_esbuild@1.0.0/node_modules/webpack
    esbuild

    What are conflicting peer dependencies? By conflicting peer dependencies we mean a scenario like the following one:

    node_modules
  .pnpm
    webpack@1.0.0_react@16.0.0_esbuild@1.0.0
    webpack@1.0.0_react@17.0.0
project1
  node_modules
    webpack -> ../../node_modules/.pnpm/webpack@1.0.0/node_modules/webpack
    react (v17)
project2
  node_modules
    webpack -> ../../node_modules/.pnpm/webpack@1.0.0_esbuild@1.0.0/node_modules/webpack
    esbuild
    react (v16)

    In this case, we cannot dedupe webpack as webpack has react in its peer dependencies and react is resolved from two different versions in the context of the two projects.

Patch Changes

  • The configuration added by pnpm setup should check if the pnpm home directory is already in the PATH before adding to the PATH.

    Before this change, this code was added to the shell:

    export PNPM_HOME="$HOME/Library/pnpm"
export PATH="$PNPM_HOME:$PATH"

    Now this will be added:

    export PNPM_HOME="$HOME/Library/pnpm"
case ":$PATH:" in
  *":$PNPM_HOME:"*) ;;
  *) export PATH="$PNPM_HOME:$PATH" ;;
esac

  • Add skipped status in exec report summary when script is missing #​6139.

  • pnpm env -g should fail with a meaningful error message if pnpm cannot find the pnpm home directory, which is the directory into which Node.js is installed.

  • Should not throw an error when local dependency use file protocol #​6115.

  • Fix the incorrect error block when subproject has been patched #​6183

Our Gold Sponsors
Our Silver Sponsors

v7.28.0

Compare Source

Minor Changes

  • Add --report-summary for pnpm exec and pnpm run #​6008.
  • Show path info for pnpm why --json or --long #​6103.
  • Extend the pnpm.peerDependencyRules.allowedVersions package.json option to support the parent>child selector syntax. This syntax allows for extending specific peerDependencies #​6108.

Patch Changes

  • Update the lockfile if a workspace has a new project with no dependencies.
  • Fix a case of installs not being deterministic and causing lockfile changes between repeat installs. When a dependency only declares peerDependenciesMeta and not peerDependencies, dependencies, or optionalDependencies, the dependency's peers were not considered deterministically before.
  • patch-commit should auto apply patches in workspaces #​6048
  • Automatically fix conflicts in v6 lockfile.
  • pnpm config set should write to the global config file by default #​5877.

Our Gold Sponsors

Our Silver Sponsors

v7.27.1

Compare Source

Patch Changes
  • Add store path description to the pnpm cli help.
  • Print a hint that suggests to run pnpm store prune, when a tarball integrity error happens.
  • Don't retry installation if the integrity checksum of a package failed and no lockfile was present.
  • Fail with a meaningful error message when cannot parse a proxy URL.
  • The strict-ssl, ca, key, and cert settings should work with HTTPS proxy servers #​4689.
Our Gold Sponsors
Our Silver Sponsors
egoist/tsup

v6.6.3

Compare Source

Bug Fixes
esbuild-kit/tsx

v3.12.5

Compare Source

Bug Fixes
  • watch: ignore hidden files (afa3c78)

v3.12.4

Compare Source

Bug Fixes
vitest-dev/vitest

v0.29.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.29.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.29.0

Compare Source

This release makes some significant changes to how tests are running. If you were using --no-threads before, you might consider enabling --single-thread instead (because your tests are now running in child_process instead of a worker thread) or try our new performance optimization feature (discussed later). If you were relying on API that was not available inside a worker (like process.chdir(), you can now use this option.

One of the potential breaking bug fixes is that environments do not share the same global scope anymore if you run them with --no-isolate, --no-threads or --single-thread - you might need to update your setup files if you were relying on a global variable before.

If you had performance issues on large code bases before, try the new deps.experimentalOptimizer option instead of disabling threads. Feedback is welcome!

One of the breaking changes includes adding a link to snapshots inside snapshot files, meaning you will need to update all your snapshots.

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

Configuration

📅 Schedule: Branch creation - "before 3am on Monday" (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 has been generated by Mend Renovate. View repository job log here.

@stackblitz
Copy link

stackblitz bot commented Feb 27, 2023

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from a3c0a8e to c6059eb Compare March 6, 2023 00:51
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 11 times, most recently from 4dde8cc to d1b7215 Compare March 14, 2023 19:09
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from d1b7215 to 4c20014 Compare March 15, 2023 12:07
@sxzz sxzz merged commit 444dd99 into main Mar 16, 2023
@sxzz sxzz deleted the renovate/all-minor-patch branch March 16, 2023 18:07
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.

None yet
1 participant
@sxzz