Releases: open-feature/flagd
Releases · open-feature/flagd
flagd: v0.10.1
flagd-proxy: v0.6.1
core: v0.9.1
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'sfractionalop would internally concatenate any specified bucketing property with theflag-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 afractionalrule, 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 thefractionalop), flagd still uses a concatentation of theflag-keyandtargetingKeyas before; this behavior has not changed.
- This is a breaking change only to the extent that it changes the assignment of evaluated flag values.
🐛 Bug Fixes
✨ New Features
🧹 Chore
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'sfractionalop would internally concatenate any specified bucketing property with theflag-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 afractionalrule, 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 thefractionalop), flagd still uses a concatentation of theflag-keyandtargetingKeyas before; this behavior has not changed.
- This is a breaking change only to the extent that it changes the assignment of evaluated flag values.
🐛 Bug Fixes
✨ New Features
🧹 Chore
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'sfractionalop would internally concatenate any specified bucketing property with theflag-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 afractionalrule, 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 thefractionalop), flagd still uses a concatentation of theflag-keyandtargetingKeyas before; this behavior has not changed.
- This is a breaking change only to the extent that it changes the assignment of evaluated flag values.