chore: release main

[github-actions]

🤖 I have created a release beep boop

flagd: 0.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: 0.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: 0.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)

---

This PR was generated with Release Please. See documentation.

[netlify]

✅ Deploy Preview for polite-licorice-3db33c canceled.

Name	Link
🔨 Latest commit	1846648
🔍 Latest deploy log	https://app.netlify.com/sites/polite-licorice-3db33c/deploys/6616be705f18720008e1a04b

[Kavindu-Dodan]

we could wait for #1266 to merge

[toddbaert]

I believe the "breaking changes" here only amount to different assignments during fractional evaluation, which can also be worked-around.

If this is the case, I will make some changes to explicitly discuss this in the release notes before we release.

[github-actions]

🤖 Release is at https://github.com/open-feature/flagd/releases/tag/flagd/v0.10.0 🌻

[github-actions]

🤖 Release is at https://github.com/open-feature/flagd/releases/tag/flagd-proxy/v0.6.0 🌻

[github-actions]

🤖 Release is at https://github.com/open-feature/flagd/releases/tag/core/v0.9.0 🌻