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.7 #3
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/pnpm-7.x
base: main
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
August 24, 2022 15:10
a8cd103
to
7823578
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
September 4, 2022 11:14
7823578
to
17e0c60
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
September 5, 2022 18:01
17e0c60
to
0430a34
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
September 18, 2022 19:44
0430a34
to
3828f76
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
September 20, 2022 03:33
3828f76
to
de72fbc
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
September 22, 2022 19:45
de72fbc
to
660a9f8
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
September 23, 2022 01:18
660a9f8
to
e898fd4
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
October 3, 2022 03:48
e898fd4
to
9080366
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
October 4, 2022 11:14
9080366
to
607b476
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
October 5, 2022 23:14
607b476
to
b6d222b
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
October 9, 2022 15:58
b6d222b
to
ae4eee6
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
October 10, 2022 16:33
ae4eee6
to
0a570d9
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
October 16, 2022 20:20
0a570d9
to
d937eb3
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
October 20, 2022 11:23
d937eb3
to
ab4c31f
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
October 22, 2022 14:21
ab4c31f
to
8c863d3
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
March 23, 2023 11:13
6378c17
to
69e1aed
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
March 24, 2023 02:45
69e1aed
to
0ce8a44
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
March 24, 2023 14:50
0ce8a44
to
1545a77
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
March 27, 2023 14:18
1545a77
to
1ccb0df
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
April 4, 2023 05:22
1ccb0df
to
311ec99
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
May 30, 2023 01:54
311ec99
to
7c08d91
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
June 1, 2023 17:40
7c08d91
to
b2e67bb
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
June 12, 2023 02:36
b2e67bb
to
db70c1d
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
June 24, 2023 02:56
db70c1d
to
1489130
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
July 1, 2023 01:20
1489130
to
ab35ca9
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
July 18, 2023 02:55
ab35ca9
to
b978bfb
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
July 19, 2023 03:00
b978bfb
to
b98f80f
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
August 6, 2023 01:59
b98f80f
to
158f1b3
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
February 7, 2024 05:55
158f1b3
to
23e888d
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
February 16, 2024 02:46
23e888d
to
98db92f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.9.3
->7.33.7
Release Notes
pnpm/pnpm (pnpm)
v7.33.7
Compare Source
Patch Changes
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