Deployment status polling broken in 2.136.8 - never receives completion status

[Deekee8]

Summary

Deployment status polling broken in 2.136.8 - CLI submits deployments successfully but never receives completion status. Deployments complete in Salesforce (verified in Setup → Deployment Status) but CLI times out polling with Status: Unknown | Components: 0/0.

Downgrading to 2.135.7 resolves the issue.

Steps To Reproduce

Unable to provide a minimal repo as the issue is with the CLI's deployment status polling, not project-specific.

1. Use salesforce/cli:latest-full Docker image (which resolved to 2.136.8 on 2026-05-27)
2. Run sf project deploy validate -d force-app -o -l RunLocalTests
3. Deployment is submitted successfully, Deploy ID returned
4. CLI begins polling for status
5. Polling loops showing Status: Unknown | Components: 0/0
6. CLI eventually times out

Environment:

• CLI: 2.136.8 (via Docker salesforce/cli:latest-full + npm install -g @salesforce/cli@latest)
• Node: 20.20.2 (via nvm)
• OS: Linux (Bitbucket Pipelines container)
• Target orgs: Production and sandbox

Tip

use sf doctor --create-issue to automatically fill the required information

Expected result

CLI receives deployment status updates and exits with success when Salesforce completes the deployment.

Actual result

CLI never receives status updates. Polling shows Status: Unknown | Components: 0/0 indefinitely until timeout, even though the deployment completed successfully in Salesforce.

Workaround: Pin to 2.135.7 - works correctly.

Additional information

This occurs in a CI/CD environment (Bitbucket Pipelines), not a local terminal.
Multiple pipelines across different branches and target orgs (prod, UAT, develop) all exhibited the same behavior simultaneously after latest-full updated to 2.136.8.
All pipelines worked correctly earlier the same day on 2.135.7.

System Information

CI/CD environment - Bitbucket Pipelines
Shell: bash
Docker image: salesforce/cli:latest-full (resolved to 2.136.8 at time of issue)

  {
    "cliVersion": "@salesforce/cli/2.136.8",
    "architecture": "linux-x64",
    "nodeVersion": "node-v20.20.2",
    "osVersion": "Linux (Bitbucket Pipelines container)",
    "shell": "bash"
  }

[github-actions]

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

[github-actions]

Hello @Deekee8 👋 It looks like you didn't include the full Salesforce CLI version information in your issue.
Please provide the output of version --verbose --json for the CLI you're using (sf or sfdx).

A few more things to check:

• Make sure you've provided detailed steps to reproduce your issue.
  • A repository that clearly demonstrates the bug is ideal.
• Make sure you've installed the latest version of Salesforce CLI. (docs)
  • Better yet, try the rc or nightly versions. (docs)
• Try running the doctor command to diagnose common issues.
• Search GitHub for existing related issues.

Thank you!