Make sure to use the correct version for adaptive content

[conico974]

Use contextId from PublishedContentSite to force refresh RSC data based on it.
When the claims change, the whole RSC data would get refreshed.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 2afb7a7

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	URL	Status
Vercel	https://gitbook-v2-lgc5jco33-gitbook.vercel.app	✅
Cloudflare	https://8534feda-gitbook-open-v2-preview.gitbook.workers.dev	✅

Test content

Site	2v	2c
GitBook	https://gitbook-v2-lgc5jco33-gitbook.vercel.app/url/gitbook.com/docs	https://8534feda-gitbook-open-v2-preview.gitbook.workers.dev/url/gitbook.com/docs
E2E	https://gitbook-v2-lgc5jco33-gitbook.vercel.app/url/gitbook.gitbook.io/test-gitbook-open	https://8534feda-gitbook-open-v2-preview.gitbook.workers.dev/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-v2 (Inspect)	✅ No changes detected	-	Jul 24, 2025, 9:18 AM
v2-cloudflare (Inspect)	👍 Changes approved	1 changed	Jul 24, 2025, 9:22 AM
v2-vercel (Inspect)	👍 Changes approved	1 changed	Jul 24, 2025, 9:18 AM

[conico974]

I've spent way too much time trying to understand what's going on here.
It seems that the staleTimes that we set for the client is not always respected.
Sometimes before the 5 minutes where it should serve stale requests from the client cache, it still triggers a request.

It's not perfect, but this PR should allow us to be safe and have a good enough client cache.
The only downsides is the "ugly" URL that we get

[SamyPesse]

While the approach makes sense, it forces us to have ugly URls and also to handle ALL urls everywhere.

Can we instead have an effect like:

React.useEffect(() => {
   next.clearRouterCacheSomehow();
}, [cacheContextKey]);

?

[conico974]

One thing with it right now, for unsigned claims using a <Link> with prefetch will cause trouble because the cookies would be set before actually clicking on it.
It could be interesting to provide a custom button for that so that we can more easily control that