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.

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

chore(deps): lock file maintenance non-major updates and lockfile maintenance(auto merge) - autoclosed #57

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 13, 2023

Mend Renovate

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
lockFileMaintenance All locks refreshed age adoption passing confidence
@types/node (source) dependencies minor 20.8.10 -> 20.10.4 age adoption passing confidence
node minor 20.9.0 -> 20.10.0 age adoption passing confidence
pnpm (source) packageManager minor 8.10.2 -> 8.12.0 age adoption passing confidence

🔧 This Pull Request updates lock files to use the latest dependency versions.


Release Notes

nodejs/node (node)

v20.10.0

Compare Source

pnpm/pnpm (pnpm)

v8.12.0

Compare Source

Minor Changes

  • Add support for basic authorization header #​7371.

Patch Changes

  • Fix a bug where pnpm incorrectly passes a flag to a run handler as a fallback command #​7244.
  • When dedupe-direct-deps is set to true, commands of dependencies should be deduplicated #​7359.

Our Gold Sponsors

Our Silver Sponsors

v8.11.0

Compare Source

Minor Changes

  • (IMPORTANT) When the package tarballs aren't hosted on the same domain on which the registry (the server with the package metadata) is, the dependency keys in the lockfile should only contain /<pkg_name>@&#8203;<pkg_version, not <domain>/<pkg_name>@&#8203;<pkg_version>.

    This change is a fix to avoid the same package from being added to node_modules/.pnpm multiple times. The change to the lockfile is backward compatible, so previous versions of pnpm will work with the fixed lockfile.

    We recommend that all team members update pnpm in order to avoid repeated changes in the lockfile.

    Related PR: #​7318.

Patch Changes

  • pnpm add a-module-already-in-dev-deps will show a message to notice the user that the package was not moved to "dependencies" #​926.
  • The modules directory should not be removed if the registry configuration has changed.
  • Fix missing auth tokens in registries with paths specified (e.g. //npm.pkg.github.com/pnpm). #​5970 #​2933

Our Gold Sponsors

Our Silver Sponsors

v8.10.5

Compare Source

Patch Changes

  • Don't fail on an empty pnpm-workspace.yaml file #​7307.

Our Gold Sponsors

Our Silver Sponsors

v8.10.4

Compare Source

Patch Changes

  • Fixed out-of-memory exception that was happening on dependencies with many peer dependencies, when node-linker was set to hoisted #​6227.

Our Gold Sponsors

Our Silver Sponsors

v8.10.3

Compare Source

Patch Changes

  • (Important) Increased the default amount of allowed concurrent network request on systems that have more than 16 CPUs #​7285.

  • pnpm patch should reuse existing patch when shared-workspace-file=false #​7252.

  • Don't retry fetching missing packages, since the retries will never work #​7276.

  • When using pnpm store prune --force alien directories are removed from the store #​7272.

  • Downgraded npm-packlist because the newer version significantly slows down the installation of local directory dependencies, making it unbearably slow.

    npm-packlist was upgraded in this PR to fix #​6997. We added our own file deduplication to fix the issue of duplicate file entries.

  • Fixed a performance regression on running installation on a project with an up to date lockfile #​7297.

  • Throw an error on invalid pnpm-workspace.yaml file #​7273.

Our Gold Sponsors

Our Silver Sponsors


Configuration

📅 Schedule: Branch creation - "before 4am 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 Mend Renovate. View repository job log here.

@renovate renovate bot added the dependencies Change in project dependencies. label Nov 13, 2023
@renovate renovate bot assigned rainx Nov 13, 2023
@renovate renovate bot requested a review from rainx November 13, 2023 05:03
@renovate renovate bot force-pushed the renovate/non-major-updates-and-lockfile-maintenance(auto-merge) branch 6 times, most recently from 69644cd to ddc6573 Compare November 18, 2023 23:05
@renovate renovate bot force-pushed the renovate/non-major-updates-and-lockfile-maintenance(auto-merge) branch 6 times, most recently from 0a717f7 to 2bb5961 Compare November 24, 2023 17:09
@renovate renovate bot force-pushed the renovate/non-major-updates-and-lockfile-maintenance(auto-merge) branch 3 times, most recently from 8de5570 to e686bdf Compare December 3, 2023 20:39
@renovate renovate bot force-pushed the renovate/non-major-updates-and-lockfile-maintenance(auto-merge) branch from e686bdf to fa8fd5e Compare December 7, 2023 09:22
@renovate renovate bot force-pushed the renovate/non-major-updates-and-lockfile-maintenance(auto-merge) branch from fa8fd5e to 10226db Compare December 8, 2023 22:37
@renovate renovate bot changed the title chore(deps): lock file maintenance non-major updates and lockfile maintenance(auto merge) chore(deps): lock file maintenance non-major updates and lockfile maintenance(auto merge) - autoclosed Dec 12, 2023
@renovate renovate bot closed this Dec 12, 2023
@renovate renovate bot deleted the renovate/non-major-updates-and-lockfile-maintenance(auto-merge) branch December 12, 2023 14:24
Copy link

Pull Request closed and locked due to lack of activity.
If you'd like to build on this closed PR, you can clone it using this method: https://stackoverflow.com/a/14969986
Then open a new PR, referencing this closed PR in your message.

@github-actions github-actions bot locked and limited conversation to collaborators Dec 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
dependencies Change in project dependencies.
Development

Successfully merging this pull request may close these issues.

1 participant