EW-6697 Remove workers.dev Cache API restriction #20411
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
This bug was fixed about a year ago, but we forgot to update the docs.
harrishancock
requested review from
a team,
GregBrimble,
ToriLindsay,
irvinebroque,
jasnell and
mikenomitch
as code owners
Contributor
|
Howdy and thanks for contributing to our repo. We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally. |
github-actions
bot
assigned
GregBrimble,
irvinebroque,
jasnell,
mikenomitch and
ToriLindsay
Contributor
|
Preview URL: https://6ccd4c6c.preview.developers.cloudflare.com Files with changes (up to 15) |
irvinebroque
approved these changes
Mar 5, 2025
harrishancock
deleted the
harris/remove-workers-dev-cache-api-restriction
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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.
Summary
This bug was fixed about a year ago, but we forgot to update the docs.
Documentation checklist