Repository navigation
crates.io: Upgrade fastly to v0.13.1 - #1248
Merged
Merged
Conversation
The `fastly` and `log-fastly` crates are updated from v0.13.0 to v0.13.1. The release adds opt-in APIs such as a cache lookup timeout and fixes clearing of `override_cache_key`, which `compute-static` does not use. The guest-side HTTP caching path that `set_after_send()` relies on only changed internally, so no code changes are needed.
ubiratansoares
approved these changes
Oct 7, 2026
ubiratansoares
left a comment
ubiratansoares
left a comment
Contributor
There was a problem hiding this comment.
Applied to staging and production
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
2 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.
The
fastlyandlog-fastlycrates are updated from v0.13.0 to v0.13.1. The release adds opt-in APIs such as a cache lookup timeout and fixes clearing ofoverride_cache_key, whichcompute-staticdoes not use. The guest-side HTTP caching path thatset_after_send()relies on only changed internally, so no code changes are needed.