[Snyk] Security upgrade graphql-tools from 5.0.0 to 9.0.1

[nn6n]

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

• examples/data-blending/dashboard-app/package.json
• examples/data-blending/dashboard-app/yarn.lock

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Predictable Value Range from Previous Values SNYK-JS-FORMDATA-10841150	863

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[gemini-code-assist]

Summary of Changes

Hello @nn6n, 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 is an automated security fix initiated by Snyk to update a critical dependency, graphql-tools, to its latest major version. The update aims to resolve a known vulnerability and, as a consequence, significantly refactors the project's dependency graph by introducing newer versions of related packages and removing deprecated ones.

Highlights

• Security Upgrade: The primary purpose of this pull request is to upgrade the graphql-tools library from version 5.0.0 to 9.0.1 in the examples/data-blending/dashboard-app project. This upgrade directly addresses a critical security vulnerability (SNYK-JS-FORMDATA-10841150) identified by Snyk, which has a high severity score of 863.
• Dependency Tree Overhaul: The major version bump of graphql-tools has led to a significant update of the project's dependency tree, as reflected in yarn.lock. This includes the introduction of several new @graphql-tools/* packages (e.g., @graphql-tools/merge, @graphql-tools/schema, @graphql-tools/utils), @apollo/client, and various utility libraries, while also removing some older, no longer required dependencies.
• Potential Breaking Changes & Zero-Install Note: As this is a major version upgrade for graphql-tools, it is flagged as a breaking change. For users leveraging Yarn's zero-installs feature, it's important to note that a manual yarn command will be required to update the .yarn/cache/ directory after pulling these changes.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 or fill out our survey to provide feedback.

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 upgrades graphql-tools from version 5.0.0 to 9.0.1 to address a security vulnerability. This is a major version upgrade that introduces significant breaking changes. The application code will likely require modifications to be compatible with the new version of graphql-tools. It is crucial to perform thorough testing to ensure the application remains functional after this upgrade. If graphql-tools is an unused dependency, consider removing it instead.

[gemini-code-assist]

Upgrading graphql-tools from v5 to v9 is a major version jump that introduces significant breaking changes. This upgrade will likely break the application if the package is in use.

Key breaking changes between these versions include:

• Modularization: Core functionalities have been moved to scoped packages. For example, makeExecutableSchema is now imported from @graphql-tools/schema instead of graphql-tools.
• API Changes: Many APIs have been altered, and some have been removed entirely.

The application code must be updated to align with the new APIs of graphql-tools v9. Without these updates, the application will likely fail at build time or runtime.

Since no direct usage of graphql-tools was found in the provided source files, it might be an unused dependency. If that's the case, it should be removed from package.json rather than being upgraded.