hive-apollo-router-plugin: bump graphql-tools and hive-console-sdk

[ardatan]

Fixes #7557

[gemini-code-assist]

Summary of Changes

Hello @ardatan, 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 updating two critical dependencies, graphql-tools and hive-console-sdk, to their latest versions within the hive-apollo-router-plugin. This ensures the project leverages the most recent features, bug fixes, and security enhancements from these libraries, contributing to a more stable and up-to-date dependency ecosystem. The changes also include the necessary Cargo.lock updates and a new changeset entry to document these modifications.

Highlights

• Dependency Update: graphql-tools: The graphql-tools dependency has been updated from version 0.4.2 to 0.5.0.
• Dependency Update: hive-console-sdk: The hive-console-sdk dependency has been updated from version 0.3.3 to 0.3.4.
• Changelog Entry Added: A new changeset file (.changeset/nice-seas-juggle.md) has been added to document these dependency bumps for the hive-apollo-router-plugin.
• Cargo.lock Synchronization: The Cargo.lock file has been updated to reflect the new versions and checksums for graphql-tools, hive-console-sdk, and hive-apollo-router-plugin, and the once_cell dependency was removed from hive-console-sdk's transitive dependencies.

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 updates the graphql-tools and hive-console-sdk dependencies to their latest versions, along with the corresponding Cargo.lock file. A new changeset entry has been added to document these dependency bumps. The changes appear to be routine maintenance to keep the project dependencies up-to-date.

[github-actions]

📚 Storybook Deployment

The latest changes are available as preview in: https://pr-7559.hive-storybook.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/apollo	0.47.2-alpha-20260126114925-d2ba06c7c12be52e9aca6477037e21f348f64b3e	npm ↗︎ unpkg ↗︎
@graphql-hive/cli	0.57.4-alpha-20260126114925-d2ba06c7c12be52e9aca6477037e21f348f64b3e	npm ↗︎ unpkg ↗︎
@graphql-hive/core	0.20.2-alpha-20260126114925-d2ba06c7c12be52e9aca6477037e21f348f64b3e	npm ↗︎ unpkg ↗︎
@graphql-hive/envelop	0.40.4-alpha-20260126114925-d2ba06c7c12be52e9aca6477037e21f348f64b3e	npm ↗︎ unpkg ↗︎
@graphql-hive/yoga	0.47.2-alpha-20260126114925-d2ba06c7c12be52e9aca6477037e21f348f64b3e	npm ↗︎ unpkg ↗︎
hive	9.2.0-alpha-20260126114925-d2ba06c7c12be52e9aca6477037e21f348f64b3e	npm ↗︎ unpkg ↗︎
hive-apollo-router-plugin	3.0.2-alpha-20260126114925-d2ba06c7c12be52e9aca6477037e21f348f64b3e	npm ↗︎ unpkg ↗︎

[github-actions]

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

Targets: build

Platforms: linux/amd64

Image Tag: d2ba06c7c12be52e9aca6477037e21f348f64b3e

[github-actions]

💻 Website Preview

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

[github-actions]

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

Targets: apollo-router-hive-build

Platforms: linux/amd64

Image Tag: b034043f7a3e91bd9d7d9ce4af9473db77e8ff1f

[dotansimha]

should we pin with = or not? @kamilkisiela @ardatan

[dotansimha]

should we pin with = or not? @kamilkisiela @ardatan