Update opennext to 1.0.0-beta.0

[SamyPesse]

No description provided.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 67375d6

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

Summary of the deployments:

Version 1 (production)

Version	URL	Status
Latest commit	https://65377153.gitbook-open.pages.dev	✅
PR	https://pr3102.gitbook-open.pages.dev	✅

Version 2 (experimental)

Version	URL	Status
Vercel	https://gitbook-v2-l98d99h4w-gitbook.vercel.app	✅
Cloudflare		✅

Test content

Site	v1	v2
GitBook	https://65377153.gitbook-open.pages.dev/docs.gitbook.com	https://gitbook-v2-l98d99h4w-gitbook.vercel.app/url/docs.gitbook.com
E2E	https://65377153.gitbook-open.pages.dev/gitbook.gitbook.io/test-gitbook-open	https://gitbook-v2-l98d99h4w-gitbook.vercel.app/url/gitbook.gitbook.io/test-gitbook-open

[argos-ci]

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build	Status	Details	Updated (UTC)
customers-v1 (Inspect)	👍 Changes approved	4 changed	Apr 5, 2025, 9:24 PM
customers-v2 (Inspect)	👍 Changes approved	4 changed	Apr 5, 2025, 9:27 PM
default (Inspect)	✅ No changes detected	-	Apr 5, 2025, 9:48 PM
v2-vercel (Inspect)	✅ No changes detected	-	Apr 5, 2025, 9:28 PM

[Copilot]

Copilot reviewed 13 out of 15 changed files in this pull request and generated 1 comment.

Files not reviewed (2)

• packages/gitbook-v2/package.json: Language not supported
• packages/gitbook-v2/wrangler.jsonc: Language not supported

Comments suppressed due to low confidence (1)

packages/gitbook-v2/src/lib/data/memoize.test.ts:49

• [nitpick] The hard-coded expected cache key value in this test makes the test brittle if the serialization of the cache key changes. Consider computing the expected cache key dynamically to safeguard against future modification of the key generation logic.

expect(await memoized({ a: 1, b: 2 }, 4)).toBe('[[["a",1],["b",2]],4], result=7');