Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 25, 2025

Bumps pnpm from 8.9.2 to 10.5.0.

Release notes

Sourced from pnpm's releases.

pnpm 10.5

Minor Changes

  • The pnpm.* settings from package.json can now be specified in the pnpm-workspace.yaml file instead #9121.

    package.json:

    {
      "pnpm": {
        "onlyBuiltDependencies": ["esbuild", "fuse-native"]
      }
    }

    pnpm-workspace.yaml:

    onlyBuiltDependencies:
    - esbuild
    - fuse-native
  • Added support for automatically syncing files of injected workspace packages after pnpm run #9081. Use the sync-injected-deps-after-scripts setting to specify which scripts build the workspace package. This tells pnpm when syncing is needed. The setting should be defined in a .npmrc file at the root of the workspace. Example:

    sync-injected-deps-after-scripts[]=compile
  • The packages field in pnpm-workspace.yaml became optional.

Patch Changes

  • pnpm link with no parameters should work as if --global is specified #9151.
  • Allow scope registry CLI option without --config. prefix such as --@scope:registry=https://scope.example.com/npm #9089.
  • pnpm link <path> should calculate relative path from the root of the workspace directory #9132.
  • Fix a bug causing catalog snapshots to be removed from the pnpm-lock.yaml file when using --fix-lockfile and --filter. #8639
  • Fix a bug causing catalog protocol dependencies to not re-resolve on a filtered install #8638.

Platinum Sponsors

... (truncated)

Changelog

Sourced from pnpm's changelog.

10.5.0

Minor Changes

  • Allow to set the "pnpm" settings from package.json via the pnpm-workspace.yaml file #9121.

  • Added support for automatically syncing files of injected workspace packages after pnpm run #9081. Use the sync-injected-deps-after-scripts setting to specify which scripts build the workspace package. This tells pnpm when syncing is needed. The setting should be defined in a .npmrc file at the root of the workspace. Example:

    sync-injected-deps-after-scripts[]=compile
  • The packages field in pnpm-workspace.yaml became optional.

Patch Changes

  • pnpm link with no parameters should work as if --global is specified #9151.
  • Allow scope registry CLI option without --config. prefix such as --@scope:registry=https://scope.example.com/npm #9089.
  • pnpm link <path> should calculate relative path from the root of the workspace directory #9132.
  • Fix a bug causing catalog snapshots to be removed from the pnpm-lock.yaml file when using --fix-lockfile and --filter. #8639
  • Fix a bug causing catalog protocol dependencies to not re-resolve on a filtered install #8638.

10.4.1

Patch Changes

  • Throws an error when the value provided by the --allow-build option overlaps with the pnpm.ignoredBuildDependencies list #9105.
  • Print pnpm's version after the execution time at the end of the console output.
  • Print warning about ignored builds of dependencies on repeat install #9106.
  • Setting init-package-manager should work.

10.4.0

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.

... (truncated)

Commits
  • 0e9fff7 chore(release): 10.5.0
  • b352d2a fix: pnpm link: imply global mode when no arguments are specified (#9151)
  • e32b1a2 feat: update injected packages after run (#9100)
  • 8fcc221 feat: reading settings from pnpm-workspace.yaml (#9121)
  • ee72c62 chore(release): 10.4.1
  • 546ab37 fix: --allow-build=\<pkg> overlaps with ignoredBuiltDependencies (#9105)
  • 0205498 fix: print warning about ignored builds on repeat install (#9116)
  • 2a6b51f chore(release): 10.4.0
  • 91d46ee feat: add --allow-build=\<pkg> to add command (#9086)
  • 31d15ff chore: pass all env variables to pnpm CLI, when running pd
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [pnpm](https://github.com/pnpm/pnpm/tree/HEAD/pnpm) from 8.9.2 to 10.5.0.
- [Release notes](https://github.com/pnpm/pnpm/releases)
- [Changelog](https://github.com/pnpm/pnpm/blob/main/pnpm/CHANGELOG.md)
- [Commits](https://github.com/pnpm/pnpm/commits/v10.5.0/pnpm)

---
updated-dependencies:
- dependency-name: pnpm
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Feb 25, 2025
@vercel
Copy link

vercel bot commented Feb 25, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
devs-in-tech ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 25, 2025 8:24pm

@netlify
Copy link

netlify bot commented Feb 25, 2025

Deploy Preview for devsintech failed.

Name Link
🔨 Latest commit 2488bde
🔍 Latest deploy log https://app.netlify.com/sites/devsintech/deploys/67be26d570fba500087c0e04

@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Feb 26, 2025

Superseded by #776.

@dependabot dependabot bot closed this Feb 26, 2025
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/pnpm-10.5.0 branch February 26, 2025 20:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant