ci(release): publish to Bunny storage instead of DO Spaces - #12
Merged
Conversation
Bunny's S3-compatible API replaces the DO Spaces action. The doctl CDN purge steps go away with it; Bunny purging needs its own API key.
nabeelio
added a commit
that referenced
this pull request
Aug 10, 2026
Publish stable.zip to Bunny storage over its S3-compatible API instead of DigitalOcean Spaces. Same commit as #12, cherry-picked onto releases/2.0. - Both upload steps use the AWS CLI that's already on the runner, so `BetaHuhn/do-spaces-action` drops out. - Bucket and access key are both `acars`, endpoint is `https://ny-s3.storage.bunnycdn.com`. The only new repo secret is `BUNNY_SECRET_ACCESS_KEY`. - `AWS_REQUEST_CHECKSUM_CALCULATION: when_required` is defensive. AWS CLI v2.23+ sends checksum headers by default and several S3-compatible stores reject them. I haven't confirmed Bunny is one of them, and it's harmless either way. - The doctl CDN purge steps are gone. Bunny purging needs its own API key, so that's a follow-up if we want it. - `SPACE_*` and `DIGITALOCEAN_ACCESS_TOKEN` are unused after this and can be deleted from the repo secrets.
nabeelio
marked this pull request as ready for review
August 10, 2026 22:21
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Publish stable.zip to Bunny storage over its S3-compatible API instead of DigitalOcean Spaces.
BetaHuhn/do-spaces-actiondrops out.acars, endpoint ishttps://ny-s3.storage.bunnycdn.com. The only new repo secret isBUNNY_SECRET_ACCESS_KEY.AWS_REQUEST_CHECKSUM_CALCULATION: when_requiredis defensive. AWS CLI v2.23+ sends checksum headers by default and several S3-compatible stores reject them. I haven't confirmed Bunny is one of them, and it's harmless either way.SPACE_*andDIGITALOCEAN_ACCESS_TOKENare unused after this and can be deleted from the repo secrets.