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	750c1bc
🔍 Latest deploy log	https://app.netlify.com/projects/openfeature/deploys/692564bcc97adf000823c28e
😎 Deploy Preview	https://deploy-preview-1314--openfeature.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

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

[gemini-code-assist]

Summary of Changes

Hello @openfeaturebot, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request serves to refresh the 'Last updated at' timestamps within numerous SDK documentation files. This automated process ensures that the documentation accurately reflects the most recent generation, maintaining up-to-date information for users across different SDKs.

Highlights

• Automated Documentation Update: This pull request automatically updates the 'Last updated at' timestamps across various SDK documentation files, ensuring the documentation reflects recent changes.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request, generated automatically, updates the 'Last updated at' timestamps across numerous SDK documentation files. While the changes are as expected from the automation, I've raised a medium-severity concern about the practice of including these timestamps. They add noise to the commit history, as every regeneration of the docs creates a diff even if no substantive content has changed. Git history itself is a better tool for tracking modification times. I've suggested removing this timestamp from the generation script to improve repository maintainability.

[gemini-code-assist]

This 'Last updated at' timestamp is redundant, as Git's history already tracks file modification times. Including it causes unnecessary commit noise because every automated documentation build will change this line, even if no substantive content has been updated. This clutters the project's history and makes it harder to track meaningful changes. To improve maintainability, I recommend removing this timestamp from the generation logic in scripts/process-sdk-readmes.ts.