chore(main): release 0.9.0

[openfeaturebot]

🤖 I have created a release beep boop

0.9.0 (2026-04-17)

⚠ BREAKING CHANGES

• remove deprecated openfeature.provider.provider module (#558)
• Drop python 3.9 support (#554)

🐛 Bug Fixes

• correctly reset api state on shutdown (#589) (eaa195b)
• Prevent providers from being initialized multiple times (45f7fd1)
• Prevent providers from being shutdown multiple times (45f7fd1)
• replace project.scripts with poethepoet (#563) (05382aa)
• validate domain is present when calling set_provider on registry (#561) (9fc6121)

✨ New Features

• add logging hook (#577) (ae59756)
• Drop python 3.9 support (04106f5)
• Implement tracking (#564) (b81ee21)

🧹 Chore

• add pyproject-fmt hook (#578) (fafd902)
• deps: pin pypa/gh-action-pypi-publish action to ed0c539 (#582) (c7ada5a)
• deps: update actions/checkout digest to de0fac2 (#572) (e9dfeac)
• deps: update astral-sh/setup-uv digest to 37802ad (#581) (ddb8fd1)
• deps: update astral-sh/setup-uv digest to e06108d (#573) (c35a1e5)
• deps: update dependency uv_build to ~=0.10.0 (#571) (a6366e2)
• deps: update github/codeql-action digest to 0d579ff (#574) (0696033)
• deps: update github/codeql-action digest to c10b806 (#583) (9478ea0)
• deps: update pre-commit hook astral-sh/ruff-pre-commit to v0.15.6 (#575) (d0d7d8f)
• deps: update pre-commit hook pre-commit/mirrors-mypy to v1.19.1 (#576) (ade3870)
• deps: update pre-commit hook pre-commit/mirrors-mypy to v1.20.0 (#588) (398d140)
• Drop python 3.9 support (#554) (04106f5)
• replace pre-commit with prek (#580) (d1e0cde)
• update pytest to v9 (#559) (71ebb9f)
• update uv to 0.11 and relax version requirement (#587) (7d9229f)

📚 Documentation

• fix inaccuracies in README code examples (#592) (17d62c4)

🔄 Refactoring

• Delete provider status instead of marking as NOT_READY (45f7fd1)
• remove deprecated openfeature.provider.provider module (#558) (7c27c7a)

---

This PR was generated with Release Please. See documentation.

[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 is an automated release for version 0.9.0 of the OpenFeature Python SDK. Its primary purpose is to update all relevant project metadata and documentation to reflect the new version number and to formally announce the discontinuation of support for Python 3.9, ensuring the project aligns with current Python ecosystem standards.

Highlights

• Version Release: This pull request officially releases version 0.9.0 of the OpenFeature Python SDK.
• Breaking Change: Support for Python 3.9 has been discontinued, which is a breaking change for users relying on that version.
• Automated Updates: Various project files, including the changelog, README, and version declarations, have been automatically updated to reflect the new 0.9.0 version.

🧠 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. ↩

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.35%. Comparing base (eaa195b) to head (62569f0).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #555   +/-   ##
=======================================
  Coverage   98.35%   98.35%           
=======================================
  Files          45       45           
  Lines        2183     2183           
=======================================
  Hits         2147     2147           
  Misses         36       36           

Flag	Coverage Δ
unittests	98.35% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[gemini-code-assist]

Code Review

This pull request is an automated release for version 0.9.0, which primarily includes dropping support for Python 3.9. The changes are mostly version bumps in various files. I've suggested a small cleanup in the CHANGELOG.md to improve its readability. Additionally, while not part of this PR's changes, I noticed that tool.ruff.target-version in pyproject.toml is still set to py39, which is inconsistent with dropping Python 3.9 support. This should probably be updated to py310 in a follow-up PR.

[Zaimwa9]

@open-feature/sdk-python-maintainers, is there an ETA on this release? We have pre-emptively implemented the tracking API in the flagsmith provider that is included in this release

[gruebel]

I would like to get in my PR #589 and then I would be fine with cutting a release.

[openfeaturebot]

🤖 Release is at https://github.com/open-feature/python-sdk/releases/tag/v0.9.0 🌻