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.7 #7
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.
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
June 30, 2022 11:51
62d4132
to
d25acdd
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 15:03
d25acdd
to
277e7b1
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
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
2 times, most recently
from
July 16, 2022 22:14
67e389d
to
f5f210c
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
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
July 22, 2022 13:12
f5f210c
to
9adb9c7
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
July 29, 2022 14:18
9adb9c7
to
0f893f7
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.6.0
chore(deps): update pnpm to v7.7.0
Jul 29, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
July 30, 2022 11:50
0f893f7
to
4a4918f
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.7.0
chore(deps): update pnpm to v7.7.1
Jul 30, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
July 31, 2022 10:44
4a4918f
to
fcee351
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.7.1
chore(deps): update pnpm to v7.8.0
Jul 31, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
August 6, 2022 20:21
fcee351
to
3769482
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.8.0
chore(deps): update pnpm to v7.9.0
Aug 6, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
2 times, most recently
from
August 17, 2022 09:52
b1d5609
to
7906985
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.9.0
chore(deps): update pnpm to v7.9.2
Aug 17, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
August 17, 2022 12:05
7906985
to
5b08ce6
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.9.2
chore(deps): update pnpm to v7.9.3
Aug 17, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
August 23, 2022 12:13
5b08ce6
to
81106bb
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.9.3
chore(deps): update pnpm to v7.9.4
Aug 23, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
August 24, 2022 12:47
81106bb
to
5aa1b87
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.9.4
chore(deps): update pnpm to v7.9.5
Aug 24, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
September 4, 2022 10:29
5aa1b87
to
8c4abf6
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.9.5
chore(deps): update pnpm to v7.10.0
Sep 4, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
September 5, 2022 12:17
8c4abf6
to
379fc6b
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.29.3
chore(deps): update pnpm to v7.30.0
Mar 20, 2023
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
2 times, most recently
from
March 24, 2023 11:52
68cd6ee
to
5c41fa6
Compare
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 21:32
4707f4e
to
ac5c521
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
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
2 times, most recently
from
April 18, 2023 01:25
b09172e
to
9c94c5d
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
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 28, 2023 10:05
9c94c5d
to
c802eab
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
May 31, 2023 12:04
c802eab
to
52c5cea
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
June 12, 2023 03:45
52c5cea
to
fa32040
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
force-pushed
the
renovate/pnpm-7.x
branch
from
June 23, 2023 16:56
fa32040
to
bf0c3ab
Compare
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
July 1, 2023 05:36
bf0c3ab
to
8d7b86e
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 12:42
fb20aea
to
52bd7d6
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 03:53
52bd7d6
to
4aa781f
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
force-pushed
the
renovate/pnpm-7.x
branch
from
February 15, 2024 14:29
4aa781f
to
db093c8
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.33.6
chore(deps): update pnpm to v7.33.7
Feb 15, 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.3.0
->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