Migrating to BuildPulse v2
The legacy v1 platform was retired on August 1, 2026. If your test results stopped uploading, here's how to get them flowing again.
Why are we moving to v2?
BuildPulse v2 brings significant improvements: a faster UI, redesigned dashboards, AI-powered code review, GitHub Actions runners, and a modern architecture that lets us ship features faster. It's the foundation for everything we're building next.
What happened on August 1?
As of August 1, 2026, the legacy BuildPulse app (v1) no longer accepts new test results. If your uploads stopped in late July, this is why: workflows still using the legacy upload action need the one-step update below. All active workflows are now served exclusively by v2.
Will I lose any data?
No. All of your existing data — test results, flaky test history, metrics, and settings — has already been migrated to v2. The migration process preserves your full history.
Do I need to change my CI configuration?
Yes. The legacy buildpulse/buildpulse-action uploaded to v1, which stopped accepting results on August 1, 2026 — switch your workflows to BuildPulseLLC/test-reporter-action@v3 with a v2 API token to resume submitting results. If you use a custom integration, update it to the v2 API endpoint in your organization settings.
What new features are available in v2?
Redesigned flaky test analytics with richer detail views, AI-powered code review on your pull requests, BuildPulse Runners for faster and cheaper GitHub Actions runners, improved engineering metrics and DORA dashboards, and MCP server integration for AI-assisted workflows.
How do I migrate?
Visit buildpulse.io and sign in with your existing GitHub account. Your organization and repositories will already be there. Complete the onboarding checklist to verify everything is connected.
I need help or have questions
Reach out to us at support@buildpulse.io. We're here to make sure your migration goes smoothly.