yarn upgrade --latest && yarn build

[sensuikan1973]

Auto-generated by create-pull-request

---

See: https://github.com/peter-evans/create-pull-request/blob/master/docs/concepts-guidelines.md#triggering-further-workflow-runs

[gemini-code-assist]

Code Review

This pull request appears to be an automated dependency upgrade using yarn upgrade --latest. While keeping dependencies up-to-date is good practice, using --latest can be risky as it ignores the version ranges specified in package.json and may introduce breaking changes from major version updates. It's generally safer to use yarn upgrade which respects semantic versioning. I've also found a critical issue with the @types/node dependency which seems to point to a non-existent version, which will likely break the build.

_{Note: Security Review has been skipped due to the limited scope of the PR.}

[gemini-code-assist]

The version for @types/node appears to be incorrect. The lockfile specifies version 25.3.5, but this version does not seem to exist in the public npm registry. The resolved URL https://registry.yarnpkg.com/@types/node/-/node-25.3.5.tgz is not accessible, which will likely cause yarn install to fail. Please investigate the automated process that generated this change. It's possible that a different dependency is causing this incorrect resolution, or there's an issue with the environment where this command was run.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.13%. Comparing base (edabd34) to head (e4a876f).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2881   +/-   ##
=======================================
  Coverage   94.13%   94.13%           
=======================================
  Files          52       52           
  Lines        1483     1483           
=======================================
  Hits         1396     1396           
  Misses         87       87           

Flag	Coverage Δ
integration_test	65.00% <ø> (ø)
macos-latest	93.05% <ø> (ø)
ubuntu	93.59% <ø> (ø)
widget_test	90.28% <ø> (ø)
windows	93.45% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 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.