posthog-ruby-v3.19.0

Minor Changes

• 15fa092: feat: add a $feature_flag_has_experiment boolean property to $feature_flag_called events when the server explicitly reports the has_experiment field; the property is omitted when the server does not report it (older deployments)

posthog-rails-v3.17.1

Patch Changes

• 5bdf777: fix: also send the request user agent as $raw_user_agent, the standardized property PostHog's server-side classification reads

posthog-ruby-v3.18.0

Minor Changes

• 5c21f66: Add secret_key config option and deprecate personal_api_key.

  secret_key is the new canonical credential for local feature flag evaluation and remote config. It accepts either a Personal API Key (phx_...) or a Project Secret API Key (phs_...). personal_api_key still works as a deprecated alias; when both are supplied, secret_key wins.

posthog-rails-v3.17.0

Minor Changes

• 5c21f66: Add secret_key config option and deprecate personal_api_key.

  secret_key is the new canonical credential for local feature flag evaluation and remote config. It accepts either a Personal API Key (phx_...) or a Project Secret API Key (phs_...). personal_api_key still works as a deprecated alias; when both are supplied, secret_key wins.

posthog-rails-v3.16.1

Patch Changes

• 737acbc: Avoid double-capturing ActiveJob exceptions through the Rails error subscriber.

posthog-ruby-v3.17.0

Minor Changes

• 14d85f7: Use stable project-relative stack frame filename values (relative to Rails.root or Dir.pwd, falling back to the basename outside the project) while preserving the raw path in abs_path; dependency and stdlib frames are detected from RubyGems/stdlib install roots, computed once per stacktrace, so in_app no longer depends on deploy-path substrings.

posthog-ruby-v3.16.0

Minor Changes

• 814c495: Improve error tracking capture signals:

  • capture_exception now walks the full exception.cause chain (outermost-first, cycle-safe, capped at 50) instead of reporting only the outermost exception; chained causes are tagged with a chained mechanism and parent linkage.
  • Exception mechanisms now reflect the capture source: manual captures stay generic/handled: true, while the Rails middleware, Rails.error subscriber, and ActiveJob integrations tag captures as rails/rails_error_reporter/active_job with the correct handled flag. capture_exception accepts a mechanism: keyword.

posthog-rails-v3.16.0

Minor Changes

• 814c495: Improve error tracking capture signals:

  • capture_exception now walks the full exception.cause chain (outermost-first, cycle-safe, capped at 50) instead of reporting only the outermost exception; chained causes are tagged with a chained mechanism and parent linkage.
  • Exception mechanisms now reflect the capture source: manual captures stay generic/handled: true, while the Rails middleware, Rails.error subscriber, and ActiveJob integrations tag captures as rails/rails_error_reporter/active_job with the correct handled flag. capture_exception accepts a mechanism: keyword.

posthog-ruby-v3.15.3

Patch Changes

• fcc6205: Stop duplicating distinct_id inside /flags person properties.

posthog-ruby-v3.15.2

Patch Changes

• 1376f19: Retry remote feature flag requests after transient 502 and 504 responses.