Closed renovate[bot] closed 1 week ago
In order to perform the update(s) described in the table above, Renovate ran the go get
command, which resulted in the following additional change(s):
go
directive was updated for compatibility reasonsDetails:
Package | Change |
---|---|
go |
1.22.3 -> 1.23.2 |
buf.build/gen/go/open-feature/flagd/grpc/go |
v1.5.1-20240215170432-1e611e2999cc.1 -> v1.5.1-20240906125204-0a6a901b42e8.1 |
buf.build/gen/go/open-feature/flagd/protocolbuffers/go |
v1.34.2-20240906125204-0a6a901b42e8.2 -> v1.35.1-20240906125204-0a6a901b42e8.1 |
github.com/go-logr/logr |
v1.4.1 -> v1.4.2 |
go.uber.org/mock |
v0.4.0 -> v0.5.0 |
golang.org/x/exp |
v0.0.0-20240416160154-fe59bbe5cc7f -> v0.0.0-20240506185415-9bf2ced13842 |
golang.org/x/net |
v0.26.0 -> v0.30.0 |
google.golang.org/grpc |
v1.64.1 -> v1.67.1 |
google.golang.org/protobuf |
v1.34.2 -> v1.35.1 |
sigs.k8s.io/controller-runtime |
v0.17.3 -> v0.19.0 |
github.com/diegoholiveira/jsonlogic/v3 |
v3.5.2 -> v3.5.3 |
github.com/open-feature/flagd-schemas |
v0.2.9-0.20240408192555-ea4f119d2bd7 -> v0.2.9-0.20240708163558-2aa89b314322 |
github.com/rogpeppe/go-internal |
v1.11.0 -> v1.12.0 |
go.opentelemetry.io/otel |
v1.25.0 -> v1.31.0 |
go.opentelemetry.io/otel/metric |
v1.25.0 -> v1.31.0 |
go.opentelemetry.io/otel/trace |
v1.25.0 -> v1.31.0 |
golang.org/x/mod |
v0.17.0 -> v0.21.0 |
golang.org/x/sys |
v0.21.0 -> v0.26.0 |
golang.org/x/text |
v0.16.0 -> v0.19.0 |
google.golang.org/genproto/googleapis/rpc |
v0.0.0-20240415180920-8c6c420018be -> v0.0.0-20241007155032-5fefd90f89a9 |
k8s.io/apimachinery |
v0.29.3 -> v0.31.1 |
k8s.io/klog/v2 |
v2.120.1 -> v2.130.1 |
k8s.io/utils |
v0.0.0-20240310230437-4693a0247e57 -> v0.0.0-20240711033017-18e509b52bc8 |
This PR contains the following updates:
v0.9.1
->v0.10.4
Release Notes
open-feature/flagd (github.com/open-feature/flagd/core)
### [`v0.10.3`](https://redirect.github.com/open-feature/flagd/releases/tag/flagd/v0.10.3): flagd: v0.10.3 ##### 🧹 Chore - adapt telemetry setup error handling ([#1315](https://redirect.github.com/open-feature/flagd/issues/1315)) ([20bcb78](https://redirect.github.com/open-feature/flagd/commit/20bcb78d11dbb16aab2b14d5869bb990a0f7bca5)) - fix unit tests and ensure their execution ([#1316](https://redirect.github.com/open-feature/flagd/issues/1316)) ([25041c0](https://redirect.github.com/open-feature/flagd/commit/25041c016ae84afb01b8eb1e2b693aae3199a6ac)) ### [`v0.10.2`](https://redirect.github.com/open-feature/flagd/releases/tag/flagd/v0.10.2): flagd: v0.10.2 ##### ✨ New Features - Create interface for eval events. ([#1288](https://redirect.github.com/open-feature/flagd/issues/1288)) ([9714215](https://redirect.github.com/open-feature/flagd/commit/9714215cedb0fd28daddf086ce1255ec29b877d4)) ##### 🧹 Chore - bump go deps to latest ([#1307](https://redirect.github.com/open-feature/flagd/issues/1307)) ([004ad08](https://redirect.github.com/open-feature/flagd/commit/004ad083dc01538791148d6233e453d2a3009fcd)) ### [`v0.10.1`](https://redirect.github.com/open-feature/flagd/releases/tag/flagd/v0.10.1): flagd: v0.10.1 ##### 🐛 Bug Fixes - **deps:** update module github.com/open-feature/flagd/core to v0.9.0 ([#1281](https://redirect.github.com/open-feature/flagd/issues/1281)) ([3cfb052](https://redirect.github.com/open-feature/flagd/commit/3cfb0523cc857dd2019d712c621afe81c2b41398)) ##### ✨ New Features - move json logic operator registration to resolver ([#1291](https://redirect.github.com/open-feature/flagd/issues/1291)) ([b473457](https://redirect.github.com/open-feature/flagd/commit/b473457ddff28789fee1eeb6704491b6aa3525e3)) ### [`v0.10.0`](https://redirect.github.com/open-feature/flagd/releases/tag/flagd/v0.10.0): flagd: v0.10.0 ##### ⚠ BREAKING CHANGES - allow custom seed when using targetingKey override for fractional op ([#1266](https://redirect.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://redirect.github.com/open-feature/flagd/issues/1255)) ([9005089](https://redirect.github.com/open-feature/flagd/commit/9005089b3e7c8ec4c1e52b42a59c0c05983647a2)) ##### ✨ New Features - allow custom seed when using targetingKey override for fractional op ([#1266](https://redirect.github.com/open-feature/flagd/issues/1266)) ([f62bc72](https://redirect.github.com/open-feature/flagd/commit/f62bc721e8ebc07e27fbe7b9ca085a8771295d65)) ##### 🧹 Chore - refactor evaluation core ([#1259](https://redirect.github.com/open-feature/flagd/issues/1259)) ([0e6604c](https://redirect.github.com/open-feature/flagd/commit/0e6604cd038dc13d7d40e622523320bf03efbcd0)) - update go deps ([#1279](https://redirect.github.com/open-feature/flagd/issues/1279)) ([219789f](https://redirect.github.com/open-feature/flagd/commit/219789fca8a929d552e4e8d1f6b6d5cd44505f43)) ### [`v0.9.2`](https://redirect.github.com/open-feature/flagd/releases/tag/flagd/v0.9.2): flagd: v0.9.2 ##### ✨ New Features - OFREP support for flagd ([#1247](https://redirect.github.com/open-feature/flagd/issues/1247)) ([9d12fc2](https://redirect.github.com/open-feature/flagd/commit/9d12fc20702a86e8385564659be88f07ad36d9e5))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 is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.