-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
feat: setting config settings via pnpm-workspace.yaml #9211
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
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reverts commit 2dfa68c.
shellscape
approved these changes
Mar 4, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. But I'd like to have some historical context noted. I'm just curious about the motivations; convenience, plan to migrate away from npmrc settings support, etc.
@shellscape we have a discussion about it. I have added the link to the description. |
4 tasks
jelmore1674
pushed a commit
to jelmore1674/build-changelog
that referenced
this pull request
Mar 19, 2025
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [pnpm](https://pnpm.io) ([source](https://github.com/pnpm/pnpm/tree/HEAD/pnpm)) | packageManager | minor | [`10.5.2+sha512.da9dc28cd3ff40d0592188235ab25d3202add8a207afbedc682220e4a0029ffbff4562102b9e6e46b4e3f9e8bd53e6d05de48544b0c57d4b0179e22c76d1199b` -> `10.6.1`](https://renovatebot.com/diffs/npm/pnpm/10.5.2/10.6.1) | --- ### Release Notes <details> <summary>pnpm/pnpm (pnpm)</summary> ### [`v10.6.1`](https://github.com/pnpm/pnpm/blob/HEAD/pnpm/CHANGELOG.md#1061) [Compare Source](pnpm/pnpm@v10.6.0...v10.6.1) ##### Patch Changes - The pnpm CLI process should not stay hanging, when `--silent` reporting is used. - When `--loglevel` is set to `error`, don't show installation summary, execution time, and big tarball download progress. - Don't ignore pnpm.patchedDependencies from `package.json` [#​9226](pnpm/pnpm#9226). - When executing the `approve-builds` command, if package.json contains `onlyBuiltDependencies` or `ignoredBuiltDependencies`, the selected dependency package will continue to be written into `package.json`. - When a package version cannot be found in the package metadata, print the registry from which the package was fetched. ### [`v10.6.0`](https://github.com/pnpm/pnpm/blob/HEAD/pnpm/CHANGELOG.md#1060) [Compare Source](pnpm/pnpm@v10.5.2...v10.6.0) ##### Minor Changes - `pnpm-workspace.yaml` can now hold all the settings that `.npmrc` accepts. The settings should use camelCase [#​9211](pnpm/pnpm#9211). `pnpm-workspace.yaml` example: ```yaml verifyDepsBeforeRun: install optimisticRepeatInstall: true publicHoistPattern: - "*types*" - "!@​types/react" ``` - Projects using a `file:` dependency on a local tarball file (i.e. `.tgz`, `.tar.gz`, `.tar`) will see a performance improvement during installation. Previously, using a `file:` dependency on a tarball caused the lockfile resolution step to always run. The lockfile will now be considered up-to-date if the tarball is unchanged. ##### Patch Changes - `pnpm self-update` should not leave a directory with a broken pnpm installation if the installation fails. - `fast-glob` replace with `tinyglobby` to reduce the size of the pnpm CLI dependencies [#​9169](pnpm/pnpm#9169). - `pnpm deploy` should not remove fields from the deployed package's `package.json` file [#​9215](pnpm/pnpm#9215). - `pnpm self-update` should not read the pnpm settings from the `package.json` file in the current working directory. - Fix `pnpm deploy` creating a `package.json` without the `imports` and `license` field [#​9193](pnpm/pnpm#9193). - `pnpm update -i` should list only packages that have newer versions [#​9206](pnpm/pnpm#9206). - Fix a bug causing entries in the `catalogs` section of the `pnpm-lock.yaml` file to be removed when `dedupe-peer-dependents=false` on a filtered install. [#​9112](pnpm/pnpm#9112) </details> --- ### 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xODkuMCIsInVwZGF0ZWRJblZlciI6IjM5LjE5MC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119--> Reviewed-on: https://gitea.justinelmore.dev/jelmore1674/build-changelog/pulls/96 Co-authored-by: Renovate Bot <renovate-bot@forgejo.justinelmore.dev> Co-committed-by: Renovate Bot <renovate-bot@forgejo.justinelmore.dev>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related discussion: https://github.com/orgs/pnpm/discussions/9037