Repository navigation
ci: publish immutable embedded releases to Cloudflare R2 - #2
Merged
Merged
Conversation
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.
Published embedded releases now upload their verified
dist-embedded.zipcontents tocdn.openpatch.org/onlineide/<tag>/include/. Each release remains immutable and older versions remain available. The existing release workflow also accepts a published tag for initial uploads and retries.Wrangler reads organization secret
CLOUDFLARE_R2_CDNand variable or secretCLOUDFLARE_ACCOUNT_ID. Publication sets CORS, correct MIME types, and immutable caching, then verifies every file through the public hostname. The Cloudflare API token needs Account → Workers R2 Storage → Edit; bucket-scoped object permissions support only S3.Validation: 12 publisher/extraction/verification tests, actionlint and the existing compiler, runtime and Chromium tests pass. The initial upload succeeded for
v2.2.1-hyperbook.28; all 414 runtime files match the verified release archive and pass public CDN checks for SHA-256, MIME type, CORS and immutable caching. A generated Hyperbook loaded the live CDN in Chromium and executed Java code with the expected output and no browser errors. Merge this workflow to enable publication for future releases.