v4.0.0 - Breaking changes to Redis Data Store, nginx logs

Summary

Major/Breaking changes

• Removed support for writing to a deprecated keyspace in Redis Data Store
  • How to upgrade: Please use a 2025 or newer release of Server Core to ensure continued function of Data Store. See: More instructions for configuring Data Store
• Fixed a bug where REDIS_ENTERPRISE_PASSWORD was not properly formatted in the Redis connection URL for Data Store. If supplied, users would have to prefix the REDIS_ENTERPRISE_PASSWORD with a colon (:) to resolve the formatting bug.
  • How to upgrade: If you are currently supplying a value for REDIS_ENTERPRISE_PASSWORD and are prefixing the password with a colon (:), remove the colon.
• Nginx error logs are now written to /dev/stderr instead of /var/log/nginx/error.log
  • How to upgrade: If you are collecting nginx logs, point your log collector to the new location.

Minor changes

• We introduced a new key format for Redis Data Store, meant to be more human-readable. If double_write_cache_for_legacy_key is set to false, then the forward proxy will only write to this new key. See: More instructions for configuring Data Store
• Nginx no longer requires root-level permissions to run
• Fixed bug causing get_id_list requests to incorrectly result in HTTP Unauthorized

More instructions for configuring Data Store

We introduced a new key format for Redis Data Store, meant to be more human-readable. If double_write_cache_for_legacy_key is set to false, then the forward proxy will only write to this new key.

We recommend that double_write_cache_for_legacy_key is set to true if using Data Store. This will configure the forward proxy to write an additional copy of data to the "legacy" location required by most SDKs as of EOY 2025.

https://hub.docker.com/repository/docker/statsig/statsig-forward-proxy/tags/stable-4.0.0/sha256:2a8abfa578122090679ba89f9b19db6660a94fe4123fe27ef1b93db206d6e57b