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	685717b
🔍 Latest deploy log	https://app.netlify.com/projects/openfeature/deploys/69577dc0c5c7bb00081ac5c1
😎 Deploy Preview	https://deploy-preview-1325--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 primarily updates the 'Last updated at' timestamps within various SDK documentation files, a common outcome of an automated documentation generation workflow. Additionally, it addresses a minor but important correction in the React SDK documentation, ensuring the correct property name is used for the FeatureFlag component.

Highlights

• Automated Documentation Updates: The pull request includes routine updates to the 'Last updated at' timestamps across numerous SDK documentation files, automatically generated by a GitHub workflow.
• React SDK Documentation Correction: A specific correction was made in the React SDK documentation, changing the FeatureFlag component property from match to matchValue for improved clarity and consistency.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 SDK README files. The changes primarily involve updating the 'Last updated at' timestamps across multiple documentation files. A notable correction has been made in docs/reference/sdks/client/web/react.mdx, where an incorrect match prop in a code example has been changed to matchValue, aligning it with the component's API. The changes are correct and improve the documentation's accuracy. I have no further comments or suggestions.