core: v0.9.3

0.9.3 (2024-06-06)

🐛 Bug Fixes

• fixes store merge when selector is used (#1322) (ed5025d)

🧹 Chore

• adapt telemetry setup error handling (#1315) (20bcb78)

flagd: v0.10.2

0.10.2 (2024-05-10)

✨ New Features

• Create interface for eval events. (#1288) (9714215)

🧹 Chore

• bump go deps to latest (#1307) (004ad08)

flagd-proxy: v0.6.2

0.6.2 (2024-05-10)

🧹 Chore

• bump go deps to latest (#1307) (004ad08)

core: v0.9.2

0.9.2 (2024-05-10)

✨ New Features

• improve error log and add flag disabled handling for ofrep (#1306) (39ae4fe)

🧹 Chore

• bump go deps to latest (#1307) (004ad08)

flagd: v0.10.1

0.10.1 (2024-04-19)

🐛 Bug Fixes

• deps: update module github.com/open-feature/flagd/core to v0.9.0 (#1281) (3cfb052)

✨ New Features

• move json logic operator registration to resolver (#1291) (b473457)

flagd-proxy: v0.6.1

0.6.1 (2024-04-19)

🐛 Bug Fixes

• deps: update module github.com/open-feature/flagd/core to v0.9.0 (#1281) (3cfb052)

core: v0.9.1

0.9.1 (2024-04-19)

🐛 Bug Fixes

• missing/nil custom variables in fractional operator (#1295) (418c5cd)

✨ New Features

• move json logic operator registration to resolver (#1291) (b473457)

flagd: v0.10.0

0.10.0 (2024-04-10)

⚠ 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

• refactor evaluation core (#1259) (0e6604c)
• update go deps (#1279) (219789f)

flagd-proxy: v0.6.0

0.6.0 (2024-04-10)

⚠ 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

• update go deps (#1279) (219789f)

core: v0.9.0

0.9.0 (2024-04-10)

⚠ 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.

✨ New Features

• allow custom seed when using targetingKey override for fractional op (#1266) (f62bc72)

🧹 Chore

• refactor evaluation core (#1259) (0e6604c)
• update go deps (#1279) (219789f)
• wire evaluation ctx to store methods (#1273) (0075932)