Project

posthog-ruby

0.07
A long-lived project that still receives updates
posthog-rubyposthog/posthog-rubyHomepageDocumentationSource CodeBug TrackerWiki
The PostHog ruby library
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
 Popularity
Downloads
2,276,679
Stars
32
Forks
27
Watchers
11
 Releases
Current version
3.5.4
Total releases
42
First release
1980-01-02
Latest release
2025-12-04
 Issues
Open Issues
5
Closed Issues
20
Total Issues
25
Issue Closure Rate
80%
 Pull Requests
Open Pull Requests
1
Closed Pull Requests
8
Merged Pull Requests
71
Pull Request Acceptance Rate
88%
 Development
Primary Language
Ruby
Licenses
MIT
Average date of last 50 commits
2025-09-14
Reverse Dependencies
2

 Dependencies

Runtime

concurrent-ruby
~> 1
 Project Readme

PostHog Ruby

Please see the main PostHog docs.

Specifically, the Ruby integration details.

Important

Supports Ruby 3.2 and above

We will lag behind but generally not support versions which are end-of-life as listed here https://www.ruby-lang.org/en/downloads/branches/

All 2.x versions of the PostHog Ruby library are compatible with Ruby 2.0 and above if you need Ruby 2.0 support.

Rails Integration

Using Rails? Check out posthog-rails for automatic exception tracking, ActiveJob instrumentation, and Rails-specific features.

Developing Locally

  1. Install asdf to manage your Ruby version: brew install asdf
  2. Install Ruby's plugin via asdf plugin add ruby https://github.com/asdf-vm/asdf-ruby.git
  3. Make asdf install the required version by running asdf install
  4. Run bundle install to install dependencies

Running example file

  1. Build the posthog-ruby gem by calling: gem build posthog-ruby.gemspec.
  2. Install the gem locally: gem install ./posthog-ruby-<version>.gem
  3. Run ruby example.rb

Testing

  1. Run bin/test (this ends up calling bundle exec rspec)
  2. An example of running specific tests: bin/test spec/posthog/client_spec.rb:26

How to release

Both posthog-ruby and posthog-rails are released together with the same version number.

  1. Create a PR that:

    • Updates lib/posthog/version.rb with the new version
    • Updates CHANGELOG.md with the changes and current date

  2. Add the release label to the PR

  3. Merge the PR to main

  4. The release workflow will:

    • Notify the Client Libraries team in Slack
    • Wait for approval via the GitHub Release environment
    • Publish both gems to RubyGems (via trusted publishing)
    • Create and push a git tag

  5. Approve the release in GitHub when prompted

The workflow handles publishing both posthog-ruby and posthog-rails in the correct order (since posthog-rails depends on posthog-ruby).