chore: apply useless change just to see if the open-next CI e2e workflow is flaky

[dario-piotrowicz]

Please ignore this PR 🙂

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
nodejs-org	✅ Ready (Inspect)	Visit Preview	Jul 30, 2025 4:43pm

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 72.98%. Comparing base (6b96719) to head (a9de586).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #8054   +/-   ##
=======================================
  Coverage   72.98%   72.98%           
=======================================
  Files          95       95           
  Lines        8324     8324           
  Branches      215      215           
=======================================
  Hits         6075     6075           
  Misses       2248     2248           
  Partials        1        1           

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

[dario-piotrowicz]

Closing since there doesn't seem to be any flakiness, also @avivkeller looked into the issue and it sounds like there was an actually legitimate bug (unrelated to open-next, which has since been solved) that caused the flakiness