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

Update pnpm to v10.4.0 #176

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update pnpm to v10.4.0 #176

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 3, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
pnpm (source) 10.3.0+sha512.ee592eda8815a8a293c206bb0917c4bb0ff274c50def7cbc17be05ec641fc2d1b02490ce660061356bd0d126a4d7eb2ec8830e6959fb8a447571c631d5a2442d -> 10.4.0 age adoption passing confidence

Release Notes

pnpm/pnpm (pnpm)

v10.4.0

Compare Source

Minor Changes
  • pnpm approve-builds --global works now for allowing dependencies of globally installed packages to run postinstall scripts.

  • The pnpm add command now supports a new flag, --allow-build, which allows building the specified dependencies. For instance, if you want to install a package called bundle that has esbuild as a dependency and want to allow esbuild to run postinstall scripts, you can run:

    pnpm --allow-build=esbuild add bundle
    

    This will run esbuild's postinstall script and also add it to the pnpm.onlyBuiltDependencies field of package.json. So, esbuild will always be allowed to run its scripts in the future.

    Related PR: #​9086.

  • The pnpm init command adds a packageManager field with the current version of pnpm CLI #​9069. To disable this behaviour, set the init-package-manager setting to false.

Patch Changes
  • pnpm approve-builds should work after two consecutive pnpm install runs #​9083.
  • Fix instruction for updating pnpm with corepack #​9101.
  • The pnpm version specified by packageManager cannot start with v.

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 was generated by Mend Renovate. View the repository job log.

Copy link

codecov bot commented Feb 3, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (dee7200) to head (d1d0ee2).

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #176   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            4         4           
  Lines          507       507           
  Branches       163       163           
=========================================
  Hits           507       507           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot force-pushed the renovate/pnpm-10.x branch 2 times, most recently from 1c13566 to a7ae19c Compare February 11, 2025 12:57
@renovate renovate bot changed the title Update pnpm to v10 Update pnpm to v10 - autoclosed Feb 13, 2025
@renovate renovate bot closed this Feb 13, 2025
@renovate renovate bot deleted the renovate/pnpm-10.x branch February 13, 2025 18:30
@renovate renovate bot changed the title Update pnpm to v10 - autoclosed Update pnpm to v10 Feb 14, 2025
@renovate renovate bot reopened this Feb 14, 2025
@renovate renovate bot force-pushed the renovate/pnpm-10.x branch from 42f96ce to a7ae19c Compare February 14, 2025 01:41
@renovate renovate bot changed the title Update pnpm to v10 Update pnpm to v10.4.0 Feb 14, 2025
@renovate renovate bot force-pushed the renovate/pnpm-10.x branch from a7ae19c to d1d0ee2 Compare February 14, 2025 06:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants