chore: make the license field PEP639 compatible

[gruebel]

This PR

• relates to chore: make the license field PEP639 compatible python-sdk#548

[gemini-code-assist]

Summary of Changes

Hello @gruebel, 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 enhancing the consistency and accuracy of license declarations within the project's Python packages. By modifying the pyproject.toml files, it ensures that the license information adheres to the PEP 639 standard, improving metadata quality and simplifying license identification for package consumers and tools.

Highlights

• PEP 639 Compliance: The license field in pyproject.toml files has been updated to be compliant with PEP 639, standardizing how license information is declared.
• License Declaration Update: The license = { file = "LICENSE" } entry has been replaced with license = "Apache-2.0" and a new license-files = ["LICENSE"] entry has been added.
• Classifier Removal: The redundant License :: OSI Approved :: Apache Software License classifier has been removed from the pyproject.toml files.
• Affected Files: These changes have been applied across multiple pyproject.toml files within the hooks and providers directories, specifically for openfeature-hooks-opentelemetry, openfeature-provider-env-var, openfeature-provider-flagd, openfeature-provider-flipt, and openfeature-provider-ofrep.

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 94.56%. Comparing base (8434aab) to head (fbc9e9d).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #317   +/-   ##
=======================================
  Coverage   94.56%   94.56%           
=======================================
  Files          22       22           
  Lines        1068     1068           
=======================================
  Hits         1010     1010           
  Misses         58       58           

☔ 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 updates the pyproject.toml files across several packages to use the modern, PEP 639-compatible format for specifying the license, using an SPDX identifier. This is a good step towards standardization. My review focuses on ensuring that this change doesn't unintentionally remove important package metadata. For packages built with uv_build, I've noted that the License classifier should be retained for now, as uv_build does not yet automatically add it based on the SPDX identifier. For the package using hatchling, the change is correct as hatchling does perform this automatic addition.