-
-
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 #17
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.
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
June 19, 2022 01:25
3660755
to
df3d8e2
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
June 20, 2022 15:36
df3d8e2
to
95c2a51
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
June 28, 2022 14:58
95c2a51
to
b72f1bf
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
June 30, 2022 13:08
b72f1bf
to
edc7684
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
July 2, 2022 13:45
edc7684
to
1f53436
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
July 12, 2022 01:08
1f53436
to
d47000b
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
July 16, 2022 21:38
d47000b
to
b3e0d87
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
July 22, 2022 15:32
b3e0d87
to
3865ead
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
July 29, 2022 13:43
3865ead
to
25e3954
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
July 30, 2022 12:00
25e3954
to
8734999
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 11:19
7714b20
to
82217db
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:55
82217db
to
9b06a02
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 05:04
9b06a02
to
0fc1730
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 13:59
0fc1730
to
c943879
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 08:00
c943879
to
451c589
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
force-pushed
the
renovate/pnpm-7.x
branch
from
July 17, 2023 13:28
451c589
to
c4e1593
Compare
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
from
July 18, 2023 13:10
c4e1593
to
f690c0a
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
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 01:10
f690c0a
to
1079abe
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
February 15, 2024 13:24
1079abe
to
b979238
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
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.1.7
->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:[email protected]
becomesnpm:[email protected]
.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
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.