Skip to content

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
merged 12 commits into from
Mar 4, 2025

Conversation

zkochan
Copy link
Member

@zkochan zkochan commented Mar 3, 2025

@zkochan zkochan requested a review from a team March 4, 2025 13:41
@zkochan zkochan marked this pull request as ready for review March 4, 2025 13:41
Copy link
Contributor

@shellscape shellscape left a 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.

@zkochan
Copy link
Member Author

zkochan commented Mar 4, 2025

@shellscape we have a discussion about it. I have added the link to the description.

@zkochan zkochan merged commit d965748 into main Mar 4, 2025
16 checks passed
@zkochan zkochan deleted the pnpm-workspace-config branch March 4, 2025 14:09
@zkochan zkochan mentioned this pull request Mar 13, 2025
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` [#&#8203;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 [#&#8203;9211](pnpm/pnpm#9211).

    `pnpm-workspace.yaml` example:

    ```yaml
    verifyDepsBeforeRun: install
    optimisticRepeatInstall: true
    publicHoistPattern:
      - "*types*"
      - "!@&#8203;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 [#&#8203;9169](pnpm/pnpm#9169).
-   `pnpm deploy` should not remove fields from the deployed package's `package.json` file [#&#8203;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 [#&#8203;9193](pnpm/pnpm#9193).
-   `pnpm update -i` should list only packages that have newer versions [#&#8203;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. [#&#8203;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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy