Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Apr 4, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
pnpm (source) 7.30.5 -> 8.1.1 age adoption passing confidence

Release Notes

pnpm/pnpm

v8.1.1

Compare Source

Patch Changes

  • Repeat installation should work on a project that has a dependency with parentheses in the scope name #​6348.
  • Error summary should be reported as expected.
  • Update @yarnpkg/shell to fix issues in the shell emulator #​6320.
  • Installation should not fail when there is a local dependency in a directory that starts with the @ character #​6332.
  • Registries are now passed to the preResolution hook.

Our Gold Sponsors

Our Silver Sponsors

v8.1.0

Compare Source

Minor Changes

  • A new setting has been added called dedupe-direct-deps, which is disabled by default. When set to true, dependencies that are already symlinked to the root node_modules directory of the workspace will not be symlinked to subproject node_modules directories. This feature was enabled by default in v8.0.0 but caused issues, so it's best to disable it by default #​6299.
  • Add ignore-workspace-cycles to silence workspace cycle warning #​6308.

Patch Changes

  • Print the right lowest supported Node.js version in the error message, when pnpm is executed with an old Node.js version #​6297.
  • Improve the outdated lockfile error message #​6304.

Our Gold Sponsors

Our Silver Sponsors

v8.0.0

Compare Source

We are excited to announce the latest release of pnpm! To install it, check the installation page.

image

Major Changes
Node.js 14 Support Discontinued

If you still require Node.js 14, don't worry. We ship pnpm bundled with Node.js. This means that regardless of which Node.js version you've installed, pnpm will operate using the necessary Node.js runtime. For this to work you need to install pnpm either using the standalone script or install the @pnpm/exe package.

Configuration Updates

Most of the configuration changes are related to peer dependencies. Most of these settings were implemented long ago, and we recommended them to users encountering peer dependency issues. The recently added dedupe-peer-dependents resolved many such problems. With these new defaults, pnpm will face significantly fewer issues during migration from other package managers.

Lockfile Modifications
  • Lockfile v6 is adopted. This new format improves the readability of the lockfile by removing hashes from package IDs. It also has some rearrangement of fields in the importers section. The new pnpm-lock.yaml file is more resistant to git merge conflicts!
  • The registry field is removed from the resolution object in pnpm-lock.yaml.
  • A lockfile is generated even for projects with no dependencies.
Other Changes
  • When there's a files field in the package.json, only the files that are listed in it will be deployed. The same logic is applied when injecting packages. This behaviour can be changed by setting the deploy-all-files setting to true (Related issue #​5911).
  • Direct dependencies are deduped. If a dependency is present in both a project and the workspace root, it will only be linked to the workspace root.
Migration Instructions

Before updating pnpm to v8 in your CI, regenerate your pnpm-lock.yaml. To upgrade your lockfile, run pnpm install and commit the changes. Existing dependencies will not be updated; however, due to configuration changes in pnpm v8, some missing peer dependencies may be added to the lockfile and some packages may get deduplicated.

You can commit the new lockfile even before upgrading Node.js in the CI, as pnpm v7 already supports the new lockfile format.

pnpm v7 Support

pnpm v7 will likely not receive any new features, but it will continue to get bug fixes for a few months and vulnerability fixes for at least a year.

Our Gold Sponsors
Our Silver Sponsors

v7.31.0

Compare Source

Minor Changes

  • Add ignore-workspace-cycles to silence workspace cycle warning #​6308.
Patch Changes
  • Registries are now passed to the preResolution hook.
  • Repeat installation should work on a project that has a dependency with () chars in the scope name #​6348.
  • Should report error summary as expected.
  • Update @yarnpkg/shell to fix issues in the shell emulator #​6320.
  • Installation should not fail when there is a local dependency that starts in a directory that starts with the @ char #​6332.

Our Gold Sponsors

Our Silver Sponsors


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • 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 UPDATE-MAJOR label Apr 4, 2023
@changeset-bot
Copy link

changeset-bot bot commented Apr 4, 2023

🦋 Changeset detected

Latest commit: 01db093

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@scaleway/eslint-config-react Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@renovate renovate bot requested review from a team, DorianMaliszewski and Lawndlwd and removed request for a team April 4, 2023 09:08
@renovate
Copy link
Contributor Author

renovate bot commented Apr 4, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.

@philibea philibea closed this Apr 6, 2023
@philibea philibea reopened this Apr 6, 2023
@philibea philibea force-pushed the renovate/pnpm-8.x branch from e94b249 to 01db093 Compare April 6, 2023 07:33
@codecov
Copy link

codecov bot commented Apr 6, 2023

Codecov Report

Merging #1272 (01db093) into main (6f07dc5) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1272   +/-   ##
=======================================
  Coverage   98.94%   98.94%           
=======================================
  Files          24       24           
  Lines         666      666           
  Branches       94       94           
=======================================
  Hits          659      659           
  Partials        7        7           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@philibea philibea merged commit b8d9d79 into main Apr 6, 2023
@philibea philibea deleted the renovate/pnpm-8.x branch April 6, 2023 07:46
@github-actions github-actions bot mentioned this pull request Apr 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants