Workers changelog for 2024-05-17 #14635
Open
+6
−0
Conversation
This file contains 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
jasnell
requested review from
GregBrimble,
WalshyDev,
kodster28,
irvinebroque and
a team
as code owners
Deploying cloudflare-docs with
|
| Latest commit: |
2ba89e3
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://088e7816.cloudflare-docs-7ou.pages.dev |
| Branch Preview URL: | https://jasnell-patch-1.cloudflare-docs-7ou.pages.dev |
|
Files with changes (up to 15)
|
| - Update v8 to 12.6 | ||
| - DigestStream is now more efficient and exposes a new bytesWritten property that indicates that number of bytes written to the digest. | ||
| - The new `fetch_standard_url` compatibility flag will become active by default on June 3rd, 2024 and ensures that URLs passed into the fetch(...) API, the new Request(...) constructor, and redirected requests will be parsed using the standard WHATWG URL parser. | ||
| - A bug in the fetch API implementation would cause the content type of a Blob to be incorrectly set. Unfortunately, the fix for this bug potentially breaks some existing code so the fix is being released behind a new `blob_standard_mime_type` compatibility flag. |
There was a problem hiding this comment.
Suggested change
| - A bug in the fetch API implementation would cause the content type of a Blob to be incorrectly set. Unfortunately, the fix for this bug potentially breaks some existing code so the fix is being released behind a new `blob_standard_mime_type` compatibility flag. | |
| - Adds the `blob_standard_mime_type` compatibility flag, which fixes a bug in the Workers runtime's implementation of the fetch API that caused the content type of a Blob to be incorrectly set. |
Link to docs for the compat flag? When is it default enabled?
| description: |- | ||
| - Update v8 to 12.6 | ||
| - DigestStream is now more efficient and exposes a new bytesWritten property that indicates that number of bytes written to the digest. | ||
| - The new `fetch_standard_url` compatibility flag will become active by default on June 3rd, 2024 and ensures that URLs passed into the fetch(...) API, the new Request(...) constructor, and redirected requests will be parsed using the standard WHATWG URL parser. |
There was a problem hiding this comment.
Link to docs for this compat flag?
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.
No description provided.