We've made a few small fixes and improvements to the Deployments report:

• Slowest and Least Successful Deployments: To provide you with more relevant and timely insights, Slowest Deployments and Least Successful Deployments will now reflect data from the last complete month instead of the last three months.
• Highlights: The 3-month rolling averages no longer include the in-progress period, providing a more accurate representation of historical performance.
• More Accurate Group Representation: When selecting a Git provider group (e.g. a GitHub team), data starts after the group was created, providing a more representative group history. This matches the behavior on newer reports, like the KPI report.
• Time to Deploy: We’ve corrected a discrepancy in Time to Deploy between the Deployments report and KPIs report. This adjustment ensures that the Time to Deploy metric now aligns with the drilldown and KPI views.
• Batch Size: We've resolved a bug affecting a small number of teams where line changes may have been counted twice.

 If you have questions, please reach out to us at support@software.com.

We have corrected an issue in the weekly group email report to ensure it consistently displays the most recent week’s data. This resolves a problem where reports sent in May and June inadvertently showed data from a prior week. No other reports were affected.

We have released a fix and added enhanced monitoring to prevent this from happening again. We apologize for any confusion this may have caused.

We recently identified and addressed a discrepancy in our Deployment Frequency calculation on the KPIs page. Over the last week (approximately May 20th - May 27th), the metric did not include deployments that exclusively contained pull requests authored by excluded users and bots. This behavior has been changed, providing an accurate count of deployments.