-
Notifications
You must be signed in to change notification settings - Fork 40
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 dev.openfeature.contrib.providers.flagd 0.6.2 #408
chore(main): release dev.openfeature.contrib.providers.flagd 0.6.2 #408
Conversation
71b313e
to
c76dd89
Compare
c0d1c9f
to
b6f3a36
Compare
0424728
to
2dea005
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Release of the initial Java flagd in-process provider.
@toddbaert please check if you agree with the release
@toddbaert proposed to wait till we have the first set of e2e tests based on gherkin testsuite. IMO, this is a good step as we can validate cross-language stability of the provider |
That's probably fine but the flagd readme won't be accurate until we release. |
7c9eed3
to
a4afd6b
Compare
a4afd6b
to
1d48485
Compare
…dev.openfeature.contrib.providers.flagd
…o v2.7.8 (open-feature#408) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
🤖 I have created a release beep boop
0.6.2 (2023-09-19)
Features
Bug Fixes
This PR was generated with Release Please. See documentation.