posthog/CHANGELOG.md

Changelog

1.14.0 - Thursday 03 September

• Insight History

Eric really killed this one with a massive pull request where 55 files were modified.

As a result, PostHog now allows you to look through a history of the charts you've made on 'Insights', so that you don't have to worry about forgetting the exact filters you used to reach a certain conclusion, or feeling bad about not having saved that perfect chart from a week ago.

Experiment with insights all you want, now without the fear of losing your work.

• Personal API Keys

We also merged another huge PR (58 files changed!) from Michael that's been a long time in the making because we wanted to get this just right.

To facilitate integrations with external services, as well as make the experience of using our API simpler and safer, we have now introduced Personal API Keys. They can be generated and deleted on the PostHog setup page. It's worth noting that this is a private API Key, compared to your public 'Team API Key' used in the snippet.

Lastly, because of this change, we have deprecated authentication with username and password for API endpoints.

• Public Roadmap

At PostHog, one of our core values is transparency. As a result, we try to make as much information public as we can, from what we're working on to how we operate.

As such, it felt important to us to release a public roadmap where our entire community can view what we're up to, what we'll work on next, and what our objectives are for the future. For a long time we have had a rough roadmap available in our Handbook, but, by now having our roadmap on GitHub, we can directly link issues to the board, and community members can also vote (with emojis 👍) on issues they believe to be important.

Furthermore, we have always encouraged members of our community to open issues for bugs, feature requests, or just anything at all they want to see changed. Now, issues opened by the community can be incorporated on the roadmap, so you can have an idea of how your suggestions fit in with our development process.

Keep the tickets coming!

• PostHog FOSS

As an open core company, we have to conciliate our open source efforts with our ability to generate revenue. Generating revenue is how we're able to continue to sustain our extensive work in the open source space.

Thus, after a lot of brainstorming and calls with the likes of Sid Sijbrandij, CEO of multibillion dollar open core company GitLab, we settled on a business model that allows PostHog to be a sustainable company in the open source space.

This led to the creation of two key things: an ee subdirectory on our main repo, and a new repository called posthog-foss. We'll be explaining these in more detail in the future, but, for now, you should know that to run fully MIT-licensed software, you can either clone the main repo and delete the ee subdirectory (without any consequences), or clone our posthog-foss repo, which is a mirror of the main repository without proprietary code.

In addition, if you're an enterprise customer looking for added functionality and improved performance, contact us at sales@posthog.com to discuss the license for using our proprietary features.

• Secret Key Requirement

To ensure the security of your PostHog instance, it's important that you use a randomly-generated unique SECRET_KEY. This key is used by Django to encrypt cookies, calculate hashes, and generate tokens, making it of high importance.

Prior to this version, we denoted the importance of this in our Docs, but did not enforce it in our software. Now, to enhance security, PostHog will not allow you to run the server without setting it.

Many of our deployments generate and set this key by default, so that you will not need to worry about it. This is the case with our Heroku One-Click deployment, for example. However, other methods may not automatically do this (we're working on it!). As such, if you run into any issues when updating PostHog, make sure you have a unique SECRET_KEY set.

You can find more information about this on our 'Securing PostHog' page and should always feel welcome to ask any questions on our community Slack group.

Bug Fixes and Performance Improvements

• We disabled our own snippet on DEBUG instances and improved tracking
• We started using django_extensions
• Tim added a test to PRs to check if our Docker image builds
• Michael and a bot helped us keep dependencies up-to-date
• Marius made the Toolbar UX better by fixing its element detection, making the info window follow the mouse, and correcting other minor things
• Paolo made user metrics better
• Eric updated our /insights endpoint
• We changed the color on some tabs and the tone on some buttons to improve our UI
• We fixed and then added tests for our multitenancy environment
• Michael fixed a UI bug on our URL list
• We overhauled our README, which was really in need of updating. It now looks better, reads better, and has better info about deployment and our Enterprise Edition.
• We improved the command description for setup_review
• Tim made our testing of PR environments easier
• We made the 'Launch Toolbar' links open on a new page
• We updated our CHANGELOG and bumped versions here and there(and in a lot of other places)
• We crushed a bug regarding rest hooks for Docker images
• We improved our syntax highlighting for code snippets
• License issues and disappearing user paths on Firefox are now bugs of the past
• @J0, a community member, introduced a feature for disabling link sharing
• Michael removed a useless release drafter action
• We had a small refactor done on PostHog's head template
• Yakko fixed our Cypress tests and made them faster
• We allowed Sentry in DEBUG mode
• We demolished issues with Safari's funnels and IDs for our CohortPeople class
• Paolo set up an awesome Preflight page
• We upgraded the Sentry SDK
• We made our action for syncing FOSS and non-FOSS repositories beautiful("using prettier")
• We set up an action for syncing our FOSS and main repo then updated it again and again
• We added regex and action hints for the Toolbar
• We migrated to BigInteger IDs
• We changed the Toolbar heatmap to display number of clicks instead of page rank
• We fixed our bottom notice warning for PostHog running on HTTP
• We set up a workflow for auto-updating the version
• We improved the description for DAUs
• Michael added a warning bar for production PostHog instances running on HTTP
• Anna fixed a bug with action deletion
• We fixed an issue with licensing and another one
• We fixed our Docker images to account for changes in Kea and Django's SECRET_KEY
• Marius upgraded us to use the newest version of Kea Typegen
• Eric pulverized a bug about empty conditions on Trends
• We added a column to denote when actions were created
• We made the Toolbar easy to launch for all users

1.13.0 – Thursday 13 August

• PostHog is Now Available on Segment!

We're happy to announce that PostHog is now available as a destination on Segment.

Our friends at Segment have built a platform that works as an integrated data pipeline to pull in all your customer data. It's a cool way to combine PostHog with ie Google Analytics or Salesforce data.

If you're already a Segment user, check us out on their Destination Catalog. Otherwise, if you're dealing with multiple tools for data collection and analysis, consider using Segment! They have a generous startup scheme too, like us.

• Quicker access to everything

We consolidated trends, sessions, funnels, retention, and user paths into one page for much faster answers to the questions you may have!

• More powerful Slack messages

PostHog has a feature where Actions can be posted to Slack or Microsoft Teams. This helps you notify your team in real time of the user actions that really matter. Just got a new user? Ping your sales team. Did a user try out a new feature? Get an alert!

The integration used to be very basic - but now you can edit the message format directly in the UI.

• Toolbars for all!

PostHog provides an irrefutably awesome toolbar. This lets you interact with your site or app and understand who is doing what. We've been in Beta for a few weeks, and spent a lot of time interviewing early users - thank you to everyone that took part!

We have now eliminated many bugs and improved the UX, so this feature will be on by default for all new PostHog users.

• Better annotations

You can annotate graphs in PostHog - mention big releases, new features, or changes to your UX.

Now, it's quicker and easier to get a quick read on what happened that caused something funky in your graphs.

We've also made all annotations default to being global. That means if you create an annotation in one graph (or in the annotations page), it is visible across any dashboard graph that covers that date range. No need to fear losing your annotations.

Bug Fixes and Performance Improvements

• Heatmaps now work for sites built with Tailwind CSS.
• Some clicks for the heatmap were being double counted. Now they aren't.
• We improved the UX for posting to Slack.
• We fixed selector attributes.
• We made a security improvement to the way session cookies are used, and removed SameSite middleware.
• We fixed a bug where GitHub actions required packer to be manually installed.
• Cohorts supported for people merged to a person.
• Solved a bug with the way the current version update message displayed.
• If you're running in DEBUG mode, it'll be more obvious!
• We refactored sessions into a new queries folder.
• There was a weird issue with the user email search. That's gone.
• We squished two bugs with our stickiness metrics when specific events were filtered.
• The team page now looks much nicer.
• Eric smushed a bug with filters.
• We improved how logouts work with the toolbar.
• We crushed a bug with date filters and funnels.
• We improved how StatsD is used for better tracking of the things that PostHog doesn't track!
• Chunk loading errors be gone. The assertive "attempt to" in the title says it all.
• Saving actions from the toolbar now makes it easier to view insights or to go to your actions list.
• We cleaned up a debug warning, leveraging heart emojis.
• An issue with demo data on the dashboard loading has been disappeared.
• Tim eliminated an issue with cumulative graphs.
• A Sentry error about breakdown filters is now brown bread (dead).
• We now return an error for malformed JSONs to the API.
• We've converted the toolbar to TypeScript. That always makes for a ridiculously huge pull request. 110 files changed. Noice, noice.
• We added a missing migration for ActionStep URL.
• Warnings on running local tests now don't appear.
• The experiments tab in the navigation didn't have a highlight. Now it does. That was weird.
• We moved most of the analytics logic into a queries folder. This means it's in one place and in the future will make a ClickHouse integration way easier.

1.12.0 - Friday 29 July

• Shared Dashboards

Dashboard on a TV in your office? Want to have a public stats page? Share a dashboard with someone who doesn't have a PostHog account? You can now publicly share a dashboard. Just click "Share Dashboard" and enable sharing. You'll get a link that's publicly accesible.

Changed your mind? You can always disable sharing.

• Aggregate Functions

Want to know the average revenue per user? Want to know the lowest browser version anyone is using? You can now do Sum, Max, Min and Avg calculations on any event property and graph them in trends!

• Global Annotations

Digging through git commits to find out what changed to make the graphs go hay-wire? No more! You can now annotate when something happened (a big release, a bugfix or a launch) and make it super easy for your team-mates to figure out what's going on. Now global.

As part of this, you can now also manage, add and delete annotations from a central screen.

• Funnel Step Time

You can now see how long it takes users on average to get through steps in a funnel.

• Regex Filtering

Regex master? Put those skills to use on any property with regex filtering

• Retention Table Improvements

Previously the retention table was hardcoded to only recognize the $pageview event as a retention event. Now, you can select any action or event to measure retention on.

Clicking on any section in the retention table will tell you exactly what users fall in that item.

Bug Fixes and Performance Improvements

• We've added a button to easily launch the toolbar
• We've made line charts more precise by straightening the lines.
• We've enabled interval selection for sessions too
• We're now using Typescript (1, 2)
• We've [fixed various issues with annotations(https://github.com/PostHog/posthog/pull/1291)
• We don't refresh the Events table if you don't select a property
• "All time" date filter works on funnels again
• You can now [delete users from your team(https://github.com/PostHog/posthog/pull/1274)
• Fixed an issue where timestamps were displayed incorrectly on sessions
• Fixed a bug where selecting "last 48 hours" wouldn't return results
• Fixed issues with funnels loading on dashboards
• UUIDs are ugly, so we just cut them off rather than wrapping entire lines in the events table
• Samcaspus contributed a little bit of magic: we now automatically adjust your date range if you change the interval
• We added a button to dashboard that allows users to [easily add a new item(https://github.com/PostHog/posthog/pull/1242)
• enhanced ctrl + click new tab opening feature
• Massively speed up loading live actions
• Fix password validation and improve minimums notice (closes #1197)
• Closes #1180 worker fails if timestamp is invalid
• (abhijitghate)[https://github.com/abhijitghate] contributed an improvement to the way we display DAU's in the graph
• Fix an issue where loading sessions would do an entire table scan, and then throw it away
• Automatically bind docker-compose 2to port 80 for production deployments
• • a bunch of improvements to make local development better! (1, 2, 3, 4)

1.11.0 - Friday 17 July

• Annotations

• Cohort filters

• Retention table filtering

• Many toolbar fixes.

Bug fixes and performance improvements

• Some first-time contributors ran into errors with TemplateDoesNotExist, which we've solved
• Add comprehensive Cypress tests for dashboards to avoid bugs
• Add webpackbar for better readability while developing
• Moves total to the bottom of the pie chart to fix z-index issues readability while developing
• Fix an issue with filtering on the event type
• Add Typescript to the PostHog frontend codebase
• Fix the ability to delete dashboards
• Add support for LZ-String compression
• [Use Black for Python formatting](https://github.com/PostHog/posthog/pull/1136

1.10.1 - Thursday 2 July 2020

Bugfixes

• Actually include the version bump when you push a release! 🐛
• Add flutter docs and reorder flow #1134
• Black all the things! #1136

1.10.0 - Wednesday 1 July 2020

Toolbar

• It's like inspect element, but for user data.

• Easily see the ranking of which parts of the page your users are interacting with the most:

• We learned a ton about our product and website within minutes of trying this out.

Feature flags

• Feature flags let you roll out changes to users with a certain property, or to a percentage of users, or some combo of the two.

Other exciting, enthralling and invigorating features

• Flutter Integration. You asked for it and now it's here!
• Retention page. PostHog already had stickiness, but now there is a table that demonstrates perhaps more clearly how your users are coming back (or not!)

• Better onboarding. We've had a go at redoing how our set up flow works, and will be tracking if it helps more people get through PostHog's own funnel!
• Platform.sh deployment. A very simple, new and trendy way to get up and running!
• Porter development. Join the cool kids and do web development in the cloud. Thank you so much to porter-dev for creating this PR.
• Event name filtering. By popular demand, you can now filter the events table by the event name. Happy debugging your implementations!

Bug fixes and performance improvements

• We are now more privacy friendly - you can discard IP address data
• Added the offer of a free pairing session to the contributing guide - ask us!!
• We fixed a bug with the start times for the session view
• We improved the ./bin/test command
• We now let you break down users by their properties (it wasn't working before!)
• We sped up the people page - pro tip: don't load stuff you don't need!
• We disabled batching in the snippet, since this helps prevent data loss
• Fixed a weird bug with moving from sessions to trends
• Fixed person properties being selected, which was causing some issues with the stats.
• We now automatically select hourly if you're looking at data from just today or yesterday - it was weird otherwise!
• We turned today into the last 24 hours - you can now think of yourself as Jack Bauer
• The people modal now has pagination
• We now copy array.js.map as well as everything else to better debug errors
• We now show a warning for old browsers, and feel bad for those in big enterprises that must use them!
• Black now added to post commit hooks, so we don't get crazy all-file reformatting
• Fixed an issue with force refreshes for cache in certain places
• We fixed a failing test problem with team_id
• Improved person properties and pagination
• Solved a Sentry error with overly long text
• We cleaned the configs for release-drafter

1.9.0 - Thursday 18 June 2020

• Sessions view
• You can then see exactly how a user interacted with your app: This should really help with debugging, or just trying to get a detailed view of what users are up to.

Better testing

• Fixed Cypress tests
• Enabled running cypress in parallel, which saved a minute.
• Fixed cypress linting errors and sped up tests further
• Cached PostHog's yarn builds, which took e2e tests down by around 30%.
• Finally, we now wait for PostHog to start serving requests rather than the 60 second sleep when running Cypress.

Develop PostHog with Porter

Management command for millions of events

Set properties to anonymous users

Bug fixes and performance improvements

• We worked hard on improving caching to speed things up. We fixed cache refreshing in a few areas, we made a few caching adjustments to fix #1022. Finally, we now use redis to cache results.
• Save time! You can now create actions from the trends page.
• Upgrade to posthog-js 1.2.0 to support dynamic params.
• We fixed long href inserts - the href can now go up to 2048 characters before truncation. Someone must have had some funky urls going on...
• We prevented intermittent issues with yarn build
• We fixed a bug that caused cohorts to fail when actions were deleted
• We solved a problem with comparing trend sessions distribution
• We added a limit to number of returned entities for breakdowns so queries don't time out
• We created a fix for an issue with heartbeats
• We made it clearer that PostHog SaaS users are on the latest version
• We slashed CPU consumption for VSCode by excluding a folder
• Generated a performance improvement for element stats
• We stopped giving way too many decimal points on our graphs!
• Trends page UX improvement
• Improved filtering on elements
• We fixed a race condition
• We don't rely on $ to separate PostHog's events
• We removed the redundant math selector on funnels - it didn't do anything!
• Django upgraded to 3.0.7
• We made HTTPS work locally - we had lots of community issues raised, so that should make it easier to get started with!
• We improved the setup overlay layout
• We sped up the events endpoint by just hitting the current week's partitions
• We solved a problem with temporary tokens
• We added webpack HMR and hashes to chunk filenames. (#878)

1.8.0 - Wednesday 3 June 2020

• Cumulative graphs

• More powerful paths

• Add property filters to actions + lots of improvements (#841)

• We cleaned up descriptions in the breakdown filter.
• The UX is nicer for selection a URL on creating an action.
• We made it simpler to understand how to use custom events during the setup process.
• The token issues, oh the token issues. Fixed and fixed.
• It was time for our events table to become Ant Designed.
• Pre-2020 events won't affect partitions any more.
• Better debugging with Sentry.
• Scrollbar small issue be gone.
• We improved how empty funnels work.
• Events are 40ms faster to process - 25% quicker!
• The sidebar works properly on mobile - no more squished interface on your cell phone.
• Fix a bug with selecting filters
• Funnels are simpler.
• Solved a tricky bug on app.posthog.com caused by URLs with non-utf8 or raw binary query parameters.
• Nothing to do with dubious cheese, we fixed errors with babel
• Improved toolbar UX for actions to fix a small issue.
• PostHog will now cache SQL and parameters between events processing. This speeds things up by a further 40%.
• We refactored more classes to hooks, fixing a bug with event name labels along the way.

1.7.0 - Wednesday 27 May 2020

• Reactive Native
• Comparison charts

• Tooltip: View the users inside each datapoint

• Property keys explained

• Automatic domain detection

• Developing PostHog is now a bit less tedious. We halved the time it takes to install python dependencies for any deployment.
• We've written a lot of front end tests, as well as a regression test for single step funnels, where there was a bug - now fixed.
• We neatened dashboard items so they're closer together in the navigation.
• We improved our Sentry setup.
• Marius fixed the way tables display when they're on a dashboard.
• Eric slayed a bug when the People page wouldn't load with entity specific filters applied.
• We've had several users with very high scale pushing the limits of redis. We have more work to do here, but we've improved the way we handle filled up servers.
• A little header spring cleaning.
• We fixed a bug with suggestions loading, and another with EditAppUrls null check.
• Cohort property filters had a small issue, now fixed.
• AntD's gradual takeover of our app and website continued - it was added to more dropdowns this week.
• We prevented requests to update server for those who have opted out, and added fine grained control to the opt out flow.

1.6.0 - Wednesday 20 May 2020

• Dashboard presentation mode

• Dashboard resizing

• Paths works with events

• Dashboard mobile support
• Microsoft Teams support
• You can now use the django-debug-toolbar to diagnoze performance issues better
• We added ES Lint, for JavaScript linting.
• We fixed property filter array issue
• Optimize funnel rendering is a major improvement in speed for those with many events - now 1 order of magnitude faster.
• Multiple filters with same key, fixed a bug that means you can now have multiple filters that are the same ie $current_url doesn't equal A and $current_url doesn't equal B
• Event partioning, which speeds up trends and paths pages in particular. Learn more about scaling PostHog.
• The component Deletewithundo wasn't working because of property mixup, now it is!
• Funnels and Actions now use Ant Design
• We temporarily removed stickiness breakdowns, as they were causing issues.
• Better handling of breakdown views when users don't have the property.
• Fixed an issue with viewing certain queries over all time.
• Resolved an issue with sessions where null conditions were missing
• Fixed the cohort input search bug
• Solved a bug with navigating to users
• Improved our event insertion scalability

1.5.0 - Wednesday 13 May 2020

• Multiple dashboards

• Dark-er mode

• Break down by cohort

• Big refactor of how we do routing in the app which means going backwards and forwards should work a lot smoother

• Faster loading of paths

• More accurate DAU/uniques count

• Fix dotted line appearing on completed days. Thanks Jujhar!

1.4.0 - Wednesday 6 May 2020

• Added filtering of properties individually. For both trends and funnels, you can now add filters for each event/action individually

• Added Breakdown by properties in graph.

• Session time series, you can now see how time spend in your app changes over time

• Export cohorts as CSV

• Edit frontend selector for actions in PostHog

• Setup page redesign

• Restrict access to instance by IP address (#679, #682)

• Fix today + hourly filtering not working (#700)

• Fix timestamps if users had wrong dates set locally (#693, #697, #699)

• Add $screen to events table (#681)

• Add noindex to login/signup screens (#702)

• Speed up cohorts page and use antd (#706)

1.3.0 - Wednesday 29 April 2020

• We have added an Android library so you can now capture events in your Android app and send them to PostHog, we can automatically capture screen changes, and send any other events that you like

• There is now, also a PostHog Gatsby plugin

• We have added URL wildcards so you can use % as a wildcard when setting up an action

• We have also updated the Trends page design as well as adding trends info hints. Trends is the default homepage when logging into PostHog.

• The Events table can now be sorted by timestamp.

• Added a more strict flake8 setup and improvements
• Upgraded Kea to 2.0.0-beta.5
• Implemented AntD into Setup page
• You can now allow access to your PostHog instance by IP address for more security. this does not apply to the JS snippet or the event capture API
• Added model for typing of filters
• Added copy code to clipboard changes
• Use forward for header in middleware if applicable
• Move get_ip_address to utils
• Fixed redirect to be explicit for /Trends
• Moved models to separate files
• Added link to docs for local deployment
• Warn instead of crash on invalid selector when using the front-end toolbar

Bug Fixes

• Fixed issue with default trends route
• Fixed Setup page operations not working
• Fixed crash when hovering over events
• Fixed issues with $create_alias when users have multiple distinct_ids attached to them
• Fixed trends save to dashboard issue
• Fixed adding dashboarditem with set dates

1.2.0 - Wednesday 22 Aptil 2020

• We have added an iOS library so you can now capture events in your iOS app and send them to PostHog, we can automatically capture screen changes, and send any other events that you like

Click here for instructions on how to install it on your app.

• We have added Sessions to /trends with two modes: “Average session length”, which shows you how long sessions are and how many, and “distribution” which makes it super easy to spot whether sessions are uniformly distributed or whether there are outliers

• Funnels can be filtered by properties

• Added indexes so loading /trends is super fast, even with millions of events
• We have offloaded storing events to workers, so that calls to our events API are non-blocking, and you can scale insertion of events independently from the rest of PostHog
• Removed drf-yasg in favor of our own hosted docs
• Added layout/header components of Ant design
• Updated property filters to be "tokenized"
• Updated the way we display actions/events in trend graphs if those action/events have no data in a given timeframe
• Updated property filters so that they 'AND' rather than 'OR' if you filter multiples

Bug Fixes

• Fixed unable to sign up to teams
• Fixed stickniess not loading
• Fixed property filter bug that would break when multiples were applied in some circumstances
• Fixed setting event name in action
• Fixzed event filtering with teams

1.1.0.1 - Thursday 16 April 2020

• Fix issues with custom events while creating actions

1.1.0 - Wednesday 15 April 2020

Important! We've added Celery workers. We'll move tasks to workers to speed up a lot of actions in PostHog. See update instructions on how to enable workers.

• Users can integrate PostHog with Slack to send push notifications when events are triggered

• Funnels can now be filtered by Events not just Actions
• Funnels can be filtered by time intervals as well

• Added Ant Design to PostHog

• Trends can now be filtered by different time intervals

• Added dotted lines to represent data yet to be determined

• Trends graphs have fixed the X axis at 0

• Daily Active Users (DAUs) added as a default dashboard

• Changed the way we rendered urls in Paths to reflect better on different screen sizes

• Updated UX when saving actions to be clearer

• Changed the way we store events properties, we now store all event names and property names against the Team
• Refactored PropertyFilters into a function
• Added filter by event name to event properties
• Added mypy rules
• Using dateutil for datetime
• Added timestamp index to allow event tables to load at large volumes
• Updated helm charts to work with redis and workers
• Added a Babel plugin to reduce antd module load
• We now use offset instead of timestamp of posthog-js to avoid the wrong user time - previously if your local machine had a time set different to your location (or if the time was just off) we would have displayed that time.
• Using npm instead of yarn in copy command as Heroku doesn't have yarn
• We now use posthog-js to get array.js
• Removed unused indexes from migrations
• Updated PostHog snippet

Bug Fixes

• Removed unused future import to prevent Heroku deployments breaking
• Fixed dupliucated users in Cohorts
• Type Migration to prevent /trend bug when navigating to a url from a dashboard
• Added missing type in initial dahsboard element creattion to fix the same bug as above
• Fixed collectstatic on fresh Heroku updates
• Fixed network timeout yarn for antd
• Fixed npm command to copy array.js
• Fixed date filter not detecting moment
• Fixed redis error when upgrading Heroku
• Stopped throwing an error if a user doesn't have a distinct id
• Fixed a trends people bug that ignored the time interval selected
• Fixed site_url pass to slack from request

1.0.11 - Wednesday 8 April 2020

Important! We've added Celery workers. We'll move tasks to workers to speed up a lot of actions in PostHog. See update instructions on how to enable workers.

• Users can filter the trends view by any event rather than just actions

• Users can now change password in /setup

• Users can also reset password at login screen
• Added a logout button

• Added GitHub / GitLab Social Authorization

• Added Stickiness explanation in /trends > Shown As > Stickiness

• Precalculated events that matched actions, this massively speeds up anything that uses actions
• Added Celery background workers
• Added gunicorn workers in docker-server script
• Added email opt in for PostHog Security and Feature updates
• Removed yarn cache in production image
• Cleaned docker yarcn cache
• Reduced size of Docker images by ~80MB
• Set default password for postgres in docker-compose.yml
• Sped up the event insert by only loading actions that were really necessary
• Migrated ip field to event property
• Updated all links to point to new docs domain
• Added GitLab API url
• Added Async JS snippet
• Docker and server updates for helm

Bug Fixes

• Fixed some instances of Cohort page hangs
• Fixed demo actions not being recalculated
• Fixed breakdown error on DAUs where tables could not be filtered
• Fixed array.js
• Fixied ActionStep.url_ so that it can be null

1.0.10.2 - Friday 3 April 2020

• Precalculate Actions to speed up everything (dashboards/actions overview etcetera)
• Fix error running Docker file

1.0.10.1 - Wednesday 1 April 2020

• Fixes for Helm charts

1.0.10 - Wednesday 1 April 2020

• Users can now be identified directly from Trend Graphs

• Added demo data to new instances of /demo

• Built a Helm Chart for PostHog

• Ordering is now by timestamp instead of id

• Fixed typing errors

• Fixed funnels not working if order was set incorrectly

• Avoided team leakage of person properties

• Fixed live actions error that resulted in opening multiple events

1.0.9 - Wednesday 25 March 2020

• Stickiness now shown on Trend Graph

• Funnel builder changes

• Changed 'Add event property filter' to 'Filter events by property'.

• Added drop down to all filters for event properties

• Added '_isnot' and 'does not contain' to properties filters

• Moved API key to it's own box

• Various performance updates

• Bug fixes

1.0.8.2 - Wednesday 18 March 2020

• Fixes bug where events wouldn't be filtered under /person or /action.

1.0.8 - Wednesday 18 March 2020

• Moved actions into /event submenu

• Improved Actions Creation

• Delete user data

• Various performance improvements

• Bug fixes

• Turbolinks: Support for navigating between pages with the toolbar open

1.0.7 - Wednesday 10 March 2020

• Added changelog and reminder to update to app.
• Filtering action trends graphs

• Exact/contains matching for URLs in actions

• Filtering paths by date

• Graphs show numbers

• Allow multiple URLS when creating actions

• Better property filters

• API change If you're using the trends api, filtering by action ID is deprecated in favour of api/action/trends?action=[{"id":1}]