Skip to content

chore: sync pnpm-lock.yaml with extension openclaw peer ranges#111

Merged
linfangw merged 1 commit into
mainfrom
v2026.3.23-2
Mar 23, 2026
Merged

chore: sync pnpm-lock.yaml with extension openclaw peer ranges#111
linfangw merged 1 commit into
mainfrom
v2026.3.23-2

Conversation

@linfangw

Copy link
Copy Markdown
Member

No description provided.

@linfangw
linfangw merged commit 35efb40 into main Mar 23, 2026
2 of 8 checks passed
@gemini-code-assist

Copy link
Copy Markdown

Summary of Changes

Hello, 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

  • Dependency Management Update: The 'openclaw' package was transitioned from a 'devDependency' to a direct 'dependency' for numerous extensions, reflecting its role as a core requirement.
  • Version Specification Refinement: The 'openclaw' dependency's version specification was updated from a 'workspace:*' link to a fixed version '2026.3.22' with a peer range '>=2026.3.22', ensuring explicit version resolution.
  • Lockfile Synchronization: The 'pnpm-lock.yaml' file was synchronized to incorporate the updated 'openclaw' dependency details, including its full package definition and snapshot entry with all transitive dependencies.

🧠 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 Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Comment thread pnpm-lock.yaml
Comment on lines +5484 to +5486
openclaw@2026.3.22:
resolution: {integrity: sha512-jQqQjRbgTiYf41PKPAIqNAPVmf0WyK4OpRhMCKP5NrC61lNqRXj4n13FMmt8l/pwNQtajtZTXEJEFfQqTKrWLA==}
engines: {node: '>=22.16.0'}

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant