Skip to content

Conversation

@taeold
Copy link
Contributor

@taeold taeold commented Nov 4, 2025

The release build in Cloud Build (Linux) was failing because npm ci could not find the @rolldown/binding-linux-x64-gnu native binding. This is a known issue when lockfiles are generated on non-Linux OSes.

Explicitly adding it to optionalDependencies ensures it's included in package-lock.json and correctly installed by npm ci on Linux, while being safely skipped on other platforms.

The release build in Cloud Build (Linux) was failing because `npm ci` could not find the `@rolldown/binding-linux-x64-gnu` native binding. This is a known issue when lockfiles are generated on non-Linux OSes.

Explicitly adding it to `optionalDependencies` ensures it's included in `package-lock.json` and correctly installed by `npm ci` on Linux, while being safely skipped on other platforms.
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @taeold, 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 resolves a critical Cloud Build failure on Linux by ensuring the necessary @rolldown/binding-linux-x64-gnu native binding is correctly included in the project's dependencies. By moving this specific binding to optionalDependencies, the build process on Linux environments will no longer fail due to missing native modules, while maintaining compatibility and avoiding unnecessary installations on other operating systems.

Highlights

  • Cloud Build Failure Resolution: Addressed a Cloud Build failure on Linux where npm ci could not find the @rolldown/binding-linux-x64-gnu native binding. This issue typically arises when package-lock.json is generated on non-Linux operating systems.
  • Dependency Management: Explicitly added @rolldown/binding-linux-x64-gnu to optionalDependencies in package.json and package-lock.json. This ensures the binding is included and correctly installed on Linux while being safely skipped on other platforms.
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.

Copy link
Contributor

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

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 correctly addresses a Cloud Build failure on Linux by explicitly adding the @rolldown/binding-linux-x64-gnu package to optionalDependencies. This ensures that npm ci can find and install the necessary native binding on Linux environments, even when the lockfile is generated on another OS. The changes to package.json and package-lock.json are appropriate for this fix. I have one comment regarding the long-term maintainability of this dependency version.

@taeold taeold enabled auto-merge November 4, 2025 19:02
@taeold taeold added this pull request to the merge queue Nov 4, 2025
@taeold taeold changed the title Fix Cloud Build failure by adding Linux rolldown bindings Fix release failure by adding Linux rolldown bindings Nov 4, 2025
Merged via the queue into master with commit 938ba9a Nov 4, 2025
32 checks passed
@github-project-automation github-project-automation bot moved this from Approved [PR] to Done in [Cloud] Extensions + Functions Nov 4, 2025
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.

3 participants