net - chore: upgrading undici to 7.22.0

[jaredwray]

Please check if the PR fulfills these requirements

• Followed the Contributing guidelines and Code of Conduct
• Tests for the changes have been added (for bug fixes/features) with 100% code coverage.

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
net - chore: upgrading undici to 7.22.0

[gemini-code-assist]

Summary of Changes

Hello @jaredwray, 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 routine dependency maintenance by upgrading the undici HTTP client library and its associated type definitions. This update ensures that the project benefits from the latest improvements, bug fixes, and features provided by these packages, contributing to overall stability and performance without introducing new functional changes.

Highlights

• Dependency Upgrade: Upgraded the undici package from 7.19.1 to 7.22.0 in the packages/net module.
• Type Definition Update: Updated the @types/http-cache-semantics package from 4.0.4 to 4.2.0.
• Lockfile Synchronization: Synchronized the pnpm-lock.yaml file to reflect the updated dependency versions and removed older, unused dependency entries.

Changelog

• packages/net/package.json
  • Updated undici dependency to ^7.22.0
  • Updated @types/http-cache-semantics dev dependency to ^4.2.0
• pnpm-lock.yaml
  • Updated undici version to 7.22.0 in the lockfile
  • Updated @types/http-cache-semantics version to 4.2.0 in the lockfile
  • Removed outdated undici@7.19.1 and undici@7.20.0 entries
  • Removed outdated @types/http-cache-semantics@4.0.4 entry

Activity

• No human activity has been recorded on this pull request yet.

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 upgrades undici to version 7.22.0 and @types/http-cache-semantics to 4.2.0. The changes in packages/net/package.json and pnpm-lock.yaml are correct for this dependency upgrade.

While reviewing the related code, I identified a potential bug in packages/net/src/index.ts. In the get method, the logic at lines 242-243 incorrectly disables caching if the caching option is set to true, contrary to the documentation. The condition if (options?.caching !== undefined) should likely be if (options?.caching === false) to align with the documented behavior and the implementation of other methods like head. As this is outside the files changed in this PR, I recommend addressing it in a separate pull request.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (d9e8518) to head (0ff6566).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #1589   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           26        26           
  Lines         2447      2447           
  Branches       545       544    -1     
=========================================
  Hits          2447      2447           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.