forked from open-feature/open-feature-operator
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update open-feature/flagd to v0.11.1 #8
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/open-featureflagd
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
84b2bf3
to
6458eed
Compare
6458eed
to
f913d7d
Compare
f913d7d
to
fa81ac1
Compare
fa81ac1
to
6125566
Compare
6125566
to
a00720d
Compare
a00720d
to
7782ac5
Compare
7782ac5
to
4c4efb0
Compare
4c4efb0
to
86ffb3f
Compare
86ffb3f
to
eff3f8b
Compare
eff3f8b
to
e528f62
Compare
e528f62
to
90536b7
Compare
90536b7
to
0ee3a2f
Compare
0ee3a2f
to
817b258
Compare
817b258
to
c04068f
Compare
c04068f
to
0da5456
Compare
0da5456
to
767f225
Compare
767f225
to
a79958c
Compare
a79958c
to
78fb9b9
Compare
78fb9b9
to
353b86a
Compare
353b86a
to
bf8697e
Compare
bf8697e
to
2061fcb
Compare
2061fcb
to
ce42eab
Compare
ce42eab
to
c39e6b1
Compare
c39e6b1
to
3f8fe4d
Compare
3f8fe4d
to
e68b9cc
Compare
e68b9cc
to
12c7474
Compare
12c7474
to
a4a1f9c
Compare
a4a1f9c
to
2f39559
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.4.4
->v0.11.1
v0.4.4
->v0.11.1
Release Notes
open-feature/flagd (ghcr.io/open-feature/flagd)
v0.11.1
: flagd: v0.11.1🐛 Bug Fixes
v0.11.0
: flagd: v0.11.0⚠ BREAKING CHANGES
🐛 Bug Fixes
✨ New Features
FLAGD_DEBUG
/--debug
/-x
(#1326) (298bd36)v0.10.3
: flagd: v0.10.3🧹 Chore
v0.10.2
: flagd: v0.10.2✨ New Features
🧹 Chore
v0.10.1
: flagd: v0.10.1🐛 Bug Fixes
✨ New Features
v0.10.0
: flagd: v0.10.0⚠ BREAKING CHANGES
Previously, flagd's
fractional
op 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 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 theflag-key
andtargetingKey
as before; this behavior has not changed.🐛 Bug Fixes
✨ New Features
🧹 Chore
v0.9.2
: flagd: v0.9.2✨ New Features
v0.9.1
: flagd: v0.9.1🐛 Bug Fixes
✨ New Features
🧹 Chore
v0.9.0
: flagd: v0.9.0⚠ BREAKING CHANGES
🐛 Bug Fixes
✨ New Features
🧹 Chore
v0.8.2
: flagd: v0.8.2🐛 Bug Fixes
v0.8.1
: flagd: v0.8.1🐛 Bug Fixes
v0.8.0
: flagd: v0.8.0⚠ BREAKING CHANGES
🐛 Bug Fixes
🧹 Chore
v0.7.2
: flagd: v0.7.2🐛 Bug Fixes
v0.7.1
: flagd: v0.7.1🐛 Bug Fixes
🔄 Refactoring
v0.7.0
: flagd: v0.7.0⚠ BREAKING CHANGES
🐛 Bug Fixes
✨ New Features
🧹 Chore
v0.6.8
: flagd: v0.6.8🐛 Bug Fixes
🧹 Chore
🔄 Refactoring
v0.6.7
: flagd: v0.6.7🐛 Bug Fixes
🧹 Chore
📚 Documentation
v0.6.6
: flagd: v0.6.6🐛 Bug Fixes
🧹 Chore
v0.6.5
: flagd: v0.6.5🐛 Bug Fixes
🧹 Chore
v0.6.4
: flagd-proxy: v0.6.4🐛 Bug Fixes
v0.6.3
: flagd-proxy: v0.6.3🐛 Bug Fixes
v0.6.2
: flagd: v0.6.2🐛 Bug Fixes
v0.6.1
: flagd: v0.6.1🐛 Bug Fixes
v0.6.0
: flagd: v0.6.0⚠ BREAKING CHANGES
🐛 Bug Fixes
🔄 Refactoring
v0.5.2
: flagd-proxy: v0.5.2✨ New Features
v0.5.1
: flagd-proxy: v0.5.1🐛 Bug Fixes
🧹 Chore
v0.5.0
: flagd-proxy: v0.5.0⚠ BREAKING CHANGES
🐛 Bug Fixes
✨ New Features
🧹 Chore
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 becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.