Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(main): release 0.4.2 #238

Merged
merged 1 commit into from
Feb 6, 2024
Merged

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Nov 14, 2023

🤖 I have created a release beep boop

0.4.2 (2024-02-06)

Features

  • add FeatureProvider protocol (#268) (caa7f36)
  • improve logging setup (#261) (ccbff2c)
  • make return value not optional in provider API functions (#270) (cb1677b)
  • make specific fields in HookContext immutable (#266) (3b89760)

Bug Fixes

  • Allow string values for FlagEvaluationDetails.reason and FlagResolutionDetails.reason (#264) (5ef6ca1)

Documentation


This PR was generated with Release Please. See documentation.

@github-actions github-actions bot force-pushed the release-please--branches--main branch 2 times, most recently from 90ed5e3 to 233b5d7 Compare December 6, 2023 16:45
@github-actions github-actions bot force-pushed the release-please--branches--main branch 3 times, most recently from aa9a486 to 5e86f1f Compare December 14, 2023 23:22
@github-actions github-actions bot force-pushed the release-please--branches--main branch 2 times, most recently from 312bb71 to e6dd084 Compare December 23, 2023 03:26
@github-actions github-actions bot force-pushed the release-please--branches--main branch 2 times, most recently from 8a885e2 to 956d378 Compare December 31, 2023 15:18
@github-actions github-actions bot force-pushed the release-please--branches--main branch 5 times, most recently from 0098baf to 1c1e35c Compare January 11, 2024 21:13
@github-actions github-actions bot force-pushed the release-please--branches--main branch 2 times, most recently from f276249 to 5f12a1f Compare January 17, 2024 21:27
@github-actions github-actions bot force-pushed the release-please--branches--main branch 5 times, most recently from 0061b06 to 0c3adeb Compare January 29, 2024 16:16
@federicobond
Copy link
Member

@beeme1mr should we mark Logging as implemented in the README feature table with the current changes?

@beeme1mr
Copy link
Member

should we mark Logging as implemented in the README feature table with the current changes?

Sure

@github-actions github-actions bot force-pushed the release-please--branches--main branch 2 times, most recently from 7f0a528 to 304ef7a Compare February 6, 2024 04:49
@beeme1mr beeme1mr closed this Feb 6, 2024
@beeme1mr beeme1mr reopened this Feb 6, 2024
Copy link

codecov bot commented Feb 6, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

❗ No coverage uploaded for pull request base (main@cb1677b). Click here to learn what that means.

❗ Current head 304ef7a differs from pull request most recent head 3e2f5d1. Consider uploading reports for the commit 3e2f5d1 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #238   +/-   ##
=======================================
  Coverage        ?   94.02%           
=======================================
  Files           ?       17           
  Lines           ?      452           
  Branches        ?        0           
=======================================
  Hits            ?      425           
  Misses          ?       27           
  Partials        ?        0           
Flag Coverage Δ
unittests 94.02% <ø> (?)

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.

@github-actions github-actions bot force-pushed the release-please--branches--main branch from 304ef7a to 3e2f5d1 Compare February 6, 2024 14:16
@keelerm84
Copy link
Contributor

Do you have a time frame in mind when this might be released? I have some work dependent on these changes being released and want to set reasonable expectations for when it might be completed.

Thank you!

@beeme1mr beeme1mr closed this Feb 6, 2024
@beeme1mr beeme1mr reopened this Feb 6, 2024
@beeme1mr beeme1mr merged commit 522d425 into main Feb 6, 2024
@beeme1mr beeme1mr deleted the release-please--branches--main branch February 6, 2024 15:37
Copy link
Contributor Author

github-actions bot commented Feb 6, 2024

@beeme1mr
Copy link
Member

beeme1mr commented Feb 6, 2024

Hey @keelerm84, sorry for the delay. I've released the update.

@keelerm84
Copy link
Contributor

Thank you so much. I appreciate you cutting that release!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants