feat: Add --json flag support to apify push

[Copilot]

apify push had no machine-readable output, making it impossible for downstream tools to access the resulting build object programmatically (e.g. in CI pipelines or the push-actor-action).

Changes

• src/commands/actors/push.ts
  • Enable --json flag via static override enableJsonFlag = true
  • After retrieving the final build object, output it as JSON and return early when --json is passed — consistent with how builds create handles it

Progress/status messages continue going to stderr; the build object is emitted to stdout only when --json is set.

Usage

apify push --json
# stdout: raw Build object as JSON
# stderr: progress messages (Info:, Run:, Warning:, etc.)

Example output:

{
  "id": "abc123",
  "actId": "xyz789",
  "status": "SUCCEEDED",
  "buildNumber": "0.0.1",
  ...
}

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Support --json option with the apify push command</issue_title>
<issue_description>Many other CLI commands support the --json option as a way of consuming the output data programmatically.

apify push doesn't have support for this (unlike e.g. builds create). Users pushing Actors with the CLI now cannot access the resulting builds directly. See a downstream dependency issue.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Support --json option with the apify push command #1024

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.