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

Update all non-major dependencies #1189

Merged
merged 1 commit into from
Mar 6, 2023
Merged

Update all non-major dependencies #1189

merged 1 commit into from
Mar 6, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 1, 2023 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@auto-it/slack 10.42.2 -> 10.43.0 age adoption passing confidence
auto 10.42.2 -> 10.43.0 age adoption passing confidence
eslint (source) 8.34.0 -> 8.35.0 age adoption passing confidence
eslint-plugin-jsdoc 40.0.0 -> 40.0.1 age adoption passing confidence
pnpm (source) 7.27.1 -> 7.29.0 age adoption passing confidence

Release Notes

intuit/auto

v10.43.0

Compare Source

🎉 This release contains work from a new contributor! 🎉

Thank you, Adil Malik (@​amalik2), for all your work!

🚀 Enhancement
Authors: 1
eslint/eslint

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

gajus/eslint-plugin-jsdoc

v40.0.1

Compare Source

pnpm/pnpm

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

Configuration

📅 Schedule: Branch creation - "after 9am on Wednesday" in timezone Europe/London, 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.

@renovate renovate bot added change: dependencies Updates to dependencies only release: skip Skips the release step when this pr is merged labels Mar 1, 2023
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 3a84375 to 8a78419 Compare March 2, 2023 22:51
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 8a78419 to 1428d15 Compare March 6, 2023 02:18
@AndrewLeedham AndrewLeedham merged commit 2dd6f03 into next Mar 6, 2023
@AndrewLeedham AndrewLeedham deleted the renovate/all-minor-patch branch March 6, 2023 12:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@AndrewLeedham AndrewLeedham

Labels
change: dependencies Updates to dependencies only release: skip Skips the release step when this pr is merged
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@AndrewLeedham