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

chore(deps): update pnpm to v7.5.0 #5

Merged
merged 1 commit into from
Jul 4, 2022
Merged

chore(deps): update pnpm to v7.5.0 #5

merged 1 commit into from
Jul 4, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 30, 2022

Mend Renovate

This PR contains the following updates:

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

Release Notes

pnpm/pnpm

v7.5.0

Compare Source

Minor Changes
  • A new value rolling for option save-workspace-protocol. When selected, pnpm will save workspace versions using a rolling alias (e.g. "foo": "workspace:^") instead of pinning the current version number (e.g. "foo": "workspace:^1.0.0"). Usage example, in the root of your workspace, create a .npmrc with the following content:

    save-workspace-protocol=rolling
    
Patch Changes
  • pnpm remove <pkg> should not fail in a workspace that has patches #​4954
  • The hash of the patch file should be the same on both Windows and POSIX #​4961.
  • pnpm env use should throw an error on a system that use the MUSL libc.
Our Gold Sponsors
##### Our Silver Sponsors
##### What's Changed * fix(env): throw an error on a system that uses MUSL libc by @​zkochan in https://github.com/pnpm/pnpm/pull/4958 * feat: use workspace spec alias by default in pnpm add by @​javier-garcia-meteologica in https://github.com/pnpm/pnpm/pull/4947 * fix(patch): the hash of the patch file should be the same on both Windows and POSIX by @​zkochan in https://github.com/pnpm/pnpm/pull/4969

Full Changelog: pnpm/pnpm@v7.4.1...v7.5.0

v7.4.1

Compare Source

Patch Changes

  • pnpm install in a workspace with patches should not fail when doing partial installation #​4954.
  • Never skip lockfile resolution when the lockfile is not up-to-date and --lockfile-only is used. Even if frozen-lockfile is true #​4951.
  • Never add an empty patchedDependencies field to pnpm-lock.yaml.

Our Gold Sponsors

#### Our Silver Sponsors
#### What's Changed * fix(lockfile): never add an empty `patchedDependencies` field to `pnpm-lock.yaml` by @​zkochan in https://github.com/pnpm/pnpm/pull/4948 * Add "refs/"+refname to resolution options by @​rotu in https://github.com/pnpm/pnpm/pull/4953 * fix: --lockfile-only in CI and with frozen-lockfile=true by @​zkochan in https://github.com/pnpm/pnpm/pull/4955 * fix: partial install in workspace with patches should not fail by @​zkochan in https://github.com/pnpm/pnpm/pull/4956 #### New Contributors * @​rotu made their first contribution in https://github.com/pnpm/pnpm/pull/4953

Full Changelog: pnpm/pnpm@v7.4.0...v7.4.1


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, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot changed the title chore(deps): update pnpm to v7.4.1 chore(deps): update pnpm to v7.5.0 Jul 2, 2022
@yjl9903 yjl9903 merged commit baa766e into main Jul 4, 2022
@renovate renovate bot deleted the renovate/pnpm-7.x branch July 4, 2022 17:54
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.

None yet

1 participant