upgrade nodejs version

[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 proposes an upgrade of the Node.js version from 25.7.0 to 25.8.0 as defined in the .node-version file. While this change is straightforward, I have added a suggestion to also specify the Node.js version in the package.json engines field. This will improve consistency and help prevent potential issues for developers using different environment setups.

[gemini-code-assist]

To ensure all developers use the correct Node.js version and to leverage built-in checks from package managers like npm and Yarn, it's a good practice to also specify the supported Node.js engine in your project's package.json file(s). This complements the .node-version file, which is often used by tools like nvm.

For example, you could add the following to website/package.json:

"engines": {
  "node": ">=25.8.0"
}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.13%. Comparing base (5b4d362) to head (ff75085).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2877   +/-   ##
=======================================
  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% <ø> (+0.06%)	⬆️
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.