Repository navigation
Conversation
dvkam
force-pushed
the
fix/647-framework-asset-headers
branch
from
November 2, 2026 22:51
b459837 to
3b94060
Compare
This branch has not been deployed
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.
Fixes #647
Preserve built
_headersfiles when uploading Worker versions that keep active secrets. Forward authored and generated files through the supported asset metadata format, without rewriting their contents.Keep reserved metadata files out of downloadable assets even when custom ignore rules try to include them. Clarify how framework apps configure headers on native Cloudflare deployments.
Validation:
f184a2f. All 170 focused tests and 33 workspace type-check tasks pass. Scoped formatting, lint and diff checks pass.No live Cloudflare deployment was performed.