feat: output build ID, number, and status from push action

[Copilot]

• Add outputs section to action.yaml with build-id, build-number, build-status outputs
• Modify push step to use --json flag and set outputs from parsed response
• Update README to document the new outputs
• Add example step in README that uses the action outputs
• Fail the action with an error message if build status is not SUCCEEDED
• Bump apify-cli to 1.3.0 (first version supporting apify push --json)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Output build ID / version</issue_title>
<issue_description>After building the Actor on Apify, we might want to reference the build in later steps. Returning the build ID / number / status from this action would definitely help with this.</issue_description>

<agent_instructions>use the issue description as well as the content of the comments to make changes to action.yml. make minimal changes that will result in this feature being implemented. be very concise, do not add excessive comments. use conventional commits for commit messages and PR titles.</agent_instructions>

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

@barjin update: https://github.com/apify/apify-cli/pull/1025 adds support for `--json` flag for `apify push` CLI command. When applied, the command will send the API response as described [here](https://docs.apify.com/api/v2/actor-build-get) to stdout.

We can pass some of this data to the Github Action outputs.</comment_new>

• Fixes Output build ID / version #17

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[barjin]

@copilot please review my comments.

[barjin]

Will the action still pass (will CLI return 0 exit code), if the build fails?

[Copilot]

It depends on the CLI implementation. The apify push command waits for the build to complete, so if the build fails the CLI should exit non-zero — causing the step to fail before outputs are even set. The build-status output is primarily useful for builds that finish with a non-fatal status (e.g. SUCCEEDED vs a partial state). Worth verifying against the actual CLI behavior once apify-cli#1025 lands.

[barjin]

well duh.

I just checked the CLI implementation, passing the --json flag actually changes the behaviour (without --json the process exits with 1 if the build is failing; with --json, it returns early). This means we'll need to check the status manually here to keep BC.

@copilot please prepare a commit failing the action if the status is not SUCCEEDED.

[Copilot]

Done in 8f066da — after parsing the JSON, the status is checked and the step exits with 1 (plus a ::error:: annotation) if it's anything other than SUCCEEDED.

[barjin]

Note for humans: we have to wait for the CLI release first landing this PR, only then we can merge this.