Pantheon incident

Git Push and deployment Operations Failing

Critical Resolved View vendor source →

Pantheon experienced a critical incident on July 3, 2026 affecting Workflow Operations and Autopilot and 1 more component, lasting 7h 9m. The incident has been resolved; the full update timeline is below.

Started
Jul 03, 2026, 06:50 AM UTC
Resolved
Jul 03, 2026, 02:00 PM UTC
Duration
7h 9m
Detected by Pingoru
Jul 03, 2026, 06:50 AM UTC

Affected components

Workflow OperationsAutopilotGit

Update timeline

  1. identified Jul 03, 2026, 06:50 AM UTC

    Sites are unable to complete builds via Integrated Composer. Builds complete successfully but fail at the final step when the platform attempts to push build artifacts back to the site's Git repository. Customers will see their deploy workflow fail with a pre-receive hook declined error. No data loss is occurring. Live sites are not affected; only new code deployments are blocked. We have identified the root cause. A dependency version mismatch on a subset of our Git servers is causing a server-side pre-receive hook to crash when build artifacts are pushed. This is a Pantheon infrastructure issue and is not caused by any customer code or configuration. No action is required on your end. Do not make changes to your repository or Composer configuration. We will update this page as remediation progresses. We will update within 2 hours, or sooner if the status changes.

  2. identified Jul 03, 2026, 09:20 AM UTC

    We have identified that this may partially affect spinning up of Multidev environments. We are continuing to work on a fix for this issue. The next update will be in 2 hours or as soon as we have more details.

  3. monitoring Jul 03, 2026, 11:10 AM UTC

    A fix has been deployed, and the Dashboard is now displaying successful Git operations. We are monitoring the affected sites closely to ensure related features are functioning within expectation to confirm issues are completely resolved. We will provide a final update once the resolution is verified. If you continue to experience the same issue, please contact us directly at [email protected].

  4. resolved Jul 03, 2026, 02:00 PM UTC

    This incident has been resolved.