-
Notifications
You must be signed in to change notification settings - Fork 1
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 v7.33.6 #143
Closed
Closed
Conversation
This file contains 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
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 2 Ignored Deployments
|
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
2 times, most recently
from
July 30, 2022 11:13
9bdb56f
to
9710fcc
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
July 31, 2022 11:03
9710fcc
to
01dd3c6
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
August 6, 2022 18:49
01dd3c6
to
2f0ded7
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
August 17, 2022 11:03
2f0ded7
to
feaea12
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
August 23, 2022 11:17
feaea12
to
04ed068
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
August 24, 2022 13:32
04ed068
to
b34a44a
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
September 4, 2022 11:33
b34a44a
to
31a209e
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
September 5, 2022 18:52
31a209e
to
62eff91
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
September 18, 2022 22:01
62eff91
to
5ca8996
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
September 20, 2022 03:06
5ca8996
to
e7897c3
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
September 25, 2022 22:26
e7897c3
to
e967c16
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
November 20, 2022 21:19
e967c16
to
ede4fd6
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
March 11, 2023 16:10
ede4fd6
to
f272bbb
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
March 16, 2023 11:42
f272bbb
to
9351776
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
March 24, 2023 17:07
9351776
to
4a2e4ee
Compare
⚠ Artifact update problemRenovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below: File name: pnpm-lock.yaml
|
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
March 27, 2023 23:54
4a2e4ee
to
a59d098
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
April 17, 2023 09:38
a59d098
to
43a468f
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
June 1, 2023 18:12
43a468f
to
5f09583
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
June 12, 2023 03:37
5f09583
to
7800193
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
June 23, 2023 15:46
7800193
to
24c15c2
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
July 1, 2023 03:18
24c15c2
to
6f6ab4e
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
2 times, most recently
from
July 18, 2023 12:10
a8cf6d4
to
be50e29
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
August 6, 2023 00:43
be50e29
to
acdebba
Compare
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.
This PR contains the following updates:
7.5.2
->7.33.6
Release Notes
pnpm/pnpm (pnpm)
v7.33.6
Compare Source
Patch Changes
Our Gold Sponsors
Our Silver Sponsors
v7.33.5
Compare Source
Patch Changes
Our Gold Sponsors
Our Silver Sponsors
v7.33.4
Compare Source
Patch Changes
publishConfig.registry
inpackage.json
for publishing #6775.git ls-remote
, causing a fallback togit+ssh
and resulting in a 'host key verification failed' issue #6805Our Gold Sponsors
Our Silver Sponsors
v7.33.3
Compare Source
Patch Changes
package.json
should not fail, when the dependency is read from cache #6721.Our Gold Sponsors
Our Silver Sponsors
v7.33.2
Compare Source
Patch Changes
node-linker
is set tohoisted
#6680..npmrc
file #6354.pnpm update --global --latest
should work #3779.Our Gold Sponsors
Our Silver Sponsors
v7.33.1
Compare Source
Patch Changes
When
dedupe-peer-dependents
is enabled, use the path (not id) to determine compatibility.When multiple dependency groups can be deduplicated, the latter ones are sorted according to number of peers to allow them to benefit from deduplication.
Resolves: #6605
Change lockfile version back to 6.0 as previous versions of pnpm fail to parse the version correctly.
Our Gold Sponsors
Our Silver Sponsors
v7.33.0
Compare Source
Minor Changes
Some settings influence the structure of the lockfile, so we cannot reuse the lockfile if those settings change. As a result, we need to store such settings in the lockfile. This way we will know with which settings the lockfile has been created.
A new field will now be present in the lockfile:
settings
. It will store the values of two settings:autoInstallPeers
andexcludeLinksFromLockfile
. If someone tries to perform afrozen-lockfile
installation and their active settings don't match the ones in the lockfile, then an error message will be thrown.The lockfile format version is bumped from v6.0 to v6.1.
Related PR: #6557
Related issue: #6312
Patch Changes
npm:foo@1.0.0
becomesnpm:foo@1.1.0
.workspace:
protocol is not found in the workspace #4477.updateConfig.ignoreDependencies
#6548Our Gold Sponsors
Our Silver Sponsors
v7.32.5
Compare Source
Patch Changes
pnpm rebuild
should not fail whennode-linker
is set tohoisted
and there are skipped optional dependencies #6553.Our Gold Sponsors
Our Silver Sponsors
v7.32.4
Compare Source
Patch Changes
pnpm link -g <pkg-name>
should not modify thepackage.json
file #4341.engines
field should match prerelease versions #6509.pnpm publish --otp
should work #6514.Our Gold Sponsors
Our Silver Sponsors
v7.32.3
Compare Source
Patch Changes
node-linker
is set tohoisted
6486.Our Gold Sponsors
Our Silver Sponsors
v7.32.2
Compare Source
Patch Changes
Our Gold Sponsors
Our Silver Sponsors
v7.32.1
Compare Source
Patch Changes
publishConfig.directory
of an injected workspace dependency does not exist #6396.Our Gold Sponsors
Our Silver Sponsors
v7.32.0
Compare Source
Minor Changes
.npmrc
. This is a convention used by Yarn too.Using
${NAME-fallback}
will returnfallback
ifNAME
isn't set.${NAME:-fallback}
will returnfallback
ifNAME
isn't set, or is an empty string #6018.Patch Changes
pnpm config get <key>
returns empty when the value is a booleanlink:
protocol inpackage.json
.Our Gold Sponsors
Our Silver Sponsors
v7.31.0
Compare Source
Minor Changes
ignore-workspace-cycles
to silence workspace cycle warning #6308.Patch Changes
@yarnpkg/shell
to fix issues in the shell emulator #6320.@
char #6332.Our Gold Sponsors
Our Silver Sponsors
v7.30.5
Compare Source
Patch Changes
pnpm audit
should work even if there are nopackage.json
file, just apnpm-lock.yaml
file.dedupe-peer-dependents
istrue
#6154.Our Gold Sponsors
Our Silver Sponsors
v7.30.4
Compare Source
v7.30.3
Compare Source
Patch Changes
Our Gold Sponsors
Our Silver Sponsors
v7.30.2
Compare Source
v7.30.1
Compare Source
Patch Changes
pnpm-lock.yaml
file if it has no changes andpnpm install --frozen-lockfile
was executed #6158.git+ssh
that use semver selectors #6239.pnpm audit
output #6203Our Gold Sponsors
Our Silver Sponsors