Repository navigation
fix(api): support Workers source fetching - #3
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
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.
Cloudflare workerd rejects fetch redirect mode error, causing every commit-pinned body request to return SOURCE_UNAVAILABLE. Use manual redirect handling and retain rejection of non-success source responses. Regression coverage verifies the runtime-compatible fetch option and redirected sources.
API/provenance tests, typecheck and lint pass. The corrected Worker is deployed through Wrangler; Live acceptance passed all selectors/pagination and hash-verified root, symlink and 292,366-character content (10 segments). Linux Node 22/24/26 CI, Security and preview build all pass. Actual Cloudflare API metrics: CPU P50 1.43 ms / P99 560 ms; memory P99 approximately 83 MiB. Free-plan refresh stress returned CPU-limit 503s; documented explicitly. Paid Workers upgrade is explicitly deferred by the user, so the existing Free plan retains cold-load/refresh CPU limits. No subscription or resource allowance was changed.