docs: update install version and links

[beeme1mr]

Prepping the readme for inclusion on openfeature.dev

[gemini-code-assist]

Summary of Changes

Hello @beeme1mr, 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 focuses on updating the README.md file to ensure its accuracy and prepare it for publication on openfeature.dev. Key changes include updating the Dart SDK installation version and correcting a link to the OpenFeature provider ecosystem.

Highlights

• Documentation Update: The README.md file has been updated to reflect the latest version of the openfeature_dart_server_sdk in the installation instructions.
• Link Correction: The link to the OpenFeature provider ecosystem has been corrected to ensure it properly filters providers by technology.
• Release Automation Markers: Adjustments were made to x-release-please markers within the README.md to improve compatibility with automated release processes.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 updates the README.md file to reflect the new version v0.0.10 and adds release-please comment blocks to automate future version updates. The changes are generally good, but I found a small issue with a malformed URL that should be corrected.

[ABC2015]

@beeme1mr Let me know if this is ready to merge into main when you have a chance.

[beeme1mr]

@beeme1mr Let me know if this is ready to merge into main when you have a chance.

It looks like the CI process is different than what I'm used to. Will it cause any issues if I force this change through?

[ABC2015]

@beeme1mr I just pushed and updated the main branch - if you pull the latest changes in that one first - it should be ok to push directly - we'll then pull back your changes directly in our development branch so it's synched.

[ABC2015]

@beeme1mr if you pull the current main branch should be ok to merge as there are some new updates we just pushed.