chore(deps): update node

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Confidence
@google/adk	^0.1.3 -> ^0.2.0
@llamaindex/google (source)	^0.3.20 -> ^0.4.0

---

Release Notes

google/adk-js (@​google/adk)

v0.2.1

Compare Source

Bumping to version 0.2.1

v0.2.0

Compare Source

Bump to version 0.2.0

run-llama/LlamaIndexTS (@​llamaindex/google)

v0.4.0

Minor Changes

• 020928c: respect Gemini's requests-per-minute rate limit with waits

v0.3.22

Patch Changes

• Updated dependencies [06f884a]
  • @​llamaindex/core@​0.6.22

v0.3.21

Compare Source

Patch Changes

• c40adaf: Add latest google models to lib
• Updated dependencies [5da1cda]
  • @​llamaindex/core@​0.6.21

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[forking-renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: docs/en/getting-started/quickstart/js/llamaindex/package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: @llamaindex/[email protected]
npm error node_modules/@llamaindex/core
npm error   peer @llamaindex/core@"0.6.20" from @llamaindex/[email protected]
npm error   node_modules/@llamaindex/workflow
npm error     @llamaindex/workflow@"^1.1.22" from the root project
npm error
npm error Could not resolve dependency:
npm error @llamaindex/google@"^0.4.0" from the root project
npm error
npm error Conflicting peer dependency: @llamaindex/[email protected]
npm error node_modules/@llamaindex/core
npm error   peer @llamaindex/core@"0.6.22" from @llamaindex/[email protected]
npm error   node_modules/@llamaindex/google
npm error     @llamaindex/google@"^0.4.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-12-19T22_25_24_477Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-12-19T22_25_24_477Z-debug-0.log

[dpebot]

/gcbrun

[gemini-code-assist]

Summary of Changes

Hello @renovate-bot, 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 performs routine dependency maintenance by updating two core packages: @google/adk and @llamaindex/google. These updates bring the project up-to-date with the latest features, performance enhancements, and bug fixes, including crucial rate limiting for Gemini API requests within the @llamaindex/google package. The changes also involve a broad refresh of the underlying dependency tree, ensuring compatibility and stability with the updated primary packages.

Highlights

• @google/adk Update: The @google/adk package has been upgraded from version ^0.1.3 to ^0.2.0, incorporating new features and bug fixes from its 0.2.0 and 0.2.1 releases.
• @llamaindex/google Update: The @llamaindex/google package has been updated from ^0.3.20 to ^0.4.0, which notably includes a change to respect Gemini's requests-per-minute rate limit with waits.
• Dependency Tree Refinement: The package-lock.json file reflects a significant refresh of the dependency tree, introducing new packages related to OpenTelemetry and Google Cloud, and removing the peer: true flag from numerous existing dependencies.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 dependencies for the Node.js quickstarts. The update for @llamaindex/google appears to be a non-breaking improvement. However, the update for @google/adk to v0.2.0 introduces a large number of new peer dependencies for OpenTelemetry. This could cause warnings or errors during installation for users following the quickstart, as these dependencies are not included in the package.json. I've added a comment to address this potential issue.

[gemini-code-assist]

The update of @google/adk to version ^0.2.0 introduces a significant number of new peerDependencies related to OpenTelemetry. While these seem to be for optional tracing and monitoring features not used in this quickstart, their absence in this package.json will likely cause warnings during npm install and could potentially cause issues with different npm versions or configurations.

For a better user experience in a quickstart guide, it would be ideal to avoid these warnings. If these peer dependencies are required for the quickstart to function, they should be added to the dependencies here. If they are truly optional, it might be worth noting this in the quickstart documentation to preempt user confusion, or exploring if the @google/adk library could be adjusted to use optionalDependencies to improve the developer experience.

[dpebot]

/gcbrun

[forking-renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[twishabansal]

/gcbrun

[dpebot]

/gcbrun