Skip to content

feat: add upload-release-to-gcs.sh script#23

Merged
ValentaTomas merged 2 commits into
mainfrom
fix/add-upload-release-to-gcs
May 13, 2026
Merged

feat: add upload-release-to-gcs.sh script#23
ValentaTomas merged 2 commits into
mainfrom
fix/add-upload-release-to-gcs

Conversation

@ValentaTomas
Copy link
Copy Markdown
Member

Adds scripts/upload-release-to-gcs.sh — downloads firecracker-{amd64,arm64} assets from a GitHub release and uploads them to GCS at the correct arch-subdir layout. Existing objects are never overwritten. Supports --dry-run.

./scripts/upload-release-to-gcs.sh --tag v1.14.1_f0a35a1 --bucket my-bucket --dry-run
./scripts/upload-release-to-gcs.sh --tag v1.14.1_f0a35a1 --bucket my-bucket

@cla-bot cla-bot Bot added the cla-signed label May 13, 2026
@cursor
Copy link
Copy Markdown

cursor Bot commented May 13, 2026

PR Summary

Low Risk
Low risk because this only adds a standalone shell script and doesn’t change runtime code paths; main risk is operational misuse of gcloud storage cp/permissions when run.

Overview
Adds scripts/upload-release-to-gcs.sh to download firecracker-amd64/firecracker-arm64 assets from a GitHub release via gh and upload them to gs://<bucket>/<tag>/<arch>/firecracker, skipping uploads when the destination object already exists and supporting a --dry-run mode.

Reviewed by Cursor Bugbot for commit 92e651f. Bugbot is set up for automated code reviews on this repo. Configure here.

@ValentaTomas ValentaTomas enabled auto-merge (squash) May 13, 2026 06:05
@ValentaTomas ValentaTomas merged commit b78bd4c into main May 13, 2026
7 checks passed
@ValentaTomas ValentaTomas deleted the fix/add-upload-release-to-gcs branch May 13, 2026 08:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants