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.33.6 - autoclosed #21
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
renovate
bot
changed the title
chore(deps): update pnpm to v7.1.3
chore(deps): update pnpm to v7.1.5
May 24, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
May 24, 2022 00:57
bcb3e2c
to
5199ec3
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.1.5
chore(deps): update pnpm to v7.1.6
May 27, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
2 times, most recently
from
May 29, 2022 09:38
77249a4
to
e944317
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.1.6
chore(deps): update pnpm to v7.1.7
May 29, 2022
renovate
bot
changed the title
chore(deps): update pnpm to v7.1.7
chore(deps): update pnpm to v7.1.8
Jun 5, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
June 5, 2022 00:25
e944317
to
a702976
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.1.8
chore(deps): update pnpm to v7.1.9
Jun 6, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
June 6, 2022 02:48
a702976
to
176b930
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.1.9
chore(deps): update pnpm to v7.2.0
Jun 10, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
2 times, most recently
from
June 11, 2022 04:33
f72c56d
to
aca078d
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.2.0
chore(deps): update pnpm to v7.2.1
Jun 11, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
June 19, 2022 00:07
aca078d
to
e3bf985
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.2.1
chore(deps): update pnpm to v7.3.0
Jun 19, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
June 28, 2022 16:43
e3bf985
to
8cb7214
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.3.0
chore(deps): update pnpm to v7.4.0
Jun 28, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
June 30, 2022 10:50
8cb7214
to
0a0f308
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.4.0
chore(deps): update pnpm to v7.4.1
Jun 30, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
July 2, 2022 14:43
0a0f308
to
cf15f50
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.4.1
chore(deps): update pnpm to v7.5.0
Jul 2, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
July 12, 2022 01:51
cf15f50
to
35edaf6
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.5.0
chore(deps): update pnpm to v7.5.1
Jul 12, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
July 16, 2022 23:36
35edaf6
to
073ba36
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.5.1
chore(deps): update pnpm to v7.5.2
Jul 16, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
July 22, 2022 15:09
073ba36
to
1a8fb0d
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.5.2
chore(deps): update pnpm to v7.6.0
Jul 22, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
September 25, 2022 15:32
1a8fb0d
to
a2fe78f
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.6.0
chore(deps): update pnpm to v7.12.2
Sep 25, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
March 23, 2023 22:29
ba4c666
to
00024fe
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.30.1
chore(deps): update pnpm to v7.30.0
Mar 23, 2023
renovate
bot
changed the title
chore(deps): update pnpm to v7.30.0
chore(deps): update pnpm to v7.30.3
Mar 24, 2023
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
2 times, most recently
from
March 27, 2023 23:51
feaeba1
to
17a0bc4
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.30.3
chore(deps): update pnpm to v7.30.5
Mar 27, 2023
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
April 17, 2023 12:44
17a0bc4
to
0f72ef2
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.30.5
chore(deps): update pnpm to v7.32.0
Apr 17, 2023
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
April 18, 2023 01:11
0f72ef2
to
1127d50
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.32.0
chore(deps): update pnpm to v7.32.1
Apr 18, 2023
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
May 28, 2023 10:19
1127d50
to
64652c0
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.32.1
chore(deps): update pnpm to v7.32.5
May 28, 2023
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
May 31, 2023 11:19
64652c0
to
92a33ca
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.32.5
chore(deps): update pnpm to v7.33.0
May 31, 2023
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
June 12, 2023 03:14
92a33ca
to
fdae103
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.33.0
chore(deps): update pnpm to v7.33.1
Jun 12, 2023
renovate
bot
changed the title
chore(deps): update pnpm to v7.33.1
chore(deps): update pnpm to v7.33.2
Jun 23, 2023
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
June 23, 2023 13:50
fdae103
to
1c3887c
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
July 1, 2023 03:53
1c3887c
to
944faae
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.33.2
chore(deps): update pnpm to v7.33.3
Jul 1, 2023
renovate
bot
changed the title
chore(deps): update pnpm to v7.33.3
chore(deps): update pnpm to v7.33.4
Jul 17, 2023
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
2 times, most recently
from
July 18, 2023 13:59
15cedcc
to
de68572
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.33.4
chore(deps): update pnpm to v7.33.5
Jul 18, 2023
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
August 6, 2023 04:50
de68572
to
fcce805
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.33.5
chore(deps): update pnpm to v7.33.6
Aug 6, 2023
renovate
bot
changed the title
chore(deps): update pnpm to v7.33.6
chore(deps): update pnpm to v7.33.6 - autoclosed
Jan 23, 2024
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.0.0
->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