chore(deps): update pnpm to v8.15.7 #10
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/pnpm-8.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
8.10.5->8.15.7Release Notes
pnpm/pnpm (pnpm)
v8.15.7Compare Source
Patch Changes
pnpm config getprints a comma-separated list for an array value instead of nothing.Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v8.15.6Compare Source
Patch Changes
pnpm run#7817.peerDependencies#7813.--ignore-scriptsargument toprunecommand #7836.Platinum Sponsors
Gold Sponsors
Silver Sponsors
v8.15.5Compare Source
Patch Changes
Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v8.15.4Compare Source
Patch Changes
readPackagehook should work #7704.Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v8.15.3Compare Source
Patch Changes
Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v8.15.2Compare Source
Patch Changes
node_modulesdirectories, pnpm will no longer print multiple prompts simultaneously.node_modules.package.json#4761.Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v8.15.1Compare Source
Patch Changes
object-hashlibrary instead ofnode-object-hashfor hashing keys of side-effects cache #7591.bundledDependenciesshould never be added to the lockfile withfalseas the value #7576.Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v8.15.0Compare Source
Upgrade to v8.15.1 or newer
Minor Changes
package.jsonbut a license file exists, try to match and extract the license name #7530.Patch Changes
pnpm update -r --latestwill no longer downgrade prerelease dependencies #7436.--aggregate-outputshould work on scripts executed from the same project #7556.pnpm update --latestruns with arguments containing versions specs. For instance,pnpm update --latest foo@nextis not allowed #7567.Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v8.14.3Compare Source
Patch Changes
pnpm packshould work as expected when "prepack" modifies the manifest #7558.Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v8.14.2Compare Source
Patch Changes
pnpm dlxshould not fail, when executed frompackage.json"scripts" 7424.pnpm publishshould pack "main" file or "bin" files defined in "publishConfig" #4195.Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v8.14.1Compare Source
Patch Changes
pnpm publish#7316.hoisted-workspace-packagesistruedon't hoist the root package even if it has a name. Otherwise we would create a circular symlink.Our Gold Sponsors
Our Silver Sponsors
v8.14.0Compare Source
Minor Changes
hoist-workspace-packagesis set totrue, packages from the workspace are symlinked to either<workspace_root>/node_modules/.pnpm/node_modulesor to<workspace_root>/node_modulesdepending on other hoisting settings (hoist-patternandpublic-hoist-pattern) #7451.pnpm dedupecommand now accepts more command line options that thepnpm installcommand also accepts. Example:pnpm dedupe --store-dir=local-store-dirPatch Changes
pnpm deployshould not touch the target directory if it already exists and isn't empty #7351.pnpm add a-module-already-in-dev-depswill show a message to notice the user that the package was not moved to "dependencies" #926 and fix #7319.Our Gold Sponsors
Our Silver Sponsors
v8.13.1Minor Changes
New commands added for inspecting the store:
pnpm cat-index: Prints the index file of a specific package in the store. The package is specified by its name and version:
pnpm cat-file: Prints the contents of a file based on the hash value stored in the index file. For example:
(EXPERIMENTAL) pnpm find-hash: Lists the packages that include the file with the specified hash. For example:
This command is experimental. We might change how it behaves.
Related issue: #7413.
A new setting added for symlinking injected dependencies from the workspace, if their dependencies use the same peer dependencies as the dependent package. The setting is called
dedupe-injected-deps#7416.Use
--fail-if-no-matchif you want the CLI fail if no packages were matched by the command #7403.Patch Changes
pnpm list --parseableshould not print the same dependency multiple times #7429.pnpm envcommands #7456.pnpm update --interactivecommand #7439.update -i -rwith Git specifiers #7415.Our Gold Sponsors
Our Silver Sponsors
v8.12.1Compare Source
Patch Changes
--fix-lockfilecrashes on tarballs #7368.node_modulesdirectory cannot be removed #7405.Our Gold Sponsors
Our Silver Sponsors
v8.12.0Compare Source
Minor Changes
Patch Changes
dedupe-direct-depsis set totrue, commands of dependencies should be deduplicated #7359.Our Gold Sponsors
Our Silver Sponsors
v8.11.0Compare Source
Minor Changes
(IMPORTANT) When the package tarballs aren't hosted on the same domain on which the registry (the server with the package metadata) is, the dependency keys in the lockfile should only contain
/<pkg_name>@​<pkg_version, not<domain>/<pkg_name>@​<pkg_version>.This change is a fix to avoid the same package from being added to
node_modules/.pnpmmultiple times. The change to the lockfile is backward compatible, so previous versions of pnpm will work with the fixed lockfile.We recommend that all team members update pnpm in order to avoid repeated changes in the lockfile.
Related PR: #7318.
Patch Changes
pnpm add a-module-already-in-dev-depswill show a message to notice the user that the package was not moved to "dependencies" #926.Our 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 has been generated by Renovate Bot.
390dbd03c6toee337641c6chore(deps): update pnpm to v8.11.0to chore(deps): update pnpm to v8.13.1ee337641c6to178ca9a8f7chore(deps): update pnpm to v8.13.1to chore(deps): update pnpm to v8.14.0178ca9a8f7to35e237731cchore(deps): update pnpm to v8.14.0to chore(deps): update pnpm to v8.14.135e237731ctoe5efa214d1chore(deps): update pnpm to v8.14.1to chore(deps): update pnpm to v8.15.1e5efa214d1to061b53ec49chore(deps): update pnpm to v8.15.1to chore(deps): update pnpm to v8.15.2061b53ec49toa5434c0108chore(deps): update pnpm to v8.15.2to chore(deps): update pnpm to v8.15.3a5434c0108to9929b9a4cdchore(deps): update pnpm to v8.15.3to chore(deps): update pnpm to v8.15.49929b9a4cdto7a42db11f6chore(deps): update pnpm to v8.15.4to chore(deps): update pnpm to v8.15.57a42db11f6to6767a51257chore(deps): update pnpm to v8.15.5to chore(deps): update pnpm to v8.15.66767a51257to5b5fd5075fchore(deps): update pnpm to v8.15.6to chore(deps): update pnpm to v8.15.7Checkout
From your project repository, check out a new branch and test the changes.