Changelog for pnpm-9.12.1-lp156.15.1.noarch.rpm :

* Tue Oct 08 2024 Avindra Goolcharan - update to version 9.12.1:
* pnpm update --latest should not update the automatically installed peer dependencies #6657
* pnpm publish should be able to publish from a local tarball #7950
* Prevent EBUSY errors caused by creating symlinks in parallel dlx processes #8604
* Fix maximum call stack size exceeded error related to circular workspace dependencies #8599
* Fri Oct 04 2024 Avindra Goolcharan - update to version 9.12.0:
* Fix peer dependency resolution dead lock #8570. This change might change some of the keys in the snapshots field inside pnpm-lock.yaml but it should happen very rarely.
* pnpm outdated command supports now a --sort-by=name option for sorting outdated dependencies by package name #8523
* Added the ability for overrides to remove dependencies by specifying \"-\" as the field value #8572
* Fixed an issue where pnpm list --json pkg showed \"private\": false for a private package #8519
* Packages with libc that differ from pnpm. supportedArchitectures.libc are not downloaded #7362
* Prevent ENOENT errors caused by running store prune in parallel #8586
* Add issues alias to pnpm bugs #8596
* Sat Sep 21 2024 Avindra Goolcharan - update to version 9.11.0:
* Experimental: added pnpm cache commands for inspecting the metadata cache #8512
* Fix a regression in which pnpm deploy with node-linker=hoisted produces an empty node_modules directory #6682
* pnpm deploy should work in workspace with shared-workspace-lockfile=false #8475
* Don\'t print a warning when linking packages globally #4761
* Wed Sep 11 2024 Avindra Goolcharan - update to version 9.10.0:
* Support for a new CLI flag, --exclude-peers, added to the list and why commands. When --exclude-peers is used, peer dependencies are not printed in the results, but dependencies of peer dependencies are still scanned #8506.
* Added a new setting to package.json at pnpm.auditConfig. ignoreGhsas for ignoring vulnerabilities by their GHSA code #6838.
* Throw an exception if pnpm switches to the same version of itself.
* Reduce memory usage during peer dependencies resolution.
* Mon Sep 02 2024 Virinas-code - update to version 9.9.0:
* https://github.com/pnpm/pnpm/compare/v9.8.0...v9.9.0
* Minor breaking change. We had to optimize how we resolve peer dependencies in order to fix some infinite loops and out-of-memory errors during peer dependencies resolution.
* pnpm deploy should write the node_modules/.modules.yaml to the node_modules directory within the deploy directory #7731
* Don\'t override a symlink in node_modules if it already points to the right location pnpm/symlink-dir#54- changes from 9.8.0:
* https://github.com/pnpm/pnpm/compare/v9.7.1...v9.8.0
* Added a new command for upgrading pnpm itself when it isn\'t managed by Corepack: pnpm self-update. This command will work, when pnpm was installed via the standalone script from the pnpm installation page #8424
* CLI tools installed in the root of the workspace should be added to the PATH, when running scripts and use-node-version is set
* pnpm setup should never switch to another version of pnpm
* Ignore non-string value in the os, cpu, libc fields, which checking optional dependencies #8431
* Remember the state of edit dir, allow running pnpm patch-commit the second time without having to re-run pnpm patch- changes from 9.7.1:
* https://github.com/pnpm/pnpm/compare/v9.7.0...v9.7.1
* Fixed passing public-hoist-pattern and hoist-pattern via env variables #8339
* pnpm setup no longer creates Batch/Powershell scripts on Linux and macOS #8418
* When dlx uses cache, use the real directory path not the symlink to the cache #8421
* pnpm exec now supports executionEnv #8356
* Remove warnings for non-root pnpm field, add warnings for non-root pnpm subfields that aren\'t executionEnv #8143
* Replace semver in \"peerDependency\" with workspace protocol [#8355]
* Fix a bug in patch-commit in which relative path is rejected [#8405]
* Update Node.js in AATTpnpm/exe to v20- changes from 9.7.0:
* https://github.com/pnpm/pnpm/compare/v9.6.0...v9.7.0
* Added pnpm version management. If the manage-package-manager-versions setting is set to true, pnpm will switch to the version specified in the packageManager field of package.json #8363
* Added the ability to apply patch to all versions #8337
* Change the default edit dir location when running pnpm patch from a temporary directory to node_modules/.pnpm_patches/pkg[AATTversion] to allow the code editor to open the edit dir in the same file tree as the main project #8379.
* Substitute environment variables in config keys #6679
* pnpm install should run node-gyp rebuild if the project has a binding.gyp file even if the project doesn\'t have an install script #8293
* Print warnings to stderr #8342
* Peer dependencies of optional peer dependencies should be automatically installed #8323
* Thu Jul 25 2024 Avindra Goolcharan - update to version 9.6.0:
* Support specifying node version (via pnpm.executionEnv.nodeVersion in package.json) for running lifecycle scripts per each package in a workspace #6720
* Overrides now support the catalogs: protocol #8303
* The pnpm deploy command now supports the catalog: protocol #8298
* The pnpm outdated command now supports the catalog: protocol #8304
* Correct the error message when trying to run pnpm patch without node_modules/.modules.yaml #8257
* Silent reporting fixed with the pnpm exec command #7608
* Add registries information to the calculation of dlx cache hash #8299
* Tue Jul 09 2024 Avindra Goolcharan - update to version 9.5.0:
* Added support for catalogs #8122
* Read authentication information from .npmrc in the current directory when running dlx #7996
* Updated AATTpnpm/tabtab to v0.5.4, enabling zsh autocomplete lazy loading #8236
* Installation with filtering will now work, when dedupe-peer- dependents is set to true #6300
* Fixed dlx not actually using the Node.js version specified by - -use-node-version.
* Sat Jul 06 2024 Avindra Goolcharan - update to version 9.4.0:
* Some registries allow the exact same content to be published under different package names and/or versions. This breaks the validity checks of packages in the store. To avoid errors when verifying the names and versions of such packages in the store, you may now set the strict-store-pkg-content-check setting to false #4724
* Fix package-manager-strict-version missing in config #8195
* If install is performed on a subset of workspace projects, always create an up-to-date lockfile first. So, a partial install can be performed only on a fully resolved (non-partial) lockfile #8165
* Handle workspace protocol with any semver range specifier, when used in peer dependencies #7578
* Fri Jun 14 2024 Avindra Goolcharan - update to version 9.3.0:
* Semi-breaking. Dependency key names in the lockfile are shortened if they are longer than 1000 characters. We don\'t expect this change to affect many users. Affected users most probably can\'t run install successfully at the moment. This change is required to fix some edge cases in which installation fails with an out-of-memory error or \"Invalid string length (RangeError: Invalid string length)\" error. The max allowed length of the dependency key can be controlled with the peers- suffix-max-length setting #8177.
* Set reporter-hide-prefix to true by default for pnpm exec. In order to show prefix, the user now has to explicitly set reporter - hide-prefix=false #8174.- changes from 9.2.0:
* If package-manager-strict-version is set to true, pnpm will fail if its version doesn\'t exactly match the version in the \"packageManager\" field of package.json.
* Update AATTyarnpkg/pnp to the latest version, fixing issue with node: imports #8161.
* Deduplicate bin names to prevent race condition and corrupted bin scripts #7833.
* pnpm doesn\'t fail if its version doesn\'t match the one specified in the \"packageManager\" field of package.json #8087.
* exec now also streams prefixed output when --recursive or - -parallel is specified just as run does #8065.- changes from 9.1.4:
* Improved the performance of the resolution stage by changing how missing peer dependencies are detected #8144.- changes from 9.1.3:
* Fix a bug in which a dependency that is both optional for one package but non-optional for another is omitted when optional=false #8066.
* Clear resolution cache before starting peer dependencies resolution #8109.
* Reduce memory usage by peer dependencies resolution #8072.
* Tue May 21 2024 draskmontAATTprotonmail.com- update to version 9.1.2- require nodejs >= 18
* Sat Apr 27 2024 Avindra Goolcharan - update to version 9.0.6:
* Lockfiles that have git-hosted dependencies specified should be correctly converted to the new lockfile format #7990.
* Don\'t upgrade the lockfile format on pnpm install - -frozen-lockfile #7991.- includes version 9.0.5:
* Lockfiles with local or git-hosted dependencies are now successfully converted to the new lockfile format #7955.
* Resolve peer dependencies correctly, when they have prerelease versions #7977.
* Fix aliased dependencies resolution on repeat install with existing lockfile, when the aliased dependency doesn\'t specify a version or range #7957.
* The lockfile should be saved in the new format even if it is up-to-date.- run spec-cleaner
* Sat Apr 20 2024 draskmontAATTprotonmail.com- update to version 9.0.4- Added shell completion subpackages for bash, zsh and fish- Removed python2 dependency- Prevent packaging of executable files for other OS.- Cleaned up specfile:
* Removed some unused tags, macros and redudant requirements
* Added licensing header
* Fixed rpmlint errors and warnings- Removed unused _service file- Restored changelog
* Thu Jan 25 2024 Marcel Kuehlhorn - update to version 8.14.3
* https://github.com/pnpm/pnpm/compare/v8.4.0...v8.14.3
* Mon Jan 14 2019 John Vandenberg - initial revision for pnpm 2.25.1