chore(main): release providers/flagd 0.1.1

[github-actions[bot]]

:robot: I have created a release beep boop

0.1.1 (2024-02-22)

🐛 Bug Fixes

• remove setup from flagd tests (#39) (85661ff)

---

This PR was generated with Release Please. See documentation.

[thisthat]

This is needed by the OTel Demo: https://github.com/open-telemetry/opentelemetry-demo/pull/1388#issuecomment-1955255713

[thisthat]

In theory, we just need to merge this PR and the automation will do everything. However, I never used pypa/gh-action-pypi-publish@release/v1, so let's see and hope for the best 🤞

[gruebel]

As long as @beeme1mr setup everything in pypi it should work 😄

[beeme1mr]

As long as @beeme1mr setup everything in pypi it should work 😄

The pressure is on... let me quickly double-check before we merge!

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (d8e10c7) 90.55% compared to head (c58cec9) 90.55%. Report is 1 commits behind head on main.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #40 +/- ## ======================================= Coverage 90.55% 90.55% ======================================= Files 8 8 Lines 180 180 ======================================= Hits 163 163 Misses 17 17 ``` | [Flag](https://app.codecov.io/gh/open-feature/python-sdk-contrib/pull/40/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=open-feature) | Coverage Δ | | |---|---|---| | [unittests](https://app.codecov.io/gh/open-feature/python-sdk-contrib/pull/40/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=open-feature) | `90.55% <ø> (ø)` | | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=open-feature#carryforward-flags-in-the-pull-request-comment) to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[federicobond]

@beeme1mr All good?

[beeme1mr]

All good?

Let's give it a shot.

[github-actions[bot]]

:robot: Release is at https://github.com/open-feature/python-sdk-contrib/releases/tag/providers/flagd/v0.1.1 :sunflower:

[federicobond]

Job failed: https://github.com/open-feature/python-sdk-contrib/actions/runs/8006817753/job/21869447530

Error: Trusted publishing exchange failure: 
Token request failed: the server refused the request for the following reasons:

* `invalid-publisher`: valid token, but no corresponding publisher (All lookup strategies exhausted)

This generally indicates a trusted publisher configuration error, but could
also indicate an internal error on GitHub or PyPI's part.

The claims rendered below are **for debugging purposes only**. You should **not**
use them to configure a trusted publisher unless they already match your expectations.

If a claim is not present in the claim set, then it is rendered as `MISSING`.

* `sub`: `repo:open-feature/python-sdk-contrib:environment:release`
* `repository`: `open-feature/python-sdk-contrib`
* `repository_owner`: `open-feature`
* `repository_owner_id`: `99483952`
* `job_workflow_ref`: `open-feature/python-sdk-contrib/.github/workflows/release.yml@refs/heads/main`
* `ref`: `refs/heads/main`