Repository navigation
feat: self-host app updates on cloudflare - #39
Merged
Merged
Conversation
leviFrosty
force-pushed
the
hot-updater-cloudflare
branch
from
October 13, 2026 22:52
702b949 to
7d6704f
Compare
leviFrosty
marked this pull request as ready for review
October 14, 2026 02:34
leviFrosty
force-pushed
the
hot-updater-cloudflare
branch
from
October 15, 2026 02:49
7d6704f to
5c7893f
Compare
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
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.
Self-host app update delivery on Cloudflare with Hot Updater 1.0.2. Each of dev, beta and prod gets a separate Worker, D1 catalog and private R2 bucket. Only the authenticated client protocol is public; deployment and administration use provider credentials. The ordinary ww-api Worker remains unchanged.
Include the official schema, pinned adapters, environment-specific migration/deploy scripts and tag workflow. The matching WitnessWork PR #757 removes Expo Updates and must land after this backend half. Existing Expo Updates binaries require a new native build to switch providers.
All three environments are provisioned: Workers deployed, D1 schemas applied, client keys registered, and scoped R2 secrets installed. Credentials are saved in the Agents vault as
WitnessWork OTA R2 (dev),WitnessWork OTA R2 (beta),WitnessWork OTA R2 (prod)and the account-scoped D1 Edit tokenWitnessWork OTA D1. No credential values are committed.Validation:
Test signatures were restored and test releases disabled after verification. Production backend configuration and credentials are verified; production app native testing remains deferred. No production app OTA, upload or release was performed.