Fix broken lockfile from merged dependabot PRs

[horgh]

The eslint and @eslint/js dependabot PRs were merged in quick succession, leaving the lockfile with a stale reference to eslint@10.0.0 in the @eslint/js peer dependency snapshot.

[gemini-code-assist]

Summary of Changes

Hello, 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 addresses and rectifies an inconsistency in the pnpm-lock.yaml file. The issue arose from a rapid succession of Dependabot merges for eslint and @eslint/js, which left the lockfile with an outdated eslint version reference. The changes ensure the lockfile accurately reflects the correct dependency versions and includes updated platform-specific metadata.

Highlights

• Lockfile Correction: The pnpm-lock.yaml file was updated to resolve a stale reference to eslint@10.0.0 within the @eslint/js peer dependency snapshot, which occurred after two Dependabot PRs were merged in quick succession.
• Dependency Version Update: The eslint version referenced by @eslint/js in both devDependencies and the snapshots section of the lockfile was correctly updated from 10.0.0 to 10.0.1.
• Platform Metadata Enhancement: Added libc definitions (e.g., glibc, musl) to several @unrs/resolver-binding-linux-* packages within the lockfile, likely a result of regenerating the lockfile.

Changelog

• pnpm-lock.yaml
  • Corrected the eslint version from 10.0.0 to 10.0.1 for the @eslint/js package in devDependencies.
  • Updated the eslint version from 10.0.0 to 10.0.1 within the @eslint/js snapshot entry.
  • Introduced libc specifications (e.g., glibc, musl) for various @unrs/resolver-binding-linux-* packages.

Activity

• No specific activity (comments, reviews, or progress updates) has been recorded for this pull request since its creation.

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

[gemini-code-assist]

Code Review

This pull request correctly resolves an issue with a broken pnpm-lock.yaml file. The changes update a stale peer dependency reference for @eslint/js to the correct version of eslint, which fixes the inconsistency caused by successive Dependabot merges. The other modifications in the lockfile are consistent with the regeneration of the file and appear to be correct.