S3-backed CI artifacts (opt-in)
Cross-job staging no longer has to use GitHub Actions artifact storage. Workflows can use artifactBackend: s3 (default remains github) so large blobs (spread OCI tars, Helm charts) go to S3-compatible storage (e.g. Bunny) via CI_ARTIFACTS_* secrets, while existing repos keep today’s behavior until they opt in.
Includes: composite upload/download actions (resolved with $/.github/actions/... for reusable workflows called from other repos), optional artifact-upload / artifact-download workflows, OCI spread upload/merge with per-run S3 cleanup, Helm diff/deploy and Release Management wiring, and Utils ci-artifacts-cleanup (scheduled retention sweep).
Consumer setup: set artifactBackend: s3 on project.yaml / project-release-management.yaml (and enable cleanup in project-utils.yaml); provision bucket + secrets per repo (e.g. Terraform ci-artifacts module).
v1.1.0
- Total issues resolved: 0
- Total pull requests resolved: 4
- Total contributors: 2
Dependencies 📦
- 301: Update docker/setup-qemu-action action to v4.4.0 thanks to @renovate-runner[bot]
- 299: Update aws-actions/configure-aws-credentials action to v6.3.0 thanks to @renovate-runner[bot]
- 292: Update packagist/conductor-github-action action to v1.7.0 thanks to @renovate-runner[bot]
