update oclif

[n1ru4l]

Background

Description

Checklist

• Input validation
• Output encoding
• Authentication management
• Session management
• Access control
• Cryptographic practices
• Error handling and logging
• Data protection
• Communication security
• System configuration
• Database security
• File management
• Memory management
• Testing

[gemini-code-assist]

Summary of Changes

Hello @n1ru4l, I'm Gemini Code Assist¹! 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 enhancing the project's command-line interface (CLI) by performing a comprehensive update of the oclif framework and its related plugins. The primary goal is to bring the CLI infrastructure up to date with the latest oclif versions, which includes a major version bump for @oclif/core. Concurrently, the approach to applying necessary patches for oclif/core has been refined to be more generic and robust, ensuring consistent module resolution across different development environments.

Highlights

• Oclif Core Upgrade: The core Oclif framework, @oclif/core, has been upgraded from version ^3.26.6 to 4.8.0, representing a significant major version update.
• Oclif Plugin Updates: Associated Oclif plugins, @oclif/plugin-help and @oclif/plugin-update, have also been updated to 6.2.36 and 4.7.16 respectively, ensuring compatibility and leveraging new features.
• Patch Consolidation and Refinement: The patching strategy for @oclif/core has been streamlined. Version-specific patches (@oclif/[email protected] and @oclif/[email protected]) have been removed or consolidated into a single, generic @oclif/core.patch. This updated patch continues to provide a custom module resolution fallback for lib/module-loader.js to address potential issues with build tools like tsup/esbuild.

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

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

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. ↩

[github-actions]

📚 Storybook Deployment

The latest changes are available as preview in: https://pr-7499.hive-storybook.pages.dev

[gemini-code-assist]

Code Review

This pull request updates oclif and its related dependencies, including a major version bump for @oclif/core. However, a critical path traversal vulnerability has been identified in the updated oclif patch. This vulnerability stems from an unsanitized environment variable (OCLIF_CLI_CUSTOM_PATH) used in a fallback mechanism for module resolution, which could lead to Remote Code Execution (RCE). A remediation has been provided to validate the path before use. Additionally, a changeset is required for this update as it affects a library package.

[github-actions]

💻 Website Preview

The latest changes are available as preview in: https://pr-7499.hive-landing-page.pages.dev

[github-actions]

🚀 Snapshot Release (alpha)

The latest changes of this PR are available as alpha on npm (based on the declared changesets):

Package	Version	Info
@graphql-hive/cli	0.57.2-alpha-20260115145806-19890c1bf72c2c4b65fb7774940055934308dbe7	npm ↗︎ unpkg ↗︎
hive	9.0.0-alpha-20260115145806-19890c1bf72c2c4b65fb7774940055934308dbe7	npm ↗︎ unpkg ↗︎

[github-actions]

🐋 This PR was built and pushed to the following Docker images:

Targets: build

Platforms: linux/amd64

Image Tag: 19890c1bf72c2c4b65fb7774940055934308dbe7