chore: sync pnpm-lock.yaml with extension openclaw peer ranges#111
Conversation
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request focuses on a critical synchronization of the 'pnpm-lock.yaml' file to accurately reflect the 'openclaw' package's dependency status and versioning across various extensions. By moving 'openclaw' from development to direct dependencies and specifying a concrete version, the changes aim to standardize dependency resolution and ensure consistent behavior throughout the project. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request updates the pnpm-lock.yaml file, specifically changing the openclaw dependency for several extensions. The dependency is moved from devDependencies to dependencies and its version is updated to 2026.3.22. A new package entry for openclaw@2026.3.22 is also added, specifying an engine requirement of node: '>=22.16.0'. The reviewer highlighted that the openclaw version appears to be a future date and the Node.js engine requirement is likely for an unreleased version, which could block dependency installation for developers.
| openclaw@2026.3.22: | ||
| resolution: {integrity: sha512-jQqQjRbgTiYf41PKPAIqNAPVmf0WyK4OpRhMCKP5NrC61lNqRXj4n13FMmt8l/pwNQtajtZTXEJEFfQqTKrWLA==} | ||
| engines: {node: '>=22.16.0'} |
There was a problem hiding this comment.
The version for openclaw is set to 2026.3.22, which appears to be a date in the distant future. This is highly unconventional and likely a mistake.
More critically, the engines requirement is set to node: '>=22.16.0'. This Node.js version is likely not yet released, which will block developers from installing dependencies and working on the project. Please use a stable and correct version of openclaw with a less restrictive Node.js engine requirement.
No description provided.