Repository navigation
Release [changeset] - #364
Merged
Merged
Conversation
fingerprint-dx-team-actions-runner
Bot
requested review from
Orkuncakilkaya,
TheUnderScorer,
ilfa and
necipallef
as code owners
November 3, 2026 15:17
TheUnderScorer
approved these changes
Nov 3, 2026
Contributor
pnpm exec changesetto create a changeset. |
Contributor
Coverage report
Test suite run success205 tests passing in 61 suites. Report generated by 🧪jest coverage report action from d52fb5c Show full coverage report
|
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@fingerprint/aws-cloudfront-proxy@2.2.1
Patch Changes
^3.1144.0). (51192a4)Cache-Controlfor the agent through as it is. The proxy no longer capsmax-ageat 3600 or injectss-maxage=60, so the browser cache lifetime follows the origin. CloudFront derives its edge TTL from the origin directives subject to the cache policy's limits, and uses the policy default when the origin sends no cache lifetime. Strip the upstreamCache-Tagheader, which carries the upstream CDN's purge tag and an API-key-derived hash. (6dc6eef)e2e-tests@0.0.2
website@0.0.2