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

fix(deps): update module github.com/open-feature/flagd/core to v0.10.2 #567

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 14, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/open-feature/flagd/core v0.9.1 -> v0.10.2 age adoption passing confidence

Release Notes

open-feature/flagd (github.com/open-feature/flagd/core)

v0.10.2: flagd: v0.10.2

✨ New Features
🧹 Chore

v0.10.1: flagd: v0.10.1

🐛 Bug Fixes
  • deps: update module github.com/open-feature/flagd/core to v0.9.0 (#​1281) (3cfb052)
✨ New Features

v0.10.0: flagd: v0.10.0

⚠ BREAKING CHANGES
  • allow custom seed when using targetingKey override for fractional op (#​1266)
    • This is a breaking change only to the extent that it changes the assignment of evaluated flag values.
      Previously, flagd's fractional op would internally concatenate any specified bucketing property with the flag-key.
      This improved apparent "randomness" by reducing the chances that users were assigned a bucket of the same ordinality across multiple flags.
      However, sometimes it's desireable to have such predictibility, so now flagd will use the bucketing value as is.
      If you are specifying a bucketing value in a fractional rule, and want to maintain the previous assignments, you can do this concatenation manually:
      { "var": "user.name" } => {"cat": [{ "var": "$flagd.flagKey" }, { "var": "user.name" }]}.
      This will result in the same assignment as before.
      Please note, that if you do not specify a bucketing key at all (the shorthand version of the fractional op), flagd still uses a concatentation of the flag-key and targetingKey as before; this behavior has not changed.
🐛 Bug Fixes
  • deps: update module github.com/open-feature/flagd/core to v0.8.2 (#​1255) (9005089)
✨ New Features
  • allow custom seed when using targetingKey override for fractional op (#​1266) (f62bc72)
🧹 Chore

v0.9.2: flagd: v0.9.2

✨ New Features

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link
Contributor Author

renovate bot commented Aug 14, 2024

ℹ Artifact update notice

File name: providers/flagd/go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 12 additional dependencies were updated

Details:

Package Change
github.com/go-logr/logr v1.4.1 -> v1.4.2
golang.org/x/exp v0.0.0-20240416160154-fe59bbe5cc7f -> v0.0.0-20240506185415-9bf2ced13842
google.golang.org/grpc v1.64.1 -> v1.65.0
github.com/diegoholiveira/jsonlogic/v3 v3.5.2 -> v3.5.3
github.com/open-feature/flagd-schemas v0.2.9-0.20240408192555-ea4f119d2bd7 -> v0.2.9-0.20240708163558-2aa89b314322
go.opentelemetry.io/otel v1.25.0 -> v1.28.0
go.opentelemetry.io/otel/metric v1.25.0 -> v1.28.0
go.opentelemetry.io/otel/trace v1.25.0 -> v1.28.0
golang.org/x/mod v0.17.0 -> v0.20.0
golang.org/x/sys v0.21.0 -> v0.23.0
golang.org/x/text v0.16.0 -> v0.17.0
google.golang.org/genproto/googleapis/rpc v0.0.0-20240415180920-8c6c420018be -> v0.0.0-20240701130421-f6361c86f094

@renovate renovate bot requested a review from a team as a code owner August 14, 2024 20:16
@renovate renovate bot force-pushed the renovate/github.com-open-feature-flagd-core-0.x branch 2 times, most recently from 267dcf4 to f754613 Compare August 20, 2024 02:42
@renovate renovate bot force-pushed the renovate/github.com-open-feature-flagd-core-0.x branch from f754613 to 1fed2ca Compare August 22, 2024 20:32
@renovate renovate bot changed the title fix(deps): update module github.com/open-feature/flagd/core to v0.10.1 fix(deps): update module github.com/open-feature/flagd/core to v0.10.2 Aug 22, 2024
@renovate renovate bot force-pushed the renovate/github.com-open-feature-flagd-core-0.x branch 2 times, most recently from 3cc566a to 656499d Compare August 27, 2024 10:58
@renovate renovate bot force-pushed the renovate/github.com-open-feature-flagd-core-0.x branch 4 times, most recently from 585a532 to 1672a0c Compare September 10, 2024 19:01
@renovate renovate bot force-pushed the renovate/github.com-open-feature-flagd-core-0.x branch from 1672a0c to 15d8575 Compare September 18, 2024 14:58
@renovate renovate bot force-pushed the renovate/github.com-open-feature-flagd-core-0.x branch from 15d8575 to 82d0cd6 Compare September 19, 2024 14:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants