build(deps): bump github.com/open-feature/go-sdk-contrib/providers/go-feature-flag from 0.1.38 to 0.2.0
Bumps github.com/open-feature/go-sdk-contrib/providers/go-feature-flag from 0.1.38 to 0.2.0.
Release notes
Sourced from github.com/open-feature/go-sdk-contrib/providers/go-feature-flag's releases.
providers/configcat: v0.2.0
0.2.0 (2023-08-02)
โ BREAKING CHANGES
- update minimum go version (#292)
๐ Bug Fixes
๐งน Chore
providers/flagd: v0.2.0
0.2.0 (2024-04-11)
โ BREAKING CHANGES
- use new eval/sync protos (requires flagd v0.7.3+) (#451)
๐ Bug Fixes
- deps: update golang.org/x/exp digest to 814bf88 (#453) (80cdaaa)
- deps: update golang.org/x/exp digest to a685a6e (#479) (e55c610)
- deps: update module buf.build/gen/go/open-feature/flagd/protocolbuffers/go to v1.33.0-20240215170432-1e611e2999cc.1 (#468) (aebf9d0)
- deps: update module github.com/open-feature/flagd/core to v0.8.1 (#483) (4c3f005)
- deps: update module github.com/open-feature/go-sdk-contrib/tests/flagd to v1.4.1 (#484) (6f4e7b7)
- deps: update module go.uber.org/mock to v0.4.0 (#425) (91f70c0)
- deps: update module google.golang.org/grpc to v1.62.1 (#430) (c20613c)
- deps: update module sigs.k8s.io/controller-runtime to v0.17.2 (#434) (acaf0cb)
โจ New Features
- update to latest flagd core release (#495) (4034850)
- use new eval/sync protos (requires flagd v0.7.3+) (#451) (308bba1)
๐งน Chore
... (truncated)
Commits
1f8276echore(main): release providers/flagd 0.2.0 (#448)4034850feat: update to latest flagd core release (#495)0ac382echore(providers/flipt): update README with correct provider import statement ...908a22dchore(main): release providers/go-feature-flag 0.1.34 (#471)9a7684dchore(main): release providers/ofrep 0.1.1 (#494)a1cb699feat: introduce OFREP provider (#477)eb092d4fix(deps): update module github.com/thomaspoignant/go-feature-flag to v1.24.2...450b2affix(deps): update module github.com/flagsmith/flagsmith-go-client/v3 to v3.4....6f4e7b7fix(deps): update module github.com/open-feature/go-sdk-contrib/tests/flagd t...aebf9d0fix(deps): update module buf.build/gen/go/open-feature/flagd/protocolbuffers/...- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency -
@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Minder Vulnerability Report โ
Minder analyzed this PR and found it does not add any new vulnerable dependencies.
Vulnerability scan of
57f1b0cd:
- ๐ vulnerable packages:
0- ๐ fixes available for:
0
@dependabot recreate
It looks like this change fixes it, but I'm not sure whether it's the only way to fix it. What do you folks think about it?
diff --git i/internal/flags/flags.go w/internal/flags/flags.go
index 7067a0acfc5f..e75ef28ce878 100644
--- i/internal/flags/flags.go
+++ w/internal/flags/flags.go
@@ -19,7 +19,7 @@ package flags
import (
"context"
- ofprovider "github.com/open-feature/go-sdk-contrib/providers/go-feature-flag/pkg"
+ ofprovider "github.com/open-feature/go-sdk-contrib/providers/go-feature-flag-in-process/pkg"
"github.com/open-feature/go-sdk/openfeature"
"github.com/rs/zerolog"
gofeature "github.com/thomaspoignant/go-feature-flag"
It looks like this change fixes it, but I'm not sure whether it's the only way to fix it. What do you folks think about it?
diff --git i/internal/flags/flags.go w/internal/flags/flags.go index 7067a0acfc5f..e75ef28ce878 100644 --- i/internal/flags/flags.go +++ w/internal/flags/flags.go @@ -19,7 +19,7 @@ package flags import ( "context" - ofprovider "github.com/open-feature/go-sdk-contrib/providers/go-feature-flag/pkg" + ofprovider "github.com/open-feature/go-sdk-contrib/providers/go-feature-flag-in-process/pkg" "github.com/open-feature/go-sdk/openfeature" "github.com/rs/zerolog" gofeature "github.com/thomaspoignant/go-feature-flag"
I think we should do that for now. We may eventually want to switch to go-feature-flag to have consistent flags across the frontend and backend, but that's a future goal.
From their docs:
go-feature-flag: Ideal for multi-language environments using the GO Feature Flag relay proxy. This provider offers a lightweight integration with minimal dependencies, ensuring consistency with other language-specific providers. go-feature-flag-in-process: Best suited for Go-only applications that prefer a direct integration without the overhead of a separate service.
Closed via #3590
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it.