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(deps): update open-feature/flagd #670

Merged
merged 2 commits into from
Jun 6, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 6, 2024

Mend Renovate

This PR contains the following updates:

Package Type Update Change
ghcr.io/open-feature/flagd minor v0.9.0 -> v0.10.3
ghcr.io/open-feature/flagd patch v0.10.1 -> v0.10.3
ghcr.io/open-feature/flagd-proxy minor v0.5.0 -> v0.6.2
github.com/open-feature/flagd-schemas require digest ea4f119 -> 61523e5
open-feature/flagd/flagd patch ghcr.io/open-feature/flagd:v0.10.1 -> v0.10.3
open-feature/flagd/flagd minor v0.9.0 -> v0.10.3
open-feature/flagd/flagd patch v0.10.1 -> v0.10.3
open-feature/flagd/flagd-proxy minor v0.5.0 -> v0.6.2

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

open-feature/flagd (ghcr.io/open-feature/flagd)

v0.10.3: flagd: v0.10.3

🧹 Chore

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

v0.9.1: flagd: v0.9.1

🐛 Bug Fixes
✨ New Features
🧹 Chore

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 becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot requested a review from a team as a code owner June 6, 2024 15:40
@renovate renovate bot added the renovate label Jun 6, 2024
@toddbaert toddbaert self-requested a review June 6, 2024 16:22
@renovate renovate bot force-pushed the renovate/open-featureflagd branch 2 times, most recently from 7410083 to 19c9892 Compare June 6, 2024 17:03
@renovate renovate bot force-pushed the renovate/open-featureflagd branch from 19c9892 to cb947c3 Compare June 6, 2024 18:13
Signed-off-by: Todd Baert <[email protected]>
@Kavindu-Dodan Kavindu-Dodan merged commit 1174a1b into main Jun 6, 2024
17 checks passed
This was referenced Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants