chore(main): release 0.2.0

[github-actions]

🤖 I have created a release beep boop

0.2.0 (2024-03-09)

⚠ BREAKING CHANGES

• Implement Requirement 1.1.3 (#80)
• rename top-level lib folder to open_feature (#90)
• Drop Ruby 2.7 and 3.0, add Ruby 3.3 (#91)

Features

• adds InMemoryProvider (#102) (25680a4)
• Implement Requirement 1.1.2 (#78) (8cea7d0)
• Implement Requirement 1.1.3 (#80) (bc65e7a)
• Updates to Provider module in preparation for InMemoryProvider (#99) (2d89570)

Miscellaneous Chores

• Drop Ruby 2.7 and 3.0, add Ruby 3.3 (#91) (51cd3a1)
• rename top-level lib folder to open_feature (#90) (e1a9a01)

---

This PR was generated with Release Please. See documentation.

[maxveldink]

@open-feature/sdk-ruby-maintainers @beeme1mr
I'd like to release this version this weekend/early next week if possible. We'd like to start pulling it in to our downstream projects.

[maxveldink]

@beeme1mr Is there a reason the CI step didn't kick off? Do we need a different PAT to kick-off workflows on PRs created by an Action?

[beeme1mr]

@maxveldink Sometimes you need to close and reopen the PR to trigger the CI. I think it has something to do with Release Please using a GitHub token instead of a PAT but I'm not 100% sure.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.39%. Comparing base (bc65e7a) to head (ab1459a).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #104   +/-   ##
=======================================
  Coverage   99.39%   99.39%           
=======================================
  Files          12       12           
  Lines         166      166           
=======================================
  Hits          165      165           
  Misses          1        1           

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

[maxveldink]

https://github.com/google-github-actions/release-please-action?tab=readme-ov-file#github-credentials

By default, Release Please uses the built-in GITHUB_TOKEN secret. However, all resources created by release-please (release tag or release pull request) will not trigger future GitHub actions workflows, and workflows normally triggered by release.created events will also not run. From GitHub's docs:

When you use the repository's GITHUB_TOKEN to perform tasks, events triggered by the GITHUB_TOKEN will not create a new workflow run. This prevents you from accidentally creating recursive workflow runs.

You will want to configure a GitHub Actions secret with a Personal Access Token if you want GitHub Actions CI checks to run on Release Please PRs.

Annoyingly, we would need to set someone's own PAT in order to auto-trigger that behavior.

[github-actions]

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