Skip to content

Update deps and refresh 2026 maintenance#19

Merged
Nek-12 merged 4 commits intomasterfrom
maintenance-2026-deps
Jan 6, 2026
Merged

Update deps and refresh 2026 maintenance#19
Nek-12 merged 4 commits intomasterfrom
maintenance-2026-deps

Conversation

@Nek-12
Copy link
Member

@Nek-12 Nek-12 commented Jan 6, 2026

Summary

  • bump deps and refresh lockfile
  • update 2026 maintenance/copyright notices
  • align cli header test mocks with new SDK constructor behavior

Testing

  • npm test -- --run

@gemini-code-assist
Copy link

Summary of Changes

Hello @Nek-12, 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 routine maintenance and dependency management, bringing the project's libraries and development tools up to date. It also includes an important adjustment to test mocks to accommodate recent changes in the SDK's client constructor, ensuring the test suite remains robust and reflective of current API behavior. The updates aim to improve overall project health, security, and developer experience.

Highlights

  • Dependency Updates: Numerous project dependencies have been updated to their latest versions, ensuring the project benefits from the newest features, bug fixes, and security patches. This includes core SDKs, development tools like ESLint and Vitest, and various underlying packages.
  • Maintenance Year Refresh: The copyright and maintenance notices across the project, specifically in the LICENSE.txt and README.md files, have been updated to reflect the year 2026, indicating ongoing project maintenance.
  • Test Mock Alignment: Unit tests for CLI headers have been refactored to align their SDK client transport mocks with recent changes in the SDK's constructor behavior, ensuring test accuracy and compatibility with the updated SDK.
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

@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 successfully updates dependencies, refreshes copyright and maintenance notices for 2026, and adapts test mocks to new SDK constructor behavior. The dependency updates, including a major version bump for vitest, are correctly handled in package.json and package-lock.json. The refactoring in tests/unit/cli-headers.test.ts to a more robust class-based mocking strategy is a solid improvement that aligns with the updated SDK. The changes are clean, well-documented in the PR description, and appear correct. I have no concerns with the proposed changes.

@Nek-12 Nek-12 enabled auto-merge January 6, 2026 19:43
@Nek-12 Nek-12 merged commit 99b6a1b into master Jan 6, 2026
3 checks passed
@Nek-12 Nek-12 deleted the maintenance-2026-deps branch January 6, 2026 19:44
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