Repository navigation
Document recovery when Worker startup failures block deployment - #319
Merged
exe-dev-github-integration[bot] merged 1 commit intoOct 30, 2026
Merged
Conversation
asselstine
force-pushed
the
docs/oauth-startup-recovery-2026-10-30
branch
from
October 30, 2026 01:25
ce92189 to
ab50a5d
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.
A Worker startup exception made the production session prerequisite fail, blocking deployment of the merged OAuth scope fix in #317. This documents restoring a compatible working version, handling Cloudflare secret-version error 10215, and the 2026-10-30 recovery evidence. The package migration rollback guide links to the procedure.
Production recovery is complete. An emergency upload applied the exact one-line fix from #317 while preserving every other bundle byte, all 20 bindings, assets, runtime settings, and the Durable Object migration tag. The normal main deployment then succeeded on attempt 3: https://github.com/GenerationSoftware/factorize/actions/runs/40984395531. Final production version:
d979c2e9-3a50-46b8-bbc2-51c4dc996b21(100% traffic).Validation:
git diff --checkpassed.npm testCI validation passed for final commitce92189: https://github.com/GenerationSoftware/factorize/actions/runs/40985427635.Supersedes #318 so the PR includes the final recovery documentation update. Repository changes are documentation only; no application or deployment gate behavior changes.