chore: update sdk readmes

[openfeaturebot]

The PR was automatically generated via the update-sdk-docs GitHub workflow.

[netlify]

✅ Deploy Preview for openfeature ready!

Name	Link
🔨 Latest commit	b2d466c
🔍 Latest deploy log	https://app.netlify.com/projects/openfeature/deploys/6a477cc79a65120008d37a76
😎 Deploy Preview	https://deploy-preview-1404--openfeature.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Warning

Review limit reached

@openfeaturebot, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 22 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 904aef31-ecda-42dc-a425-134b15e6c7cc

📥 Commits

Reviewing files that changed from the base of the PR and between daa8f59 and b2d466c.

📒 Files selected for processing (16)

• docs/reference/sdks/client/kotlin.mdx
• docs/reference/sdks/client/swift.mdx
• docs/reference/sdks/client/web/angular.mdx
• docs/reference/sdks/client/web/index.mdx
• docs/reference/sdks/client/web/react.mdx
• docs/reference/sdks/server/cpp.mdx
• docs/reference/sdks/server/dart.mdx
• docs/reference/sdks/server/dotnet.mdx
• docs/reference/sdks/server/go.mdx
• docs/reference/sdks/server/java.mdx
• docs/reference/sdks/server/javascript/index.mdx
• docs/reference/sdks/server/javascript/nestjs.mdx
• docs/reference/sdks/server/php.mdx
• docs/reference/sdks/server/python.mdx
• docs/reference/sdks/server/ruby.mdx
• docs/reference/sdks/server/rust.mdx

📝 Walkthrough

Walkthrough

This PR updates the autogenerated "Last updated" timestamp in the header comment of sixteen SDK reference documentation pages (client and server SDKs), changing dates from Jul 01, 2026 to Jul 02, 2026. No content, code, or logic changes were made.

Changes

SDK reference docs timestamp updates

Layer / File(s)

Summary

Refresh generated timestamp headers docs/reference/sdks/client/kotlin.mdx, docs/reference/sdks/client/swift.mdx, docs/reference/sdks/client/web/*, docs/reference/sdks/server/cpp.mdx, docs/reference/sdks/server/dart.mdx, docs/reference/sdks/server/dotnet.mdx, docs/reference/sdks/server/go.mdx, docs/reference/sdks/server/java.mdx, docs/reference/sdks/server/javascript/*, docs/reference/sdks/server/php.mdx, docs/reference/sdks/server/python.mdx, docs/reference/sdks/server/ruby.mdx, docs/reference/sdks/server/rust.mdx

The generated "Last updated at" timestamp in each page's header comment was changed from Jul 01, 2026 to Jul 02, 2026.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• open-feature/openfeature.dev#1394: Both PRs update the same autogenerated "Last updated" header timestamp across the same set of docs/reference/sdks/**.mdx files.

Suggested reviewers: beeme1mr

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is related to the change, though it is a bit imprecise because the diff updates SDK reference docs timestamps rather than README files.
Description check	✅ Passed	The description is on-topic and matches the automated docs-update workflow that produced these changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}