-
-
Notifications
You must be signed in to change notification settings - Fork 0
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 #9
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 }}
Loading
Could not load tags
Nothing to show
Loading
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
November 14, 2022 15:58
50088ee
to
bc0a82e
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
November 16, 2022 18:07
bc0a82e
to
4d88425
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
November 20, 2022 22:13
4d88425
to
14c188f
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
2 times, most recently
from
December 4, 2022 00:28
b5780d5
to
17a0609
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
December 6, 2022 13:59
17a0609
to
4312281
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
December 12, 2022 14:41
4312281
to
d36c363
Compare
renovate
bot
changed the title
Update pnpm to v7.18.2
chore(deps): update pnpm to v7.18.2
Dec 19, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
December 21, 2022 14:02
d36c363
to
770878d
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.18.2
chore(deps): update pnpm to v7.19.0
Dec 21, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
December 26, 2022 00:31
770878d
to
0cb9840
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.19.0
chore(deps): update pnpm to v7.20.0
Dec 26, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
December 28, 2022 17:53
0cb9840
to
0907ee5
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.20.0
chore(deps): update pnpm to v7.21.0
Dec 28, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
January 3, 2023 16:10
0907ee5
to
368bc60
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.21.0
chore(deps): update pnpm to v7.22.0
Jan 3, 2023
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
January 9, 2023 03:24
368bc60
to
ce2fb85
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.22.0
chore(deps): update pnpm to v7.23.0
Jan 9, 2023
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
March 12, 2023 11:08
ce2fb85
to
522f3d2
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.23.0
chore(deps): update pnpm to v7.29.1
Mar 12, 2023
⚠ 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 14, 2023 07:55
522f3d2
to
97a22c7
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.29.1
chore(deps): update pnpm to v7.29.2
Mar 14, 2023
renovate
bot
changed the title
chore(deps): update pnpm to v7.29.2
chore(deps): update pnpm to v7.29.3
Mar 16, 2023
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
March 16, 2023 15:10
97a22c7
to
1918d85
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
from
March 20, 2023 21:27
1918d85
to
1c30d18
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.30.0
chore(deps): update pnpm to v7.30.5
Mar 27, 2023
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
March 27, 2023 17:33
1c30d18
to
7d3895f
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
2 times, most recently
from
June 1, 2023 16:32
fdb5d7c
to
6e75f33
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.30.5
chore(deps): update pnpm to v7.33.0
Jun 1, 2023
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 12, 2023 18:00
6e75f33
to
657cf9f
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.33.1
chore(deps): update pnpm to v7.33.2
Jun 24, 2023
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
2 times, most recently
from
July 1, 2023 01:40
67f249d
to
b7ac22c
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 18, 2023
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
July 18, 2023 02:36
b7ac22c
to
4b26d28
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.33.4
chore(deps): update pnpm to v7.33.5
Jul 19, 2023
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
July 19, 2023 05:53
4b26d28
to
1f62ace
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
August 6, 2023 05:38
1f62ace
to
e5ca2da
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
February 16, 2024 08:28
e5ca2da
to
f816533
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.33.6
chore(deps): update pnpm to v7.33.7
Feb 16, 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.14.2
->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
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.
This PR was generated by Mend Renovate. View the repository job log.