Document GitHub Actions workflow for artifact deployment to Google Cloud Storage

[Copilot]

This PR addresses the question about which GitHub Action creates artifacts and pushes them to gs://hedera-platform-builds by providing a comprehensive analysis of the repository's CI/CD workflows.

Key Findings

After examining all GitHub Actions workflows in the repository, no workflow explicitly references gs://hedera-platform-builds. However, the main artifact creation and deployment infrastructure consists of:

Primary Workflow: node-zxc-build-release-artifact.yaml

This reusable workflow (workflow_call) is responsible for:

• Building node artifacts and creating deterministic ZIP archives
• Uploading artifacts to Google Cloud Storage using configurable bucket names
• Publishing Docker images to multiple registries (GCP and JFrog)
• Publishing Maven artifacts to either Google Artifact Registry or Maven Central

Key upload destinations:

• ${{ secrets.bucket-name }} - Primary artifact bucket (likely the target bucket)
• ${{ secrets.cdn-bucket-name }} - CDN distribution bucket
• gs://platform-sdk-ci-release-artifacts - SDK-specific artifacts

Calling Workflows

Two workflows trigger the artifact building process:

1. node-flow-deploy-release-artifact.yaml - Production releases

   • Triggered by version tags (v*.*.*)
   • Passes ${{ secrets.RELEASE_ARTIFACT_BUCKET_NAME }} as bucket-name

2. node-flow-deploy-adhoc-artifact.yaml - Adhoc releases

   • Manual workflow dispatch
   • Also uses ${{ secrets.RELEASE_ARTIFACT_BUCKET_NAME }}

Conclusion

The gs://hedera-platform-builds bucket is most likely configured as the RELEASE_ARTIFACT_BUCKET_NAME secret in the repository settings. The actual artifact creation and upload is handled by node-zxc-build-release-artifact.yaml when called by the deployment workflows.

---

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

[lfdt-bot]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)