chore: add skew-version support in Cloudflare open-next worker

[dario-piotrowicz]

Description

This PR adds support for skew protection in the Cloudflare open-next deployment (which has been recently added to the open-next adapter (in 1.5.0))

For more details on the feature see: https://opennext.js.org/cloudflare/howtos/skew

Validation

I've applied the changes and deployed the site: https://nodejs-org.testing.devprod.cloudflare.dev/en
And everything seems to be working as expected 🙂

I'll double check with @vicb if he has some suggestion to best test that the skew protection is actually in place and working as expected 🙂

Related Issues

Check List

• I have read the Contributing Guidelines and made commit messages that follow the guideline.
• I have run pnpm format to ensure the code follows the style guide.
• I have run pnpm test to check if all tests are passing.
• I have run pnpm build to check if the website builds without errors.
• I've covered new added functionality with unit tests if necessary.

[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 25, 2025 1:53pm

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 73.01%. Comparing base (230c564) to head (3e2e029).
Report is 1 commits behind head on main.

✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
packages/rehype-shiki/src/index.mjs	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7980      +/-   ##
==========================================
+ Coverage   72.95%   73.01%   +0.06%     
==========================================
  Files          95       95              
  Lines        8317     8317              
  Branches      215      214       -1     
==========================================
+ Hits         6068     6073       +5     
+ Misses       2248     2243       -5     
  Partials        1        1              

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

[dario-piotrowicz]

https://github.com/nodejs/nodejs.org/actions/runs/16280236085/job/45968187377?pr=7980#step:11:74 👀

again! is this something that is happening quite often? 😓

[avivkeller]

https://github.com/nodejs/nodejs.org/actions/runs/16280236085/job/45968187377?pr=7980#step:11:74 👀

again! is this something that is happening quite often? 😓

Yea, it happens pretty often now that I think about it.

https://github.com/nodejs/nodejs.org/actions/workflows/playwright-cloudflare-open-next.yml?query=is%3Afailure

[dario-piotrowicz]

https://github.com/nodejs/nodejs.org/actions/runs/16280236085/job/45968187377?pr=7980#step:11:74 👀
again! is this something that is happening quite often? 😓

Yea, it happens pretty often now that I think about it.

https://github.com/nodejs/nodejs.org/actions/workflows/playwright-cloudflare-open-next.yml?query=is%3Afailure

oof... and do you know if it is just happening on the open-next build?

[avivkeller]

oof... and do you know if it is just happening on the open-next build?

yes, it's not duplicated on the regular Playwright run. We've had no¹ failures on that.

Footnotes

1. Excluding changes that you would expect to break Playwright. ↩

[dario-piotrowicz]

oof... and do you know if it is just happening on the open-next build?

yes, it's not duplicated on the regular Playwright run. We've had no1 failures on that.

Footnotes

1. Excluding changes that you would expect to break Playwright. ↩

ok, so sorry for the inconvenience 🙇 I'll look into addressing the issue then 🙇

[avivkeller]

No problem! It's not a required check so it's not breaking anything

[dario-piotrowicz]

No problem! It's not a required check so it's not breaking anything

good! but it must be pretty annoying 😅😓

[AugustinMauroy]

LGMT !

[ovflowd]

LGTM! Buit can we document this variable for the time being somewhere? (the OPEN_NEXT_CLOUDFLARE)

[ovflowd]

LGMT !

Every time you write LGMT I feel like I want to eat Subway's BLT for some reason

[avivkeller]

LGMT !

Every time you write LGMT I feel like I want to eat Subway's BLT for some reason

Looks good, me too!

[avivkeller]

Yeah, no problem

[dario-piotrowicz]

#8023 🙂

[github-actions]

Lighthouse Results

URL	Performance	Accessibility	Best Practices	SEO	Report
/en	🟠 82	🟢 100	🟢 100	🟢 100	🔗
/en/about	🟢 100	🟢 97	🟢 100	🟠 88	🔗
/en/about/previous-releases	🟢 99	🟢 93	🟢 100	🟠 89	🔗
/en/download	🟠 87	🟢 100	🟢 100	🟢 100	🔗
/en/blog	🟢 100	🟢 100	🟢 96	🟢 100	🔗

[ovflowd]

@dario-piotrowicz builds seems to be failing tho

[dario-piotrowicz]

@dario-piotrowicz builds seems to be failing tho

Thanks 🙂

Yeah I noticed, for some reason the build script is not detecting the open-next package, I don't really understand why 😕

I've fixed it in this way: 3e2e029

Not the best solution possible but I think it should be good enough for now and we can always dig deeper into the issue if/when needed? what do you think? 🙂

---

PS: I couldn't reproduce the issue locally 😕