Flow release: February 21, 2025

GitHub app authentication

We've added GitHub Apps as a new authentication method for our GitHub Cloud and GitHub Enterprise Server integrations. This authentication method gives you:

More security: Take advantage of short-lived tokens, fine-grained permissions, and more granular repo access controls.
Higher rate limits: Rate limits are scalable and set per GitHub organization, which means Flow can ingest your data faster and with fewer disruptions.
Easier token management. Authentication is not tied to a user account. Just install the app on your GitHub organizations.

Where should I start? If you want to create a new GitHub integration, we recommend using the GitHub app authentication method whenever possible. If you already have GitHub integrations, migrate to GitHub app authentication if you'd like to take advantage of the benefits. Refer to the GitHub app integration and migration guide to get started. If you have a large number of GitHub organizations and want to use the GitHub app, let your Flow contact know so we can support you with the best way to ingest your data.

Updated calculation for Lead time for changes and deployments

In some cases, customers have reported unexpected commits being associated with their deployments in Flow. This mainly impacted the calculations for Lead time for changes, but also impacted the number of commits associated with their deployments in Deployment log. We've updated our calculation for deployment changesets and Lead time for changes to better recognize which commits are associated with which deployments especially in situations where:

You have git tags outside a linear commit history that aren't included in your deployment and git tag configuration.
You have git tags in multiple branches that are classified as deployments in your deployment and git tag configuration.

We've already made this change for new deployments, but in the next week we'll be reprocessing your historical data to ensure all your data uses this new calculation. While you're likely to see some changes in your metrics, this change will much more accurately represent the work you're deploying.

This is a particularly impactful change for organizations that employ complex branching and git tag workflows. Now Flow will better represent your data automatically.

Where should I start? You don't need to do anything for this change. We will automatically reprocess all your historical deployments and new deployment data will use this updated calculation logic. You may notice some metric change over the next week, but then you'll be able to take advantage of deployment metrics that better represent the way you work.