Default to NPM if javascript_package_manager is unset, require pnpm v11.x, and release v1.21.1 - #435
Merged
Merged
Conversation
* For backwards compatibility, we need to be explicit about the change in the JS package manager, or else users of existing instance that upgraded `invenio-cli` would get out of nowhere an error message about `pnpm` missing.
slint
changed the title
javascript_package_manager is unset, require pnpm v11.x, and release v1.21.1
utnapischtim
approved these changes
Aug 5, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
fix(config): default to NPM if
javascript_package_manageris unsetin the JS package manager, or else users of existing instance that
upgraded
invenio-cliwould get out of nowhere an error messageabout
pnpmmissing.fix(requirements): require pnpm v11.x
📦 release: v1.12.1