chore: release main (#1267)

🤖 I have created a release *beep* *boop*
---


<details><summary>flagd: 0.10.0</summary>

##
[0.10.0](flagd/v0.9.2...flagd/v0.10.0)
(2024-04-10)


### ⚠ BREAKING CHANGES

* allow custom seed when using targetingKey override for fractional op
([#1266](#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](#1255))
([9005089](9005089))


### ✨ New Features

* allow custom seed when using targetingKey override for fractional op
([#1266](#1266))
([f62bc72](f62bc72))


### 🧹 Chore

* refactor evaluation core
([#1259](#1259))
([0e6604c](0e6604c))
* update go deps
([#1279](#1279))
([219789f](219789f))
</details>

<details><summary>flagd-proxy: 0.6.0</summary>

##
[0.6.0](flagd-proxy/v0.5.2...flagd-proxy/v0.6.0)
(2024-04-10)


### ⚠ BREAKING CHANGES

* allow custom seed when using targetingKey override for fractional op
([#1266](#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](#1255))
([9005089](9005089))


### ✨ New Features

* allow custom seed when using targetingKey override for fractional op
([#1266](#1266))
([f62bc72](f62bc72))


### 🧹 Chore

* update go deps
([#1279](#1279))
([219789f](219789f))
</details>

<details><summary>core: 0.9.0</summary>

##
[0.9.0](core/v0.8.2...core/v0.9.0)
(2024-04-10)


### ⚠ BREAKING CHANGES

* allow custom seed when using targetingKey override for fractional op
([#1266](#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](#1266))
([f62bc72](f62bc72))


### 🧹 Chore

* refactor evaluation core
([#1259](#1259))
([0e6604c](0e6604c))
* update go deps
([#1279](#1279))
([219789f](219789f))
* wire evaluation ctx to store methods
([#1273](#1273))
([0075932](0075932))
</details>

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

---------

Signed-off-by: OpenFeature Bot <[email protected]>
Signed-off-by: Todd Baert <[email protected]>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Todd Baert <[email protected]>

Author: github-actions[bot]

.release-please-manifest.json

@@ -1,5 +1,5 @@
 {
-  "flagd": "0.9.2",
-  "flagd-proxy": "0.5.2",
-  "core": "0.8.2"
+  "flagd": "0.10.0",
+  "flagd-proxy": "0.6.0",
+  "core": "0.9.0"
 }

core/CHANGELOG.md

@@ -1,5 +1,31 @@
 # Changelog
 
+## [0.9.0](https://github.com/open-feature/flagd/compare/core/v0.8.2...core/v0.9.0) (2024-04-10)
+
+
+### ⚠ BREAKING CHANGES
+
+* allow custom seed when using targetingKey override for fractional op ([#1266](https://github.com/open-feature/flagd/issues/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](https://github.com/open-feature/flagd/issues/1266)) ([f62bc72](https://github.com/open-feature/flagd/commit/f62bc721e8ebc07e27fbe7b9ca085a8771295d65))
+
+
+### 🧹 Chore
+
+* refactor evaluation core ([#1259](https://github.com/open-feature/flagd/issues/1259)) ([0e6604c](https://github.com/open-feature/flagd/commit/0e6604cd038dc13d7d40e622523320bf03efbcd0))
+* update go deps ([#1279](https://github.com/open-feature/flagd/issues/1279)) ([219789f](https://github.com/open-feature/flagd/commit/219789fca8a929d552e4e8d1f6b6d5cd44505f43))
+* wire evaluation ctx to store methods ([#1273](https://github.com/open-feature/flagd/issues/1273)) ([0075932](https://github.com/open-feature/flagd/commit/00759322594f309ca9236156f296805a09f5f9fe))
+
 ## [0.8.2](https://github.com/open-feature/flagd/compare/core/v0.8.1...core/v0.8.2) (2024-03-27)
 
 

flagd-proxy/CHANGELOG.md

@@ -1,5 +1,34 @@
 # Changelog
 
+## [0.6.0](https://github.com/open-feature/flagd/compare/flagd-proxy/v0.5.2...flagd-proxy/v0.6.0) (2024-04-10)
+
+
+### ⚠ BREAKING CHANGES
+
+* allow custom seed when using targetingKey override for fractional op ([#1266](https://github.com/open-feature/flagd/issues/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](https://github.com/open-feature/flagd/issues/1255)) ([9005089](https://github.com/open-feature/flagd/commit/9005089b3e7c8ec4c1e52b42a59c0c05983647a2))
+
+
+### ✨ New Features
+
+* allow custom seed when using targetingKey override for fractional op ([#1266](https://github.com/open-feature/flagd/issues/1266)) ([f62bc72](https://github.com/open-feature/flagd/commit/f62bc721e8ebc07e27fbe7b9ca085a8771295d65))
+
+
+### 🧹 Chore
+
+* update go deps ([#1279](https://github.com/open-feature/flagd/issues/1279)) ([219789f](https://github.com/open-feature/flagd/commit/219789fca8a929d552e4e8d1f6b6d5cd44505f43))
+
 ## [0.5.2](https://github.com/open-feature/flagd/compare/flagd-proxy/v0.5.1...flagd-proxy/v0.5.2) (2024-03-27)
 
 

flagd/CHANGELOG.md

@@ -1,5 +1,35 @@
 # Changelog
 
+## [0.10.0](https://github.com/open-feature/flagd/compare/flagd/v0.9.2...flagd/v0.10.0) (2024-04-10)
+
+
+### ⚠ BREAKING CHANGES
+
+* allow custom seed when using targetingKey override for fractional op ([#1266](https://github.com/open-feature/flagd/issues/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](https://github.com/open-feature/flagd/issues/1255)) ([9005089](https://github.com/open-feature/flagd/commit/9005089b3e7c8ec4c1e52b42a59c0c05983647a2))
+
+
+### ✨ New Features
+
+* allow custom seed when using targetingKey override for fractional op ([#1266](https://github.com/open-feature/flagd/issues/1266)) ([f62bc72](https://github.com/open-feature/flagd/commit/f62bc721e8ebc07e27fbe7b9ca085a8771295d65))
+
+
+### 🧹 Chore
+
+* refactor evaluation core ([#1259](https://github.com/open-feature/flagd/issues/1259)) ([0e6604c](https://github.com/open-feature/flagd/commit/0e6604cd038dc13d7d40e622523320bf03efbcd0))
+* update go deps ([#1279](https://github.com/open-feature/flagd/issues/1279)) ([219789f](https://github.com/open-feature/flagd/commit/219789fca8a929d552e4e8d1f6b6d5cd44505f43))
+
 ## [0.9.2](https://github.com/open-feature/flagd/compare/flagd/v0.9.1...flagd/v0.9.2) (2024-03-27)