You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The /flags endpoint is ready for big time – with these PRs (#33194, #33032) landing, we now support all of the /decide fields on /flags, which means we can cut over to /flags with no loss of functionality. Putting together a launch checklist:
gonna add the post-launch checklist to a different ticket, since it's not a priority and I'd like to see how things are looking before I look into this too much.
Uh oh!
There was an error while loading. Please reload this page.
The
/flags
endpoint is ready for big time – with these PRs (#33194, #33032) landing, we now support all of the/decide
fields on/flags
, which means we can cut over to/flags
with no loss of functionality. Putting together a launch checklist:Infra
posthog-feature-flags
service in US and EU to 140 HPA per datacenter #33327/flags
service #33264SDKs
/flags
to posthog-js feat(flags): replace/decide
with/flags&config=true
posthog-js#2000. NB: make sure I'm hashing the token rollout initially so that it only goes to a subset of traffic since JS changes often propagate immediately./flags
to android use /flags instead of /decide posthog-android#245/flags
to iOS chore(flags): use new/flags
endpoint instead of/decide
posthog-ios#345Docs
/decide
in our docs to talk about/flags
or/flags&config=true
#33329The text was updated successfully, but these errors were encountered: